by

In June 2022, the Web Content Accessibility Guidelines (WCAG) 2.2 became a formal recommendation. It’s an incremental update on WCAG 2.1, introducing new success criteria focused on mobile usability, authentication, and fine motor interactions. If your organisation already aligns with WCAG 2.1, the transition is straightforward—but you should understand the new expectations.

What is WCAG 2.2?

WCAG 2.2 sits within the W3C’s family of standards that help make digital content accessible to people with disabilities. Like earlier versions, it is organized into four principles—Perceivable, Operable, Understandable and Robust—and each principle contains testable success criteria at Levels A, AA, and AAA. WCAG 2.2 supplements rather than replaces WCAG 2.1, so compliance with 2.2 implies you also meet 2.1 and 2.0.

Why update from WCAG 2.1?

Technology and user expectations evolve. WCAG 2.2 addresses gaps identified through real-world audits and adds criteria that improve experiences for users of mobile devices, users with cognitive impairments, and those who rely on small touch targets or alternative input devices. Meeting WCAG 2.2 also signals proactive compliance as many organisations and laws will soon reference it.

What’s new in WCAG 2.2?

Here are the nine new success criteria introduced in WCAG 2.2 (Level A–AAA). These summaries are for orientation; refer to the official spec for details.

  • 2.4.11 Focus Appearance (Level AA) – Keyboard focus indicators must be clearly visible with a minimum area and contrast ratio.
  • 2.4.12 Focus Not Obscured (Minimum) (Level AA) – Ensure the focus indicator is not hidden when UI elements appear or scroll.
  • 2.4.13 Focus Not Obscured (Enhanced) (Level AAA) – A stricter version that prevents any obstruction of focus indicators.
  • 2.5.7 Dragging Movements (Level AA) – All functionality that uses dragging gestures must be achievable with a simple click or tap.
  • 2.5.8 Target Size (Minimum) (Level AA) – Interactive targets (buttons, links) should be at least 24 by 24 CSS pixels or have sufficient spacing around them.
  • 3.2.6 Consistent Help (Level A) – Help options like contact info, self-help tools or FAQs must appear in the same relative order across pages.
  • 3.3.7 Redundant Entry (Level A) – Users shouldn’t have to re-enter information that they’ve previously supplied within a process.
  • 3.3.8 Accessible Authentication (Minimum) (Level AA) – Login and authentication tasks must not rely on cognitive memory tasks (like solving puzzles or remembering long codes).
  • 3.3.9 Accessible Authentication (Enhanced) (Level AAA) – Strengthens 3.3.8 by limiting any cognitive function test and ensuring alternative methods exist.

Impact on existing WCAG 2.1 compliance

If you already meet WCAG 2.1 Level AA, most of your site will remain compliant. The biggest changes involve keyboard focus styling, touch target sizes, and authentication flows. Check custom components (modal overlays, menus) to ensure the focus indicator isn’t obscured. Review login forms and CAPTCHA use; ensure there’s an accessible alternative like e‑mail or device-based verification.

How to prepare for WCAG 2.2

  1. Audit against new criteria – Conduct a targeted review of pages and tasks using the success criteria above. Automated scanning helps, but manual checks are essential for focus indicators and drag gestures.
  2. Update design patterns – Work with your design system or component library to ensure buttons, links, and form elements meet target size and focus appearance requirements.
  3. Test user flows – Validate that multi-step processes don’t require users to retype data and that authentication does not present memory tests.
  4. Plan for future updates – WCAG 3.0 is on the horizon. Building accessible patterns now reduces future rework.

Conclusion & Next steps

WCAG 2.2 signals incremental progress toward more inclusive digital experiences. By understanding the new requirements and updating key interactions, organisations can demonstrate commitment to accessibility and reduce legal risk. If you need help interpreting the guidelines or auditing your site, request an accessibility audit and we’ll match you with a provider.

Leave a Comment