WCAG 2.1 vs WCAG 2.2: What has changed?
Last updated:
What is WCAG 2.2?
The Web Content Accessibility Guidelines (WCAG) 2.2 is the latest version of the international standard for web accessibility at the time of writing, published by the W3C on October 5, 2023. WCAG 2.2 builds directly on WCAG 2.1 — every success criterion from 2.1 is included in 2.2, with one exception.
WCAG 2.2 is structured around the same four principles as earlier versions: websites must be Perceivable, Operable, Understandable, and Robust (POUR).
What changed from WCAG 2.1 to 2.2?
The differences between WCAG 2.1 and WCAG 2.2 are:
- 9 new success criteria were added — 2 at Level A, 4 at Level AA, and 3 at Level AAA.
- 1 success criterion was removed — 4.1.1 Parsing, which was deprecated because modern browsers handle the underlying issues well enough.
- All WCAG 2.1 criteria are still present in WCAG 2.2 (except 4.1.1), so any site that meets WCAG 2.1 AA is close to WCAG 2.2 AA — it needs to satisfy the 2 new Level A and 4 new Level AA criteria. For government websites or others targeting Level AAA, there are 3 additional new AAA criteria to address.
New success criteria in WCAG 2.2
The following success criteria are new in WCAG 2.2, listed in order from the W3C specification. Criteria at Level A and AA are required for WCAG 2.2 Level AA compliance.
2.4.11 Focus Not Obscured (Minimum) — AA
When a component receives keyboard focus, it must not be entirely hidden by overlapping page content. Sticky headers, sticky footers, cookie banners, and non-modal dialogs are common examples of content that can obscure a focused component. Users need to see the active element to understand their current position on the page.
2.4.12 Focus Not Obscured (Enhanced) — AAA
Where 2.4.11 allows a focused component to be partially visible, 2.4.12 requires the entire component to be visible when it receives focus. No part of it may be hidden by overlapping page content.
2.4.13 Focus Appearance — AAA
The goal of this criterion is to ensure the focus indicator is clearly visible. The focus area must enclose the component, have a contrast ratio of at least 3:1 between focused and unfocused states, and not be fully obscured by other content.
2.5.7 Dragging Movements — AA
Any action that requires dragging must also be achievable with a single click or tap. Reordering items or adjusting a slider are examples of actions that must have this alternative. This makes these interactions accessible to users who cannot perform precise dragging gestures.
2.5.8 Target Size (Minimum) — AA
Interactive targets (buttons, links, form controls) must be at least 24×24 CSS pixels. Exceptions apply when targets are inline within text, or when the spacing between targets compensates for a smaller size.
3.2.6 Consistent Help — A
Help mechanisms must appear in the same location on every page where they are present. Examples are a phone number, a chat widget, or a link to an FAQ. Consistent placement helps users find support more easily.
3.3.7 Redundant Entry — A
Information a user has already entered must not be asked again in the same process. Re-entry is only allowed when it is essential, such as confirming a password. This reduces the effort required to complete multi-step forms.
3.3.8 Accessible Authentication (Minimum) — AA
Login forms must not require users to solve a cognitive test to authenticate. Transcribing characters, solving puzzles, and recognizing images are examples of such tests. An alternative method must be provided if a cognitive test is used. Password managers and copy-paste must not be blocked.
3.3.9 Accessible Authentication (Enhanced) — AAA
Where 3.3.8 allows a cognitive test if an alternative is provided, 3.3.9 does not allow a cognitive test at all. No exceptions are made. Check your WCAG 2.2 compliance
Removed: 4.1.1 Parsing
WCAG 2.1 included 4.1.1 Parsing, which required HTML to have no duplicate IDs, unclosed elements, or other markup errors that could confuse assistive technologies.
This criterion was removed in WCAG 2.2 because modern browsers and assistive technologies now handle malformed markup well enough.
Is it good practice to use WCAG 2.2?
Yes. WCAG 2.2 includes all WCAG 2.1 success criteria, except the removed 4.1.1 Parsing. Testing against WCAG 2.2 is a good practice. If your website passes WCAG 2.2, it also passes WCAG 2.1.
Use an automated accessibility checker to identify which WCAG 2.2 criteria your site already meets and which gaps remain.
Conclusion
WCAG 2.2 is a backwards-compatible update to WCAG 2.1. It adds 9 new success criteria and removes one (4.1.1 Parsing). Of the new criteria, 2 are at Level A, 4 at Level AA, and 3 at Level AAA. A website that already meets WCAG 2.1 AA needs to address 6 additional criteria to reach WCAG 2.2 AA.
It is good practice to test against WCAG 2.2 directly. A passing result covers both WCAG versions at once.
As the founder of ExcellentWebCheck, I'm very passionate about accessibility and ensuring equal access to information and services online. With the current speed of digitalization, it is crucial to make sure that everyone has access to important goods and services such as healthcare, financial services, education, and government resources, regardless of their abilities.