WCAG 2.2 AA conformance checklist
If you already meet 2.1 AA, this is the exact gap to 2.2 AA: six criteria, each with a one-line test.
The six-criterion checklist
The Level A and AA criteria new in WCAG 2.2, with how to verify each:
| SC | Criterion | Level | How to verify |
|---|---|---|---|
| 2.4.11 | Focus Not Obscured (Minimum) | AA | Tab through the page with sticky headers, footers, and banners present; confirm no focused element is entirely hidden. |
| 2.5.7 | Dragging Movements | AA | For each drag interaction, confirm a single-pointer click or tap alternative exists. |
| 2.5.8 | Target Size (Minimum) | AA | Measure pointer targets; confirm at least 24 by 24 CSS px, or that the spacing, inline, or equivalent exception applies. |
| 3.2.6 | Consistent Help | A | If help links or contact options repeat across pages, confirm they appear in the same relative order. |
| 3.3.7 | Redundant Entry | A | In multi-step forms, confirm earlier-entered data is auto-filled or selectable rather than re-typed. |
| 3.3.8 | Accessible Authentication (Minimum) | AA | Confirm login allows password autofill and paste, accepts pasted one-time codes, or offers a non-cognitive method. |
Each criterion links to a full page with thresholds, code, exceptions, and detail. Also remove 4.1.1 Parsing from any 2.2 checklist — it is obsolete and removed (why).
What full 2.2 AA includes
If you do not already have a WCAG 2.1 AA basis, “2.2 AA” means all 55 Level A and AA criteria, not just these six. The other 49 are carried forward unchanged from WCAG 2.0 and 2.1 — contrast, keyboard operability, names and roles, captions, headings and structure, and so on. The authoritative, filterable list is the W3C quick reference (Source: W3C, How to Meet WCAG (Quickref) ) .
Tools you need
- Keyboard only. Tab, Shift+Tab, Enter, Space, Escape, and arrow keys cover focus, dragging alternatives, and obscured-focus testing.
- Browser dev tools. The box model shows target sizes in CSS pixels for 2.5.8.
- An automated checker such as axe to catch carried-forward 2.0/2.1 issues. Automated tools cannot fully judge the new 2.2 criteria, which need manual review.
- A password manager to verify autofill and paste are not blocked for 3.3.8.
Writing a conformance statement
An accessibility statement should name the standard and level you are claiming (WCAG 2.2 Level AA), the date and method of evaluation, any known exceptions, and a way to report barriers. For a worked example, see this site’s own accessibility statement, which targets WCAG 2.2 AA. A dedicated guide to authoring conformance statements is planned as this reference grows.
Common questions
What is on a WCAG 2.2 AA checklist?
All Level A and AA success criteria, which is 55 criteria in WCAG 2.2. If you already meet WCAG 2.1 AA, the new work is the six criteria added in 2.2 at Level A or AA, listed here.
Do I need to re-check all 55 criteria?
If you have a current WCAG 2.1 AA conformance basis, no. The 2.1 AA criteria are unchanged in 2.2, so you only need to verify the six new A/AA criteria and remove 4.1.1 Parsing from your list.