WCAG 2.2 Compliance Checklist
Every Level A and AA success criterion from WCAG 2.2 mapped to actionable checks. Work through each principle to verify your site meets current accessibility standards. Your progress is saved automatically.
Frequently asked questions
What's the difference between Level A, AA, and AAA?
Level A is the absolute minimum — content must clear these or it's literally inaccessible to some users. Level AA is the standard most laws and contracts require (ADA, Section 508, EAA, AODA). Level AAA is the aspirational tier — pursue it where reasonable but don't sacrifice usability. This checklist includes all A and AA criteria; AAA items are flagged separately in individual pattern pages.
Do I need to meet all of WCAG 2.2 to be "compliant"?
Conformance to WCAG 2.2 requires meeting all Level A and AA success criteria. "Substantially conforms" or "WCAG 2.2 AA where possible" is the common practical claim. Most legal requirements (ADA in the US, EAA in EU, AODA in Ontario) reference Level AA, so target that.
What's new in WCAG 2.2 vs 2.1?
Nine new success criteria, most focused on cognitive accessibility and mobile. Highlights: 2.4.11 Focus Not Obscured (Minimum) ensures focused elements aren't hidden by sticky headers; 2.5.8 Target Size (Minimum) requires 24×24 CSS px tap targets; 3.3.7 Redundant Entry means don't ask for the same data twice; 3.3.8 Accessible Authentication (Minimum) prohibits CAPTCHA-style cognitive function tests for login.
Are any 2.1 criteria removed in 2.2?
Yes — 4.1.1 Parsing is marked obsolete in 2.2. Modern browsers handle parse errors gracefully, so the criterion no longer adds value. Don't worry about validating against 4.1.1 specifically, but valid HTML is still good practice and helps automated tools.
How does this differ from the developer checklist?
This checklist maps 1:1 to WCAG 2.2's 50 success criteria — it's the legal-conformance audit. The Developer checklist is reorganized for build-time use, grouped by POUR principles, and includes practical implementation guidance beyond strict WCAG mapping. Use this one for compliance reporting; use the developer one for daily work.
What if my product can't meet some criterion?
Document the gap clearly in your accessibility statement, the user impact, and the timeline to fix. Some criteria are infeasible for certain content types (e.g., audio descriptions for live broadcasts) — WCAG provides documented "exceptions" for these cases. Engage with affected users and offer alternative formats where possible.
Does meeting WCAG 2.2 AA mean my site is fully accessible?
No — WCAG is a floor, not a ceiling. AA conformance dramatically reduces accessibility barriers but doesn't guarantee a great experience for every disabled user. Pair WCAG conformance with real user testing (especially with disabled users) and cognitive accessibility considerations from WCAG 3.0.
When should I expect to need WCAG 3.0?
WCAG 3.0 is in working-draft status with no published deadline. WCAG 2.2 will remain the legal reference for years. Treat WCAG 3.0 as a direction-of-travel — start adopting its more inclusive cognitive accessibility patterns now, but build to 2.2 for legal compliance. See the WCAG 3.0 guide for more detail.