Written by the AX4E accessibility team. Checked against the primary sources listed at the end of this page (W3C, U.S. Department of Justice, ISO and others). Last reviewed November 4, 2026. Read how we write and review guides in our editorial standards.
The short version
If your site conforms to WCAG 2.1 AA, moving to 2.2 AA means meeting six additional criteria (two at Level A, four at Level AA). Most of them are about keyboard focus, touch and pointer use, and reducing memory and effort, which especially helps people with motor and cognitive disabilities.
The nine new success criteria
| Criterion | Level | In plain language |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | When something has keyboard focus, sticky headers, chat bubbles or banners must not completely hide it. |
| 2.4.12 Focus Not Obscured (Enhanced) | AAA | No part of the focused item is hidden. |
| 2.4.13 Focus Appearance | AAA | The focus indicator is large and high-contrast enough to see easily. |
| 2.5.7 Dragging Movements | AA | Anything you can do by dragging can also be done with a simple click or tap, like arrows on a slider. |
| 2.5.8 Target Size (Minimum) | AA | Clickable targets are at least 24 by 24 CSS pixels, or have enough space around them, with some exceptions. |
| 3.2.6 Consistent Help | A | If you offer help, like a phone number, chat or contact link, it appears in the same place across pages. |
| 3.3.7 Redundant Entry | A | Do not make people re-type information they already gave in the same process. Pre-fill it or let them select it. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Logging in must not depend on a memory or puzzle test, unless there is an alternative. Allow password managers and paste. |
| 3.3.9 Accessible Authentication (Enhanced) | AAA | A stricter version, with fewer exceptions. |
What was removed
Success criterion 4.1.1 Parsing was removed from WCAG 2.2 because modern browsers and assistive technology handle the issues it addressed. The W3C has also noted it should be treated as always satisfied for WCAG 2.0 and 2.1.
What to check on your site
- Tab through your pages with a sticky header and cookie banner showing. Can you always see what is focused?
- Find anything draggable: sliders, sortable lists, maps, carousels. Is there a click alternative?
- Measure small targets: icon buttons, close buttons, pagination, links in dense lists.
- Check where help lives across your templates.
- Walk through multi-step forms and checkouts. Are you asking for the same address twice?
- Test your login. Can a password manager fill it? Can people paste? Is any CAPTCHA the only option?
Should you target 2.1 or 2.2?
Some requirements still name WCAG 2.1, including the U.S. rule for state and local governments. WCAG 2.2 is backward compatible: content that meets 2.2 AA also meets 2.1 AA. Targeting 2.2 future-proofs your work and is increasingly what buyers ask for.
Common questions
When was WCAG 2.2 published?
WCAG 2.2 became a W3C Recommendation on October 5, 2023.
How many new success criteria are in WCAG 2.2?
Nine: two at Level A, four at Level AA and three at Level AAA. One criterion, 4.1.1 Parsing, was removed.
If we meet WCAG 2.2, do we also meet 2.1?
Yes. WCAG 2.2 includes all WCAG 2.1 success criteria except the removed 4.1.1 Parsing, which is treated as satisfied, so 2.2 conformance covers 2.1.
Want a second set of eyes?
Request a free assessment. A real person on our team looks at your site or documents and tells you, in plain language, what to fix first.
Request a free assessment Run a free scan