WCAG 2.2: What Changed and How to Update Your Compliance

WCAG 2.2 became a W3C Recommendation in October 2023, adding 9 new success criteria to the existing WCAG 2.1 standard. While the EAA currently references WCAG 2.1, the expectation is that 2.2 will be adopted as the baseline. Here's what changed and what to do about it.

New Level A criteria

2.4.11 Focus Not Obscured (Minimum) — When an element receives keyboard focus, it must not be entirely hidden by other content (like sticky headers or cookie banners). This is particularly relevant for consent banners — a common accessibility failure. 3.2.6 Consistent Help — If you provide help mechanisms (chat widget, contact link, FAQ), they must be in a consistent location across pages. 3.3.7 Redundant Entry — Don't make users re-enter information they've already provided in the same process. Auto-populate where possible.

New Level AA criteria

2.4.12 Focus Not Obscured (Enhanced) — Like 2.4.11 but stricter: no part of the focused element may be hidden, not just "not entirely hidden." 2.5.7 Dragging Movements — Any functionality that uses dragging must also have a non-dragging alternative (click, tap, or keyboard operation). 2.5.8 Target Size (Minimum) — Interactive targets must be at least 24×24 CSS pixels, with exceptions for inline links and browser-default controls. 3.3.8 Accessible Authentication (Minimum) — Login processes must not rely on cognitive function tests (like transcribing text or solving puzzles). Password fields with paste enabled, and passkeys/WebAuthn, satisfy this. 3.3.9 Accessible Authentication (Enhanced) — Stricter version: no cognitive function tests at all, including object recognition.

What was removed

WCAG 2.2 removed 4.1.1 Parsing from Level A. Modern browsers and assistive technologies no longer need perfectly valid HTML to function. This is a pragmatic acknowledgment that the web has moved on.

Prioritization for most websites

If you're already WCAG 2.1 AA compliant, here's the priority order for 2.2: 1. Focus Not Obscured — Check that sticky elements don't cover focused content. High impact, often a quick fix. 2. Target Size — Audit your interactive elements for the 24px minimum. Common failures in footers, mobile nav, and form elements. 3. Accessible Authentication — Ensure login works with password managers (paste enabled) or WebAuthn. If you use CAPTCHA, it needs an accessible alternative. 4. Dragging Movements — If you have drag-and-drop interfaces, add click/keyboard alternatives. 5. Consistent Help & Redundant Entry — Usually satisfied by good UX design.

Moving forward

Even though the EAA references WCAG 2.1, investing in WCAG 2.2 compliance now positions you ahead of the curve. The new criteria address real usability gaps — particularly for users with motor disabilities and cognitive impairments — and meeting them makes your product better for everyone.