WCAG 2.2 Updates: What's New?

WCAG 2.2 Updates: Transitioning to Modern Inclusive Standards

In October 2023, the W3C (World Wide Web Consortium) officially released WCAG 2.2. This update does not remove the standards from WCAG 2.0 or 2.1; it is fully backwards compatible, with one major exception. This update is heavily focused on improving the experience for three specific groups: mobile device users, users with visual impairments (Low Vision), and users with cognitive disabilities.

This article technically dissects these new elements, extracted specifically from the comprehensive guide Web Accessibility: WCAG 2.2 made easy by Olga Revilla.

1. The Death of Criterion 4.1.1 (Parsing)

The most radical change in WCAG 2.2 is not what was added, but what was removed. Success criterion 4.1.1 (Parsing) is now officially Obsolete.

In the era of WCAG 2.0, HTML was highly unstable. Browsers could "break" (fail to render) just because a developer forgot to close a <div> tag or used a duplicate ID attribute. However, modern browsers (Chrome, Firefox, Safari) and the HTML5 specification are now incredibly sophisticated at automatically correcting syntax errors (error handling).

Olga Revilla asserts that modern Assistive Technologies (Screen Readers) rely on the Accessibility Tree built by the browser, not on the raw HTML parsing. Therefore, parsing errors no longer have a direct impact on accessibility, and 4.1.1 was finally retired.

WCAG 2.2 introduces much stricter rules regarding the visibility of the focus indicator (keyboard cursor).

2.4.11 Focus Not Obscured (Minimum) - Level AA

Have you ever pressed the `Tab` key, only for your focus indicator to disappear behind a Sticky Header or a floating Cookie Banner? This criterion prohibits that. If an element receives keyboard focus, it must not be entirely hidden by other content.

2.4.12 Focus Not Obscured (Enhanced) - Level AAA

Similar to 2.4.11, but at the AAA level, the focused element must not be obscured at all (even partially) by any other element.

2.4.13 Focus Appearance - Level AAA

This establishes a mathematical standard for the focus indicator. The focus indicator must have a contrast ratio of at least 3:1 against adjacent pixels, and its thickness must be at least a 2 CSS pixel solid perimeter. The best approach is simply using `outline: 2px solid [contrasting-color]`.

3. Pointer Interaction Accuracy (Target Size & Dragging)

2.5.7 Dragging Movements - Level AA

Users with motor disabilities (such as Parkinson's) find it extremely difficult to perform click-and-hold drag movements. This criterion mandates that any dragging operation must have a simple click alternative (e.g., up/down arrow buttons to move an item in a list, or a click button to open a file picker interface).

2.5.8 Target Size (Minimum) - Level AA

Tiny buttons on touch devices are a nightmare. This new criterion dictates that every interactive click target must have a minimum size of 24 x 24 CSS pixels. If the visual button is smaller, you must add transparent padding so the total clickable area meets this requirement, preventing misclicks.

4. Cognitive Protection (Accessible Authentication & Redundant Entry)

The largest area of updates is aimed at reducing the mental (Cognitive) load of users.

3.2.6 Consistent Help - Level A

If your site has a Help page (like an FAQ, Live Chat, or contact number), the link to that help must be in the same visual location on every page (e.g., always in the bottom right corner).

3.3.7 Redundant Entry - Level A

Users with memory impairments will be highly frustrated if they have to type the same information repeatedly. If a user has already entered their "Shipping Address" on the first page of checkout, do not force them to retype their "Billing Address" on the second page if the data is the same. Provide a "Same as Shipping Address" checkbox.

3.3.8 Accessible Authentication (Minimum) - Level AA

Forcing a user to memorize a complex password or transcribe a 6-digit TOTP code from their phone to their laptop within 30 seconds (a Cognitive Test) is now prohibited. The system must allow alternative methods, such as: - Allowing Copy-Paste features for passwords. - Supporting Password Managers (Autofill). - Offering biometric recognition (Fingerprint/FaceID). - Using single-use login links (Magic Links via email).

5. Conclusion

The WCAG 2.2 update is not just "extra homework" for developers. These new criteria, specifically Accessible Authentication and Target Size, are modern UX best practices that will directly improve conversion rates and comfort for all your users.

References

The analysis of the new success criteria (SC) above is extracted purely from the dedicated chapter The WCAG 2.2 Additions in the literature Web Accessibility: WCAG 2.2 made easy by Olga Revilla. The in-depth explanation regarding the retirement of SC 4.1.1 (Parsing) and the mathematical metrics of Target Size Minimum refer entirely to the technical documentation from that author.