Loading content...
Loading content...
Last Updated: January 2025
Learn what's new in WCAG 2.2, how it differs from WCAG 2.1, and what you need to know to upgrade.
WCAG 2.2 introduces 9 new success criteria addressing mobile accessibility, focus visibility, and cognitive accessibility.
When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.
When a user interface component receives keyboard focus, no part of the component is hidden by author-created content.
When the keyboard focus indicator is visible, an area of the focus indicator meets specific size and contrast requirements.
All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential.
Targets have a size of at least 24 by 24 CSS pixels, except where the target is available through an equivalent link or control on the same page that is at least 24 by 24 CSS pixels.
If a Web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple Web pages within a set of Web pages, they occur in the same relative order on each page.
Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated or available for the user to select.
A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of: a mechanism to assist the user, an alternative authentication method, or a mechanism is available to turn off the cognitive function test.
A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of: a mechanism to assist the user, an alternative authentication method, or a mechanism is available to turn off the cognitive function test.
Status: This success criterion has been deprecated in WCAG 2.2 and is no longer required for conformance.
Why it was deprecated: Modern HTML parsers automatically handle well-formed markup, making this criterion obsolete. The requirement was originally intended to ensure that assistive technologies could parse content correctly, but modern browsers and assistive technologies handle malformed HTML gracefully.
What this means: You no longer need to ensure that HTML elements have complete start and end tags, are nested according to their specifications, and don't contain duplicate attributes. However, it's still good practice to write valid HTML for maintainability and performance.
Note: While 4.1.1 is deprecated, you should still follow HTML best practices. Valid HTML improves code maintainability, performance, and reduces potential issues with assistive technologies.
| Feature | WCAG 2.1 | WCAG 2.2 |
|---|---|---|
| Total Success Criteria | 78 | 87 (9 new, 1 deprecated) |
| New Criteria | - | 9 new criteria |
| Deprecated Criteria | - | 4.1.1 (Parsing) |
| Focus Areas | Desktop, keyboard, screen readers | + Mobile, low vision, cognitive |
| Backward Compatible | Yes (with 2.0) | Yes (with 2.1) |
| Published | June 2018 | October 2023 |
If your site is already WCAG 2.1 compliant, here's what you need to do: