# WCAG 2.1 vs. 2.2: What Changed and What to Do

Source: https://allyway.ai/glossary/wcag-2-1-vs-2-2

WCAG 2.1 vs. 2.2 compares two versions of the Web Content Accessibility Guidelines. WCAG 2.2, published on 5 October 2023, keeps the 2.1 criteria, adds nine new success criteria and makes 4.1.1 Parsing obsolete.

WCAG 2.1 vs. 2.2 is a question most teams face when they update an audit, a contract or an accessibility statement. The short answer: WCAG 2.2 contains almost everything from WCAG 2.1, adds nine new success criteria and drops one obsolete criterion, 4.1.1 Parsing. Because the versions are backwards compatible, a site that meets WCAG 2.2 also meets 2.1. For the full overview of the current version, see our [WCAG 2.2 guide](https://allyway.ai/regulations/wcag-2-2).

## What it means

[WCAG](https://allyway.ai/glossary/wcag) 2.1 was published on 5 June 2018, WCAG 2.2 on 5 October 2023. According to the [W3C WCAG overview](https://www.w3.org/WAI/standards-guidelines/wcag/), content that conforms to WCAG 2.2 also conforms to WCAG 2.1 and 2.0, and W3C encourages using the latest version. The nine additions, listed on W3C's [What's New in WCAG 2.2](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/):

| Success criterion | Level | In short |
|---|---|---|
| 2.4.11 [Focus Not Obscured (Minimum)](https://allyway.ai/glossary/focus-not-obscured) | AA | The focused element is not entirely hidden by sticky headers or banners |
| 2.4.12 Focus Not Obscured (Enhanced) | AAA | No part of the focused element is hidden |
| 2.4.13 Focus Appearance | AAA | The focus indicator is large enough and has enough contrast |
| 2.5.7 [Dragging Movements](https://allyway.ai/glossary/dragging-movements) | AA | Anything done by dragging also works with single clicks or taps |
| 2.5.8 [Target Size (Minimum)](https://allyway.ai/glossary/target-size) | AA | Targets are at least 24 × 24 CSS pixels, with exceptions |
| 3.2.6 [Consistent Help](https://allyway.ai/glossary/consistent-help) | A | Help options appear in the same relative order on each page |
| 3.3.7 [Redundant Entry](https://allyway.ai/glossary/redundant-entry) | A | Information already entered is not requested again in the same process |
| 3.3.8 [Accessible Authentication (Minimum)](https://allyway.ai/glossary/accessible-authentication) | AA | Login does not depend on a cognitive function test such as remembering a password, unless there is help |
| 3.3.9 Accessible Authentication (Enhanced) | AAA | The same, with fewer exceptions |

The one change that breaks the rule "nothing old changes": **4.1.1 Parsing** is obsolete and removed from WCAG 2.2. Notes added to WCAG 2.1 and 2.0 explain how to treat it there.

Counted by level, WCAG 2.1 has 78 success criteria (30 A, 20 AA, 28 AAA). WCAG 2.2 has 86 (31 A, 24 AA, 31 AAA): 78 plus nine new, minus 4.1.1.

> **Note:** > **What laws refer to**
> [EN 301 549](https://allyway.ai/glossary/en-301-549) V3.2.1, the harmonised standard in the EU, is based on WCAG 2.1; according to W3C, the 2026 version of EN 301 549 uses WCAG 2.2. WCAG 2.2 is also an ISO standard, ISO/IEC 40500:2025. Building for 2.2 AA covers both.

## Examples

Two of the new AA criteria often need CSS changes. Make icon buttons large enough and keep the focused element visible below a sticky header:

```html title="Example"
<style>
  /* 2.5.8 Target Size (Minimum) */
  .icon-button { min-width: 24px; min-height: 24px; }
  /* 2.4.11 Focus Not Obscured: leave room for a 64px sticky header */
  html { scroll-padding-top: 64px; }
</style>
<button class="icon-button" aria-label="Close">×</button>
```

**Do:** Do

Target WCAG 2.2 AA in new projects, contracts and statements, test the six new A and AA criteria explicitly and keep valid HTML as good practice even without 4.1.1.

**Don't:** Don't

Assume a WCAG 2.1 audit covers 2.2, or claim WCAG 2.2 conformance without testing focus visibility, target size, dragging and login flows.

## How to move from WCAG 2.1 to 2.2



## Questions

Q: What is the difference between WCAG 2.1 and 2.2?
A: WCAG 2.2 adds nine success criteria – two at level A, four at AA and three at AAA – and makes 4.1.1 Parsing obsolete. All other criteria of WCAG 2.1 are unchanged.

Q: Is WCAG 2.2 backwards compatible with WCAG 2.1?
A: Yes. According to W3C, content that conforms to WCAG 2.2 also conforms to WCAG 2.1 and 2.0.

Q: Why was 4.1.1 Parsing removed in WCAG 2.2?
A: According to the W3C Understanding page, assistive technologies no longer parse HTML themselves – browsers do, and they handle parsing errors much better. Issues that still matter now fail 1.3.1 Info and Relationships or 4.1.2 Name, Role, Value.

Q: WCAG 2.1 vs. 2.2: which version should I use?
A: W3C encourages the latest version. Even where a law or standard still references 2.1, meeting WCAG 2.2 AA covers 2.1 AA as well.

Q: How do I check my site against WCAG 2.2?
A: Combine automated and manual testing. The [free WCAG scanner](https://allyway.ai/free-wcag-accessibility-scanner-for-websites) checks a page against WCAG 2.2 AA in seconds.
