WCAG 2.2: the nine new success criteria
WCAG 2.2 has been a W3C Recommendation since 5 October 2023. It adds nine success criteria to WCAG 2.1 (six at levels A and AA, three at AAA) and removes criterion 4.1.1 “Parsing”.
In brief
- 9 new criteria: 6 at A/AA (adopted by RGAA 5) and 3 at AAA.
- Most visible: focus not obscured, dragging, 24 px target, consistent help, redundant entry, authentication.
- Criterion 4.1.1 is removed as obsolete with current browsers.
The nine criteria at a glance
| Criterion | Level | Requirement in short |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | A focused component is not entirely hidden by author-created content. |
| 2.4.12 Focus Not Obscured (Enhanced) | AAA | No part of the focused component is hidden. |
| 2.4.13 Focus Appearance | AAA | Focus indicator of minimum size and contrast. |
| 2.5.7 Dragging Movements | AA | Any dragging function has a single-pointer alternative. |
| 2.5.8 Target Size (Minimum) | AA | Targets at least 24 × 24 CSS px, with exceptions. |
| 3.2.6 Consistent Help | A | Repeated help mechanisms appear in the same relative place. |
| 3.3.7 Redundant Entry | A | Don’t ask again for information already provided in the same process. |
| 3.3.8 Accessible Authentication (Minimum) | AA | No login step relies on a cognitive test without an alternative. |
| 3.3.9 Accessible Authentication (Enhanced) | AAA | Version without the object-recognition or personal-content exceptions. |
Focus Not Obscured (2.4.11)
Typical case: a sticky header covers the focused link. Reserve space with scroll-padding (see RGAA 5). Test: tab to the footer then go back with Shift+Tab.
Dragging Movements (2.5.7)
Always offer a simple alternative: a “Move to…” menu, up/down buttons, a number field next to a slider.
<li draggable="true">
Write the FAQ
<label>Move to
<select name="column"><option>To do</option><option>In progress</option><option>Done</option></select>
</label>
</li>Target Size (2.5.8)
The clickable area counts, not the icon. Exceptions: sufficient spacing, inline links, native browser controls, essential size.
.icon-button { min-width: 24px; min-height: 24px; display: inline-grid; place-items: center; }
/* Key actions: aim for 44px (AAA criterion 2.5.5) */Consistent Help (3.2.6) and Redundant Entry (3.3.7)
Place contact, FAQ or chat in the same relative order on every page through a single template component. In checkout, offer “billing address same as delivery” instead of asking again.
Accessible Authentication (3.3.8)
Avoid memory, transcription or puzzle tests without an alternative. Allow pasting the password and code.
<input type="password" name="password" autocomplete="current-password">
<input type="text" name="otp" autocomplete="one-time-code" inputmode="numeric" maxlength="6" pattern="\d{6}">A CAPTCHA remains possible if an alternative is offered.
Frequently asked questions
Does WCAG 2.2 replace WCAG 2.1?
WCAG 2.2 is backward compatible: content meeting WCAG 2.2 also meets WCAG 2.1, except for the removed criterion 4.1.1.
Which WCAG 2.2 criteria are most often missed?
Target size, focus hidden by fixed headers, and blocked pasting in authentication fields.
Do automated tools detect WCAG 2.2?
Only very partially: only target size can be detected automatically, and even then exceptions require human review.