Skip to main content

WCAG 2.2: What Developers Actually Need to Know

The latest accessibility standard adds 9 new success criteria. Here's what changed and what to fix first.

WCAG 2.2 was published as a W3C Recommendation in October 2023, replacing WCAG 2.1 as the current standard. It adds 9 new success criteria focused on users with cognitive disabilities, low vision, and mobile devices. If your site targets WCAG 2.1 AA, here's what you need to update.

New in WCAG 2.2

Focus Not Obscured (2.4.11 AA / 2.4.12 AAA): When an element receives keyboard focus, it must not be entirely hidden behind sticky headers, footers, or modals. At minimum, some part of the focused element must be visible. This is a common issue with sticky navigation bars that cover focused links when tabbing through a page.

Focus Appearance (2.4.13 AAA): Focus indicators must be at least 2px thick and have a contrast ratio of at least 3:1 against the unfocused state. No more barely-visible dotted outlines.

Dragging Movements (2.5.7 AA): Any functionality that uses dragging must also have a single-pointer alternative. Drag-and-drop interfaces need a click-based fallback for users who can't perform drag gestures.

Target Size Minimum (2.5.8 AA): Interactive targets must be at least 24x24 CSS pixels. This replaced the previous AAA-only requirement (44x44px) with a more practical minimum. Inline links in text are exempt.

Consistent Help (3.2.6 A): If your site provides help mechanisms (chat, phone, FAQ links), they must appear in the same relative location across pages. Don't move the help button around.

Redundant Entry (3.3.7 A): Don't ask users to re-enter information they've already provided in the same process. If they typed their address on step 1, auto-fill it on step 3.

Accessible Authentication (3.3.8 AA / 3.3.9 AAA): Login flows can't require cognitive function tests like puzzles or memory tasks. CAPTCHAs that require identifying objects are problematic. Allow password managers and passkeys.

What to do now

Run a scan of your site against WCAG 2.2 to see where you stand. Focus on the AA criteria first — they're the standard for legal compliance. The most common new violations are target size issues and focus obscured by sticky headers. Both are quick CSS fixes.

Ready to fix your accessibility issues?

Scan your site free. Get AI-powered fixes as pull requests.

Start scanning free