WCAG 2.2: What Changed and Why It Matters

Overview of Changes

WCAG 2.2, published as a W3C Recommendation in October 2023, builds on WCAG 2.1 with a focus on three populations: users with cognitive and learning disabilities, users of mobile devices, and users of ebooks.

The update adds 9 new success criteria at Levels A and AA, removes 1 at Level A (4.1.1 Parsing), and subtly modifies the understanding documents for dozens of existing criteria.

New Success Criteria That Matter Most

Of the 9 new criteria, 6 are at Level AA — meaning they apply to most compliance requirements. The three highest-impact additions for development teams are Target Size (2.5.8), Focus Not Obscured (2.4.11), and Accessible Authentication (3.3.8).

Target Size requires all interactive elements to be at least 24×24 CSS pixels. Based on RegLayer scans of 50,000 pages, 72% of sites fail this criterion — primarily in footer links, mobile navigation, and icon buttons without padding.

• 2.5.8 Target Size (Minimum) — 24×24px minimum for all interactive targets
• 2.4.11 Focus Not Obscured — focused elements can't be hidden by sticky headers
• 3.3.8 Accessible Authentication — no cognitive tests for login (CAPTCHAs, math puzzles)
• 2.5.7 Dragging Movements — single-pointer alternative required for all drag actions
• 3.3.7 Redundant Entry — don't make users re-enter previously provided information
• 3.2.6 Consistent Help — help mechanisms must appear in the same position across pages

Practical Impact on Your Codebase

The most common failures we see across 50,000+ scanned pages:

Target Size (72% fail rate): Footer links, social icons, and mobile nav items are almost always under 24px. The fix is simple — add min-height and min-width to clickable elements, or increase padding.

Focus Not Obscured (58% fail): Sticky headers and cookie banners routinely cover focused elements. Add scroll-padding-top equal to your sticky header height.

Dragging (41% fail): Sortable lists, kanban boards, and slider controls. Every drag interaction needs an explicit button alternative (move up/down arrows).

// Fix Target Size violations globally
button, a, [role="button"], input, select, textarea {
  min-height: 24px;
  min-width: 24px;
}

// Fix Focus Not Obscured
html {
  scroll-padding-top: calc(var(--header-height) + 16px);
}

How to Test for WCAG 2.2

RegLayer's scanner automatically detects violations for 6 of the 9 new criteria. For Consistent Help, Redundant Entry, and Accessible Authentication, automated detection requires multi-page flow analysis — which our crawler handles by following navigation paths.

For manual testing, focus on these quick checks:

• Tab through every page — is the focused element always visible?
• Check all interactive targets with DevTools — are they 24×24px minimum?
• Try your login flow without a mouse — can you complete it without memorizing anything?
• Attempt every drag interaction — is there a button alternative?
• Fill out a multi-step form — does it remember what you already entered?

Regulatory Adoption Timeline

WCAG 2.2 is already the de facto standard, but regulatory references are catching up:

October 2023: W3C publishes WCAG 2.2 as Recommendation. June 2025: EAA enforcement begins, referencing WCAG 2.1 but strongly recommending 2.2. January 2026: DOJ updated its web accessibility guidance to reference 2.2 criteria. 2026-2027: Section 508 refresh expected to formally incorporate WCAG 2.2.

Bottom line: if you're building for compliance in 2026, you should be testing against WCAG 2.2. The regulatory gap is closing fast.