WCAG 2.2 vs. 2.1: what's actually new, and does it change what Cluesia checks

WCAG 2.2 became a W3C Recommendation — the formal, finished version of the standard — on 5 October 2023. If you've seen "WCAG 2.2" mentioned alongside "WCAG 2.1" and weren't sure which one actually applies to you, here's the short version: for EAA compliance today, WCAG 2.1 AA is still the operative baseline, and that's not a mistake or an oversight.

What's new in WCAG 2.2

WCAG 2.2 adds 9 new success criteria on top of WCAG 2.1's 78, and removes one that's no longer needed — 4.1.1 Parsing, which required HTML to be free of major markup errors. That criterion existed because older assistive technology was fragile against malformed markup; modern browsers and screen readers handle it well enough that the W3C's own working group judged it obsolete.

The 9 additions are mostly about making interactive elements more predictable and easier to operate, not introducing entirely new categories of accessibility work:

• Focus Not Obscured (two levels) — a focused element shouldn't be hidden behind a sticky header, cookie banner, or other overlapping content.
• Focus Appearance — a visible focus indicator needs a minimum size and contrast, not just "some kind of outline."
• Dragging Movements — anything operated by a drag gesture needs a single-pointer alternative (a button, not just click-and-drag).
• Target Size (Minimum) — clickable/tappable targets need a minimum size, so a small icon button isn't unusably fiddly.
• Consistent Help — if a help mechanism (chat, contact link, FAQ) appears on multiple pages, it needs to stay in the same relative place.
• Redundant Entry — don't make someone re-enter information they already gave you earlier in the same process.
• Accessible Authentication (two levels) — login shouldn't require a cognitive test (like solving a puzzle) with no other way to authenticate.

None of these are exotic. If your site already handles focus states, target sizing, and form design carefully, you're likely closer to WCAG 2.2 AA than you'd guess.

Why WCAG 2.1 AA is still the standard that matters right now

The EAA's technical standard is EN 301 549, and the version currently in force — V3.2.1 — incorporates WCAG 2.1 AA, not 2.2. Cluesia's scanner checks against that same version, for the same reason: it's the version an EU regulator or a national enforcement body will actually be checking your site against today. Scanning for a newer version that isn't yet the legally operative one wouldn't tell you anything useful about your current obligation.

When EN 301 549 V4.1.1 — the version expected to incorporate WCAG 2.2 — is formally adopted, Cluesia's versioned standards data updates to match, and every future scan checks against the new baseline automatically. That's a data change on our side, not something that requires you to do anything differently in the meantime.

What this means for you today

Keep meeting WCAG 2.1 AA — that's your real, current obligation under the EAA. If you're building new features now, it costs very little to also follow WCAG 2.2's guidance on focus visibility and target size, since both are genuinely good UX practices independent of any specific compliance deadline. But don't let "WCAG 2.2 is out" create urgency that doesn't actually exist yet for EAA purposes.

Want to see exactly where your site stands against the current standard? Check your website for a free first look, or see pricing for a full audit.