What changed in WCAG 2.2, and what do you need to pass AA?
WCAG 2.2 adds 9 success criteria to WCAG 2.1 and removes one, 4.1.1 Parsing. To pass AA, a page meets every Level A and AA criterion, which now includes 6 of the new ones: 2.4.11, 2.5.7, 2.5.8, 3.2.6, 3.3.7 and 3.3.8.
95.9% of the top one million home pages had WCAG failures that software can detect, 56.1 errors per page on average. Low contrast text was on 83.9% of them.
The 9 new success criteria in WCAG 2.2
WCAG 2.2 became a W3C Recommendation on 5 October 2023. The current version is dated 12 December 2024. The new criteria, with their levels:
- 2.4.11 Focus Not Obscured (Minimum), AA: “When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.” Sticky headers and cookie banners are the usual cause.
- 2.4.12 Focus Not Obscured (Enhanced), AAA: no part of the focused component is hidden.
- 2.4.13 Focus Appearance, AAA: a focus indicator at least as large as a 2 CSS pixel border around the component, with a contrast of at least 3:1 between its focused and unfocused states.
- 2.5.7 Dragging Movements, AA: anything done by dragging can also be done with a single pointer without dragging, unless dragging is essential. Think sliders, sortable lists and map pins.
- 2.5.8 Target Size (Minimum), AA: “The size of the target for pointer inputs is at least 24 by 24 CSS pixels”, with exceptions such as enough spacing around a smaller target, or a link inside a sentence.
- 3.2.6 Consistent Help, A: if help such as contact details, a contact form or a chat appears on several pages, it appears in the same order relative to the rest of the page.
- 3.3.7 Redundant Entry, A: information the user already entered in the same process is filled in for them or available to select, so a shipping address does not have to be typed twice.
- 3.3.8 Accessible Authentication (Minimum), AA: no step of a login requires a cognitive function test, such as remembering a password or solving a puzzle, unless the step offers another method, a mechanism to help, or the test is only recognising objects or content the user provided. Letting people use a password manager and paste is the usual way to pass.
- 3.3.9 Accessible Authentication (Enhanced), AAA: the same, without the exceptions for recognising objects or the user’s own content.
What was removed
In the W3C’s words: “WCAG 2.2 has removed one success criterion, 4.1.1 Parsing.” The W3C overview calls it “obsolete and removed”. Teams that must report against WCAG 2.0 or 2.1 by policy may still need to test it.
Everything else from 2.1 carries over. A page that conforms to 2.2 is, in the W3C’s words, “at least as accessible” as one that conforms to 2.1.
What Level AA means
The conformance rule is short: “For Level AA conformance, the web page satisfies all the Level A and Level AA success criteria, or a Level AA conforming alternate version is provided.” There is no partial pass. One failed criterion on a page means that page does not conform.
The WCAG 2.2 AA checklist I work from
The full list of criteria is in the W3C text. This one is shorter: the checks that find most real problems, each tied to its criterion.
- Every image that carries meaning has a text alternative (1.1.1, A).
- Headings, lists, tables and form labels are real markup, not just styling (1.3.1, A).
- Text has a contrast of at least 4.5:1, large text 3:1 (1.4.3, AA). Buttons, inputs and icons have 3:1 against what is next to them (1.4.11, AA).
- Text can be resized to 200% without losing content (1.4.4, AA), and the page works at 320 CSS pixels wide without scrolling sideways (1.4.10, AA).
- Everything works with a keyboard (2.1.1, A), and focus never gets trapped (2.1.2, A).
- Focus moves in an order that makes sense (2.4.3, A), is visible (2.4.7, AA), and is not hidden behind sticky content (2.4.11, AA).
- Links make sense from their text, or their text and context (2.4.4, A).
- Targets are at least 24 by 24 CSS pixels, or spaced enough (2.5.8, AA), and dragging has a non-dragging alternative (2.5.7, AA).
- The page language is set in the code (3.1.1, A).
- Help appears in the same place across pages (3.2.6, A), and forms do not ask for the same thing twice (3.3.7, A).
- Every input has a label or instructions (3.3.2, A), and errors are named and described in text (3.3.1, A).
- Logins work with a password manager and paste (3.3.8, AA).
- Every control has a name and a role that assistive technology can read (4.1.2, A), and status messages are announced without moving focus (4.1.3, AA).
How to test it
- Run an automated scan, such as axe, on each template. It catches the mechanical failures, like missing labels and low contrast. A clean scan means the easy part is done.
- Put the mouse away and go through the main flows with the keyboard only: sign-up, search, checkout. If you lose track of where the focus is, so will the people who use a keyboard every day.
- Go through the same flows with a screen reader and listen for unnamed buttons and unannounced errors.
- Zoom the text to 200% and narrow the window to 320 pixels. This is usually where a sticky header takes half the screen.
Where WCAG 2.2 meets the law
The European Accessibility Act does not name a WCAG version. It asks for websites that are “perceivable, operable, understandable and robust”, the same four principles WCAG is built on. Reviewing against WCAG 2.2 AA is the practical way to check a site against that. It is not legal advice, and it is not a certificate.
Read next
Sources
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2, 12 Dec 2024
- W3C WAI, What’s new in WCAG 2.2, 5 Oct 2023
- WebAIM, The WebAIM Million, 30 Mar 2026
- EUR-Lex, Directive (EU) 2019/882, Annex I, 17 Apr 2019