WCAG 2.2 Explained: What's New, What Changed, and What Your Team Needs to Do

WCAG 2.2 became a W3C Recommendation in October 2023 — and it's now the accessibility standard referenced in the European Accessibility Act, ADA compliance guidance, and increasingly in enterprise procurement requirements. If your team is still auditing against WCAG 2.1, you're behind. Here's what changed and what it means in practice.

What Was Removed

WCAG 2.2 removed one success criterion from WCAG 2.1: 4.1.1 Parsing. This criterion required valid HTML markup, but with modern browsers handling malformed markup gracefully, the W3C determined it no longer served its intended purpose. Removing it doesn't mean HTML quality doesn't matter — the focus has shifted to what users actually experience, not markup compliance in isolation.

The 9 New Success Criteria

WCAG 2.2 adds nine new success criteria across three conformance levels.

Level A: 3.2.6 Consistent Help — help mechanisms must appear in consistent locations. 3.3.7 Redundant Entry — users shouldn't have to re-enter information already provided in the same session.

Level AA: 2.4.11 Focus Appearance — keyboard focus indicators must meet minimum size and contrast. 2.5.7 Dragging Movements — any drag action must have a pointer alternative. 2.5.8 Target Size (Minimum) — interactive targets must be at least 24×24 CSS pixels. 3.3.8 Accessible Authentication — authentication cannot require solving a cognitive test without an alternative.

Level AAA: 2.4.12 Focus Appearance (Enhanced), 3.3.9 Accessible Authentication (Enhanced).

The biggest practical change in WCAG 2.2 is keyboard focus visibility. Many sites that were 'WCAG 2.1 compliant' will fail on this criterion alone.

What This Means for Your Codebase

Focus appearance is the criterion most likely to require design-level changes. The default browser focus ring is typically insufficient under the new minimum requirements. Your design system needs to define a visible focus indicator — at least 2px, with adequate contrast — and apply it consistently across all interactive elements.

Target size affects mobile interfaces most acutely. Anything smaller than 24×24px without sufficient whitespace is now a WCAG 2.2 AA failure. Accessible authentication hits any interface using CAPTCHA or image-based challenges during login — you need a bypass to remain compliant.

Audit and Remediation Approach

For teams already WCAG 2.1 compliant, the delta to 2.2 is manageable. Run an automated scan, then conduct manual testing with keyboard navigation and screen readers. Focus your manual review on: focus indicator visibility, form re-entry across multi-step flows, authentication journeys, and drag-based interactions. Document findings in an updated Accessibility Conformance Report.