Updated: 2026-07-07

WCAG 2.2[1] was published as a W3C recommendation on October 5, 2023, adding 9 new criteria to WCAG 2.1. Changes are modest in number but significant in intention: they improve accessibility on mobile and for users with cognitive limitations. For companies bound by the EAA (in force since 2025), WCAG 2.1 AA remains the legal minimum; WCAG 2.2 AA is where the bar is heading.

Key takeaways

  • The 4 most impactful new AA criteria are: Focus Not Obscured (2.4.11), Dragging Movements (2.5.7), Target Size Minimum (2.5.8), and Accessible Authentication (3.3.8).

  • Target Size (2.5.8) is the criterion most likely to break existing UIs: 16×16 icon buttons and dense inline links violate by default.

  • For teams already meeting WCAG 2.1 AA, the jump to 2.2 AA is 1-2 sprints for a medium-size product.

  • WCAG 3 ("Silver") is still in development; do not wait for it to improve accessibility.

  • EAA regulation references WCAG 2.1 AA as minimum; targeting 2.2 AA directly is more future-compatible.

The 9 New Criteria

Level A (minimum)

3.2.6 Consistent Help (A): if the site offers "contact", "help", "chat", they must be in the same consistent location across pages.

3.3.7 Redundant Entry (A): do not ask for information already entered in the same session.

Level AA (most impactful)

2.4.11 Focus Not Obscured (Minimum) (AA): when an element receives keyboard focus, at least part of it must be visible.

2.5.7 Dragging Movements (AA): any drag-requiring functionality must have an alternative (click, tap).

2.5.8 Target Size (Minimum) (AA): clickable targets must be at least 24×24 CSS pixels.

3.3.8 Accessible Authentication (Minimum) (AA): login process must not require cognitive skills without alternative. Password managers must work.

Level AAA

2.4.12 Focus Not Obscured (Enhanced) (AAA): focused element must not be at all obscured.

2.4.13 Focus Appearance (AAA): focus indicator must have minimum 3:1 contrast and sufficient area.

3.3.9 Accessible Authentication (Enhanced) (AAA): even stricter than 3.3.8.

Impact on Existing Products

Target Size (2.5.8)

Most likely to break your current UI:

  • Small inline links within text.

  • 16×16 or 20×20 icon buttons.

  • Small switches/toggles.

  • Dense pagination links.

Solution: increase to minimum 24×24, or add padding making the clickable area 24×24 even if the visible element is smaller.

Dragging Movements (2.5.7)

Any drag-and-drop interface: kanban boards, list reordering, image croppers, custom range sliders.

Solution: add alternative controls (buttons, numeric inputs). Keep drag as preferred but not the only method.

Accessible Authentication (3.3.8)

Breaking patterns:

  • reCAPTCHA v2 with image identification (cognitive load).

  • Password fields blocking paste (prevents password managers).

  • Custom CAPTCHA with puzzles.

Solution: accessible CAPTCHA (reCAPTCHA v3 silent, Cloudflare Turnstile), allow paste, alternative methods (passkey, social login).

Focus Not Obscured (2.4.11)

  • Sticky headers that cover the focused element while scrolling.

  • Cookie banners fixed at the bottom.

  • Chat widgets that cover buttons.

Solution: scroll-margin-top in CSS, careful z-index management, viewport-unit awareness.

Practical Migration from 2.1

If you already meet WCAG 2.1 AA, upgrading to 2.2 AA is manageable:

  • Audit with 2.2-aware tools: axe-core[2] already ships WCAG 2.2 rules such as target-size (disabled by default until the version is more widely adopted), and Pa11y and WAVE also cover the new criteria.

  • Prioritise the 4 new AA criteria: 2.4.11, 2.5.7, 2.5.8, 3.3.8.

  • Review drag interactions, icon buttons, CAPTCHAs.

  • Update internal design-system policies.

Typically 1-2 sprints for a mid-size product already accessible to 2.1.

The EAA context

For companies already operating under the European Accessibility Act (in force since 28 June 2025):

  • Legal minimum: EN 301 549 references WCAG 2.1 AA.

  • Next revision of EN 301 549 will incorporate WCAG 2.2.

  • Prudent decision: target 2.2 AA now, so you do not have to re-audit when the reference changes.

In the UK, the GOV.UK Service Manual[3] already requires teams to, verbatim, "meet level AA of the Web Content Accessibility Guidelines (WCAG) 2.2 as a minimum" in its acceptance criteria for public services.

Cognitive accessibility: the new focus

A common thread in WCAG 2.2 is cognitive accessibility:

  • Redundant Entry reduces memory load.

  • Accessible Authentication removes cognitive tests.

  • Consistent Help reduces cognitive search effort.

This benefits every user, not only people with cognitive disabilities. It is an area WCAG had historically paid the least attention to.

Conclusion

WCAG 2.2 is an incremental but focused update. For teams already meeting 2.1 AA, the jump is manageable and worthwhile: the benefits are real, especially on mobile and for users with cognitive load. For companies already bound by the EAA, targeting 2.2 AA directly is more future-compatible. The standard’s direction is clear: increasing focus on cognitive, mobile, and situational accessibility. Sticking with only visible technical criteria (contrast, ARIA) no longer suffices to be considered an accessible product.

Spanish version: WCAG 2.2: lo que trae la nueva versión de accesibilidad.

Sources

  1. WCAG 2.2
  2. axe-core
  3. GOV.UK Service Manual