FeaturesPricingAudit GuideFree StatementDashboard →

WCAG 2.2: What's New and When It Becomes Mandatory

WCAG 2.2 guide covering 56 success criteria, new mobile/cognitive accessibility requirements, and adoption timeline.

9 min read

Overview

WCAG 2.2 was published in October 2023 and adds 6 new success criteria focused on mobile accessibility, cognitive disabilities, and user control. While not yet legally mandatory, adoption is increasing.

Jurisdiction

Global (gradually; some jurisdictions mandate adoption 2025-2026)

Who must comply

Currently optional but recommended. By 2026-2027, expect legal mandates to require WCAG 2.2 Level AA in most countries. Early adoption shows organizational commitment to accessibility.

Penalties

Currently optional; no legal penalty for non-compliance yetWill match ADA/EAA penalties ($2,500-$75,000+ per violation) once legally mandated (expected 2025-2026)

Key Requirements

Focus Appearance (SC 2.4.11 - NEW)

Focus indicators must be clearly visible, prominent, and not confused with other content. Minimum visibility requirements added to WCAG 2.2.

Dragging Movements (SC 2.5.7 - NEW)

Any drag-and-drop interface must have an alternative single-pointer method (button click, form control). Users with motor disabilities cannot use drag-drop alone.

Hidden Targets (SC 2.5.8 - NEW)

Touch targets must be 24x24 CSS pixels for single pointers. Spacing requirement prevents accidentally activating wrong control.

Accessible Authentication (SC 3.3.7 - NEW)

Authentication must not require cognitive tests (CAPTCHA, puzzles). Must provide alternative method: email verification, security codes, etc.

Redundant Entry (SC 3.3.8 - NEW)

Users shouldn't be asked to enter the same information twice. If required, provide pre-filled field or confirmation.

Consistent Help (SC 3.2.6 - NEW)

Help mechanisms (contact info, chat, links) should be in consistent location across pages. Predictability aids users.

Compliance Checklist

All WCAG 2.1 Level AA criteria still met (backward compatible)

Focus indicators enhanced: clearly visible, minimum 2px, adequate contrast (SC 2.4.11)

Drag-and-drop interfaces have single-click alternatives (SC 2.5.7)

Touch targets are 24x24 CSS pixels minimum; well-spaced (SC 2.5.8)

Authentication doesn't require CAPTCHA or cognitive tests (SC 3.3.7)

No redundant data entry; pre-filled when possible (SC 3.3.8)

Help links/contact info in consistent location on all pages (SC 3.2.6)

Mobile touch targets adequate for users with motor disabilities

Keyboard alternatives to all drag-drop interactions

Alternative authentication methods tested

Penalties & Enforcement

Penalty range: Currently optional; no legal penalty for non-compliance yet to Will match ADA/EAA penalties ($2,500-$75,000+ per violation) once legally mandated (expected 2025-2026)
WCAG 2.2 not yet legally mandated in most jurisdictions. But proactive adoption is smart risk management and shows accessibility commitment.

Timeline

2023

WCAG 2.2 officially published (October 5, 2023)

2024

Early adopters implement WCAG 2.2; UK/EU testing and feedback phase

2025

EU, UK, Australia, Canada expected to mandate WCAG 2.2 adoption (phased)

2026

WCAG 2.2 likely becoming standard requirement; US courts beginning to reference it

2027+

WCAG 2.2 full adoption expected; WCAG 3.0 design phase ongoing

Frequently Asked Questions

Do I need to adopt WCAG 2.2 now?
Not legally required in 2026 (yet), but early adoption is recommended. By 2027-2028, expect legal mandates. Starting now gives you 2+ years to fix issues.
Are WCAG 2.1 and 2.2 compatible?
Yes, fully backward compatible. All WCAG 2.1 criteria still apply in 2.2. The 6 new criteria add to the 50, making 56 total (actually 52 + 4 revised).
Which new WCAG 2.2 criteria should I prioritize?
Start with: Focus Appearance (affects keyboard users), Accessible Authentication (blocks many users), Dragging Movements (motor disabilities), Touch Targets (mobile). These have highest impact.
What about CAPTCHA alternatives?
WCAG 2.2 says no CAPTCHA alone. Provide alternatives: email verification, SMS code, security questions, biometric, or other methods accessible to users with disabilities.
Does WCAG 2.2 apply to existing websites?
Once legally mandated (2025-2026 timeline), yes. But there's usually a grace period (6-12 months) to remediate. Start now to avoid rush.

Check your website for free

Get your ADA, WCAG, privacy & security score in 90 seconds.

No credit card
WCAG 2.1
ADA
Privacy

Related guides