Complete Guide to WCAG 2.2 AA: The 9 New Success Criteria Every Developer Must Know

The World Wide Web Consortium (W3C) officially published WCAG 2.2 as the definitive standard for digital accessibility. WCAG 2.2 builds directly upon WCAG 2.1 by adding 9 new success criteria focused on mobile usability, cognitive accessibility, and keyboard focus visibility.

Overview of WCAG 2.2 AA

WCAG 2.2 introduces stricter rules to ensure that users with cognitive impairments, motor disabilities, and low vision can interact with modern web applications without friction.

1. Focus Appearance (WCAG 2.4.11 - Level AA)

When an interactive control receives keyboard focus, the focus indicator must have an area of at least the perimeter of the control with a 1px thickness and achieve a contrast ratio of at least 3:1 against adjacent colors.

/* Compliant Focus Ring */
:focus-visible {
  outline: 2px solid var(--accent-cyan, #06b6d4);
  outline-offset: 3px;
}

2. Target Size (WCAG 2.5.8 - Level AA)

The size of the target for pointer inputs must be at least 24 by 24 CSS pixels, except where the target is in a sentence or inline text. On touch devices, Rogabot recommends a minimum of 44 by 44 CSS pixels.

3. Consistent Help (WCAG 3.2.6 - Level A)

If a web page provides help mechanisms (such as contact information, chat widgets, or FAQ links), they must be presented in the same relative order and location across all pages in the set.

4. Redundant Entry (WCAG 3.3.7 - Level A)

Information previously entered by or provided to the user in a multi-step process must either be auto-populated or available for the user to select, eliminating repetitive typing.

5. Accessible Authentication (WCAG 3.3.8 - Level AA)

Authentication processes must not rely solely on cognitive function tests (such as memorizing passwords or solving puzzle CAPTCHAs) without providing an accessible alternative (such as password autofill, copy-paste support, WebAuthn/passkeys, or email magic links).