Free educational reference
WCAG 2.2 AA, explained.
The nine success criteria added in WCAG 2.2, what changed from 2.1, who the new rules help, and how to meet each one. Source-backed, vendor-neutral, and honest about what the law actually requires.
What the law requires today (US)
WCAG 2.1 Level AA
The DOJ’s 2024 ADA Title II rule codified WCAG 2.1 AA for state and local government. Section 508 still references WCAG 2.0 AA.
The current W3C standard
WCAG 2.2 Level AA
Published as a W3C Recommendation (2023, updated 2024) and an ISO standard. Backward-compatible with 2.1, and the right target for new work.
This site explains the standard. For the US legal layer — who must comply with Title II, deadlines, and documents — see our sister reference wcag21aa.org.
Start here
Three ways into the reference. Pick the one that matches your question.
What changed
The 9 new criteria
Every success criterion added in WCAG 2.2, grouped by what it governs, with the exact threshold and who it helps.
The honest answer
Is WCAG 2.2 required?
What is legally mandated versus what is best practice, across ADA Title II, Section 508, and the EU — without the vendor spin.
Put it into practice
Conformance checklist
If you already meet 2.1 AA, the exact six criteria to add for 2.2 AA, each with a one-line test.
The nine new success criteria
WCAG 2.2 adds nine criteria and removes one (4.1.1 Parsing). Six of the nine apply at Level A or AA, so a site targeting AA needs to meet those six. Linked titles have a full reference page.
Focus & keyboard
- AA Focus Not Obscured (Minimum) 2.4.11
- AAA Focus Not Obscured (Enhanced) 2.4.12
- AAA Focus Appearance 2.4.13
Pointer & touch
- AA Dragging Movements 2.5.7
- AA Target Size (Minimum) 2.5.8
Forms & cognition
- A Consistent Help 3.2.6
- A Redundant Entry 3.3.7
- AA Accessible Authentication (Minimum) 3.3.8
- AAA Accessible Authentication (Enhanced) 3.3.9
About this reference
wcag22aa.org is an independent educational reference, not a government source and not a vendor selling an overlay or an audit. It exists to explain WCAG 2.2 clearly for the people who implement it: designers, developers, product and QA teams, and the accessibility and compliance staff who advise them.
Every factual claim cites a primary source: the W3C WCAG 2.2 Recommendation and its Understanding documents, ada.gov, the Federal Register, and other official records. Where law and standard diverge, the page says so plainly rather than overstating what is required.
Pages carry a “Last reviewed” date and are updated when the standard or the law changes. This site is also built to meet WCAG 2.2 AA itself — see the accessibility statement.