The Web Content Accessibility Guidelines (WCAG) 2.2 became an official W3C recommendation in October 2023, introducing nine new success criteria and retiring one from WCAG 2.1. For enterprise and government organizations operating digital products, understanding these changes isn't optional — it's a legal and ethical imperative.
In this article, we break down every new criterion, what it means in practice, and how to begin your remediation roadmap.
What Changed from WCAG 2.1 to 2.2?
WCAG 2.2 adds nine new success criteria across Levels A, AA, and AAA. The goal is to address gaps identified since 2018, particularly around mobile usability, cognitive accessibility, and authentication flows. One criterion — 4.1.1 Parsing — was removed as modern browsers handle parsing issues automatically.
The Nine New Success Criteria
2.4.11 Focus Not Obscured (Minimum) — Level AA
When a user interface component receives keyboard focus, the component must not be entirely hidden. This is critical for sticky headers and cookie banners that can overlap focused elements. Partial visibility is acceptable at the minimum level.
2.4.12 Focus Not Obscured (Enhanced) — Level AAA
The stricter AAA version requires that no part of the focused component is hidden by sticky or fixed content. Worth targeting for government portals and healthcare applications.
2.4.13 Focus Appearance — Level AAA
This criterion specifies minimum size and contrast requirements for focus indicators. While AAA, expect it to be referenced in procurement requirements for high-stakes sectors.
2.5.7 Dragging Movements — Level AA
Any functionality that can be operated by dragging must also be operable by a single pointer without dragging. Think of drag-to-reorder lists, map interactions, and sliders. This directly impacts design systems used in dashboards.
2.5.8 Target Size (Minimum) — Level AA
Interactive targets must be at least 24×24 CSS pixels. The spacing between targets counts — a target smaller than 24×24 is acceptable if there's enough surrounding non-interactive space. This has significant impact on mobile navigation and inline text links.
3.2.6 Consistent Help — Level A
If a help mechanism (phone number, chat, FAQ link, contact form) is provided across multiple pages, it must appear in the same relative order on each page. This primarily affects enterprise applications with embedded support widgets.
3.3.7 Redundant Entry — Level A
Information users previously entered in the same session must not be re-requested unless essential. This is transformative for multi-step forms: tax filings, job applications, e-commerce checkouts. Auto-filling or displaying entered data for review satisfies this criterion.
3.3.8 Accessible Authentication (Minimum) — Level AA
A cognitive function test (such as remembering a password or solving a puzzle) must not be required for authentication, unless an alternative method is provided, or a mechanism to assist the user is available. This directly impacts CAPTCHA implementations and password-only login screens.
3.3.9 Accessible Authentication (Enhanced) — Level AAA
Removes exceptions from the minimum level — no cognitive function tests are permitted. Password managers and copy-paste must be supported unconditionally.
Which Criteria Apply to You?
Most organizations target WCAG 2.2 Level AA, which adds the following criteria to your existing checklist:
- 2.4.11 Focus Not Obscured (Minimum)
- 2.5.7 Dragging Movements
- 2.5.8 Target Size (Minimum)
- 3.2.6 Consistent Help
- 3.3.7 Redundant Entry
- 3.3.8 Accessible Authentication (Minimum)
If your organization serves users under Section 508 (US federal) or EN 301 549 (EU), WCAG 2.2 AA is increasingly being cited in updated procurement standards.
Common Failure Patterns We See
Based on our audit work, here are the most prevalent failures organizations discover during a WCAG 2.2 audit:
- Fixed navigation obscuring focused links — Sticky headers covering the focused element in the content below
- Icon-only buttons under 24px — Close buttons, filter toggles, and pagination arrows frequently fail 2.5.8
- Slider components with no keyboard alternative — Price range and date-range sliders relying entirely on drag interaction
- Address forms re-asking for details already entered — Billing address asking for name/email again after shipping step
- CAPTCHA on every login — No alternative pathway for users unable to complete visual puzzles
Building Your WCAG 2.2 Roadmap
A pragmatic remediation roadmap typically follows four phases:
- Audit — Automated scanning plus manual expert review to identify all failures across the six new AA criteria
- Triage — Prioritise by severity and frequency; authentication and focus issues typically affect every session
- Remediate — Fix in code; update design systems to enforce minimum target sizes; restructure authentication flows
- Document & Monitor — Maintain an Accessibility Conformance Report (VPAT) and integrate automated checks into CI/CD
"Accessibility is not a feature. It is the baseline from which great user experience is built. WCAG 2.2 isn't raising the bar — it's clarifying what the bar always should have been."
How Let's Redefine Can Help
Our accessibility team conducts comprehensive WCAG 2.2 audits covering both automated and manual testing across WCAG 2.1 and all nine new 2.2 criteria. We deliver a prioritised remediation report with code-level guidance, and can manage the full remediation lifecycle on your behalf.
We also offer WCAG-compliant design system reviews to prevent failures from reaching production in the first place — the most cost-effective form of accessibility investment.
If you're unsure of your current conformance level or have an upcoming procurement requirement, contact us for a complimentary accessibility assessment.