April 3, 2026

WCAG 2.2: The 9 New Requirements Your Website Probably Fails

WCAG 2.2 was published by the W3C in October 2023, adding 9 new success criteria to the existing WCAG 2.1 standard. Most websites that were built to meet WCAG 2.1 AA haven't been updated. Here's what changed and how to check your site.

What's New at Level AA

These are the criteria most relevant for legal compliance (Level AA):

2.4.11 Focus Not Obscured (Minimum) — Level AA

When an element receives keyboard focus, it can't be entirely hidden behind sticky headers, cookie banners, chat widgets, or fixed footers. At least part of the focused element must be visible.

Common failure: A sticky navigation bar covers focused links as the user tabs through content below it.

2.4.13 Focus Appearance — Level AAA (informative for AA planning)

While this is Level AAA, the direction is clear: focus indicators should be at least 2px thick with a 3:1 contrast ratio. Planning for this now future-proofs your site.

2.5.7 Dragging Movements — Level AA

Any functionality that requires a dragging movement (drag-and-drop, sliders, map panning) must provide a single-pointer alternative. Users must be able to accomplish the same action with clicks or taps.

Common failure: Image carousels that only work by swiping, or sortable lists that only work by drag-and-drop.

2.5.8 Target Size (Minimum) — Level AA

Interactive targets (buttons, links, form controls) must be at least 24x24 CSS pixels, or have sufficient spacing from adjacent targets. This is smaller than the Level AAA requirement of 44x44px but still catches many tiny mobile buttons.

Common failure: Footer link lists with links packed tightly together, small social media icons, compact navigation items on mobile.

3.2.6 Consistent Help — Level A

If your website provides help mechanisms (contact information, chat widget, FAQ link), they must appear in the same relative location across pages. Users shouldn't have to hunt for the help button on different pages.

3.3.7 Redundant Entry — Level A

Don't make users re-enter information they've already provided in the same process. If they entered their address on step 1, don't ask for it again on step 3. Auto-populate or let them select previously entered data.

3.3.8 Accessible Authentication (Minimum) — Level AA

Authentication can't require cognitive function tests like traditional CAPTCHAs, math puzzles, or remembering passwords without paste support. Users must be able to authenticate via password manager paste, copy-paste, or biometric authentication.

Common failure: CAPTCHA puzzles (select all traffic lights), login forms that block paste in password fields.

What Was Removed

4.1.1 Parsing was removed from WCAG 2.2. Modern browsers and assistive technologies handle HTML parsing errors gracefully, so this criterion is no longer needed. One less thing to worry about.

How to Check Your Site Against WCAG 2.2

1. Tab through your entire site — Is focus ever hidden behind a sticky header or banner?
2. Check target sizes — Use browser DevTools to measure clickable elements (24x24px minimum)
3. Test without dragging — Can you use every feature with just clicks?
4. Verify authentication — Can you paste into login forms? Are there CAPTCHA puzzles?
5. Check help placement — Is the help/contact link in the same spot on every page?
6. Test multi-step forms — Are you asked to re-enter information?

Most automated tools are still catching up to WCAG 2.2. Manual testing is especially important for these new criteria.