Accessibility Compliance
WCAG 2.1 vs 2.2: The 9 New Success Criteria
WCAG 2.2 was published by the W3C in October 2023, and it doesn't replace WCAG 2.1 - it extends it. Every WCAG 2.1 success criterion still applies; 2.2 adds nine new ones and removes one obsolete one. If you're already WCAG 2.1 AA conformant, here's exactly what's new and what it takes to close the gap to 2.2.
The nine new success criteria
- 2.4.11 Focus Not Obscured (Minimum) - AA: a keyboard-focused element must not be entirely hidden by other content, like a sticky header or a cookie banner.
- 2.4.12 Focus Not Obscured (Enhanced) - AAA: a stricter version requiring no part of the focused element to be hidden.
- 2.4.13 Focus Appearance - AAA: sets minimum size and contrast requirements for the visible focus indicator itself.
- 2.5.7 Dragging Movements - AA: any drag-based interaction must have a single-pointer alternative that doesn't require dragging.
- 2.5.8 Target Size (Minimum) - AA: interactive targets must be at least 24x24 CSS pixels, with some exceptions.
- 3.2.6 Consistent Help - A: if a help mechanism (contact info, chat, FAQ link) appears on multiple pages, it must appear in the same relative order each time.
- 3.3.7 Redundant Entry - A: information a user has already provided in a process shouldn't need to be re-entered, unless it's for security or is no longer valid.
- 3.3.8 Accessible Authentication (Minimum) - AA: login shouldn't rely solely on a cognitive function test, like remembering a password, without an alternative - unless specific exceptions apply.
- 3.3.9 Accessible Authentication (Enhanced) - AAA: a stricter version of the same criterion, with fewer exceptions.
What was removed
4.1.1 Parsing was dropped as obsolete. It addressed HTML parsing errors (duplicate IDs, improper nesting) that modern browsers and assistive technology now handle consistently regardless, making the criterion no longer meaningful to test.
The criteria most sites fail first
From practical audit experience, Target Size (Minimum) and Focus Not Obscured are the two most commonly failed on first testing, since they affect extremely common UI patterns - small icon buttons, sticky headers and banners - that predate the criteria entirely.
What this means if you're already WCAG 2.1 AA conformant
You're not automatically 2.2 conformant - but treat it as a focused gap assessment against nine specific, well-defined criteria rather than a full re-audit. That's a much smaller scope of work than starting from scratch.
Need help with this in practice?
A5 Cyber Nexus audits, remediates and certifies against these frameworks.
Frequently asked questions
Do I need to redo my whole audit for WCAG 2.2?
No - if you're already WCAG 2.1 AA conformant, a focused gap assessment against the 9 new criteria is a much smaller, faster scope than a full re-audit.
Which regulations actually require WCAG 2.2 specifically, versus 2.1?
Most current regulations (the US ADA Title II rule, for example) still reference WCAG 2.1 AA as their explicit baseline, though 2.2 is increasingly treated as current best practice. We test to 2.2 by default so you're ahead of that curve.
Make it accessible.
Make it attack-ready.
Prove both before launch.
Bring us your app, audit deadline, or security concern. We'll map the fastest path to WCAG conformance, VAPT coverage, and regulator-ready evidence.
