WCAG 2.2 vs 2.1:
what changed
WCAG 2.2 introduced 9 new success criteria. Here's what's different, why it matters, and which version you should target.
WCAG 2.1 vs 2.2 at a glance
Both versions share the same foundation, but 2.2 adds important improvements.
WCAG 2.1
Released June 2018
- 78 success criteria (Levels A, AA, AAA)
- Added mobile accessibility criteria
- DOJ-referenced standard for Title II
- Most commonly cited in legal proceedings
WCAG 2.2
Released October 2023
- 87 success criteria (+9 new)
- Improved focus visibility requirements
- Better cognitive accessibility support
- Current W3C recommendation
Recommended for new projects
9 new success criteria in WCAG 2.2
These additions focus on improved focus visibility, motor accessibility, cognitive support, and authentication.
Level AA— Most relevant for compliance
Focus Not Obscured (Minimum)
When a component receives keyboard focus, it must not be entirely hidden by author-created content.
Dragging Movements
Any functionality that uses dragging must have a single-pointer alternative.
Target Size (Minimum)
Interactive targets must be at least 24x24 CSS pixels, with some exceptions.
Accessible Authentication (Minimum)
Authentication must not require cognitive function tests unless alternatives exist.
Level A— Basic requirements
Consistent Help
Help mechanisms must appear in the same relative order across pages.
Redundant Entry
Information previously entered should be auto-populated or available for selection.
Level AAA— Enhanced (not typically required)
Focus Not Obscured (Enhanced)
When a component receives focus, no part of it should be hidden by author-created content.
Focus Appearance
Focus indicators must have sufficient size and contrast to be clearly visible.
Accessible Authentication (Enhanced)
No cognitive function test is allowed for authentication, even with alternatives.
Which version should you target?
The answer depends on your situation and requirements.
Target WCAG 2.2 AA for new projects
If you're building something new or doing a major redesign, target WCAG 2.2 Level AA. It's the current W3C recommendation, and meeting 2.2 automatically means you meet 2.1.
- Future-proofs your compliance efforts
- Better experience for users with disabilities
- Washington State already requires 2.2
WCAG 2.1 AA is the legal baseline (for now)
Courts and the DOJ Title II rule reference WCAG 2.1 Level AA. If you're focused purely on meeting current legal requirements, 2.1 AA is the benchmark.
- Referenced in DOJ's April 2024 Title II rule
- Most commonly cited standard in litigation
- European Accessibility Act references EN 301 549 (based on 2.1)
What about WCAG 3.0?
WCAG 3.0 is in development but not yet finalized. It will use a different conformance model and scoring system. For now, focus on 2.1 or 2.2 — when 3.0 is released, there will be transition guidance.
Note: One criterion was removed
WCAG 2.2 removed Success Criterion 4.1.1 "Parsing" from WCAG 2.1. This criterion required valid HTML markup. It was removed because modern browsers and assistive technologies handle parsing errors well, and other criteria already cover the accessibility concerns it addressed.
If you're already meeting WCAG 2.1, you don't need to worry about this change — it only removes a requirement, it doesn't add one.
Frequently asked questions
Common questions about WCAG 2.1, 2.2, and choosing the right version.
If I meet WCAG 2.2, do I automatically meet 2.1?
Yes. WCAG 2.2 is backward compatible with 2.1 (except for the removed 4.1.1 criterion). Meeting 2.2 Level AA means you meet 2.1 Level AA as well.
Do I need to meet Level AAA criteria?
Level AAA is not typically required for legal compliance. It represents enhanced accessibility that may not be achievable for all content types. Focus on Level AA, which balances strong accessibility with practical implementation.
What's the minimum target size in WCAG 2.2?
The new Target Size (Minimum) criterion (2.5.8) requires interactive elements to be at least 24x24 CSS pixels. There are exceptions for inline links, user-agent controls, and cases where the target's size is essential to the information being conveyed.
How do the new authentication criteria affect CAPTCHAs?
Accessible Authentication (3.3.8) at Level AA requires that if you use a cognitive function test (like a CAPTCHA), you must provide an alternative method. This could be audio CAPTCHA, object recognition, or allowing password managers. Level AAA (3.3.9) prohibits cognitive tests entirely.
Does inclly test for WCAG 2.2 criteria?
Yes. inclly scans for both WCAG 2.1 and 2.2 criteria. Our reports clearly indicate which version each issue relates to, so you can prioritize based on your compliance target.
When will regulations require WCAG 2.2?
Washington State already requires WCAG 2.2 AA by July 2026. Other jurisdictions may follow. The W3C recommends 2.2 as the current standard, so it's likely that future regulatory updates will reference it.
Continue Learning
Explore related guides to strengthen your WCAG compliance strategy.
WCAG 2.2 AA Checklist
All 50 Level A and AA success criteria with automated vs manual testing indicators.
EAA vs WCAG
How the European Accessibility Act relates to WCAG and what compliance means.
Testing Tools Comparison
Compare axe, WAVE, Lighthouse, Pa11y and other accessibility testing tools.
Manual Testing Guide
5 essential manual accessibility tests every developer should know.
Check your WCAG status
See how your site measures up against both WCAG 2.1 and 2.2 criteria. Get clear, actionable reports that prioritize what to fix first.