WCAG 2.2 became a W3C Recommendation in October 2023. It adds 9 new success criteria to WCAG 2.1 and removes one. If you're building for ADA, Section 508, or the European Accessibility Act (EAA) — which took effect in June 2025 — you need to know what changed.

What changed from 2.1 to 2.2

Added: 9 new success criteria (6 at Level A/AA, 3 at Level AAA) Removed: 4.1.1 Parsing (no longer relevant with modern browsers) Unchanged: All other 2.1 criteria remain

The new criteria focus on three areas: cognitive accessibility, mobile/touch interactions, and authentication.

New Level A criteria

3.3.7 Redundant Entry

Don't make users re-enter information they've already provided in the same process. If a user enters their address on step 1 of checkout, don't ask for it again on step 3.

What to do: Audit multi-step forms for repeated fields. Use autocomplete attributes. Pre-fill with previously submitted data.

3.2.6 Consistent Help

If your site provides help mechanisms (chat, phone, FAQ link), they must appear in the same relative location on every page.

What to do: Place help links in a consistent location (footer or fixed position). Don't conditionally hide them.

New Level AA criteria

2.4.11 Focus Not Obscured (Minimum)

When a component receives keyboard focus, it must not be entirely hidden by sticky headers, modals, or cookie banners.

What to do: Add scroll-padding-top matching your sticky header height. Test tab navigation with sticky elements.

html {
  scroll-padding-top: 80px; /* height of sticky nav */
}

2.5.7 Dragging Movements

Any drag-and-drop functionality must have a non-dragging alternative (buttons, dropdown, etc.).

What to do: Add move up/down buttons to sortable lists. Kanban boards need a "Move to" menu.

2.5.8 Target Size (Minimum)

Interactive targets must be at least 24x24 CSS pixels. Exceptions exist for inline links and native controls.

What to do: Audit small icon buttons in toolbars, tables, and cards. Add padding to reach 24px minimum.

button, a, [role="button"] {
  min-width: 24px;
  min-height: 24px;
}

3.3.8 Accessible Authentication (Minimum)

Don't require cognitive function tests (puzzle CAPTCHAs, security questions) as the sole authentication method.

What to do: Support password managers with correct autocomplete attributes. If using CAPTCHA, offer an alternative (email code, SMS). Support passkeys/WebAuthn.

<input type="email" autocomplete="username" />
<input type="password" autocomplete="current-password" />

New Level AAA criteria

2.4.12 Focus Not Obscured (Enhanced) — focused element must be fully visible, not just partially
2.4.13 Focus Appearance — focus indicator must meet size and contrast requirements
3.3.9 Accessible Authentication (Enhanced) — no cognitive tests at all, no exceptions

Removed: 4.1.1 Parsing

Valid HTML is no longer a WCAG conformance requirement. Modern browsers handle parsing errors gracefully. But duplicate IDs still cause real issues — keep your HTML valid anyway.

Compliance deadlines

ADA (US): Courts increasingly reference 2.1 AA. Adopting 2.2 is advisable.
Section 508: Still references 2.0 formally. Refresh expected.
EAA (EU): Took effect June 2025. Maps to WCAG 2.1 via EN 301 549 — 2.2 alignment expected.
AODA (Ontario): References 2.0 AA. Update pending.

Targeting WCAG 2.2 Level AA covers all current and upcoming regulations.

Implementation checklist

Add scroll-padding-top for sticky headers
Ensure 24x24px minimum on interactive targets
Add non-drag alternatives to drag-and-drop UIs
Check multi-step forms for redundant entry
Ensure help mechanisms are consistently located
Support password managers with correct autocomplete
Offer CAPTCHA alternatives

Is your team testing against 2.2, or still on 2.1? The target size and focus obscuring criteria seem to cause the most rework — what's been your experience?