WCAG 2.2 Added 9 New Rules: Here's What Actually Changed for Your Site

ClearPath Team · 2026-07-18 · 7 min read

If your last accessibility audit happened before 2023, it's working from an outdated rulebook. WCAG 2.2 was published as a W3C Recommendation on October 5, 2023, and it's now the version accessibility professionals point to when they talk about "current" standards. Most business owners never heard about the update because nothing dramatic happened. No press release, no deadline, no big announcement. Just nine new rules quietly added to a document most people never read.

That's the problem. Agencies and small business owners keep building sites to a standard that's already one step behind, and a lot of the new criteria hit exactly the parts of a site that get the most complaints: login screens, checkout flows, and anything with drag-and-drop.

What actually changed

WCAG 2.2 didn't rewrite the rulebook. It builds on 2.1 and 2.0, so if you already meet those, you're most of the way there. The change is additive: nine new success criteria were introduced, and one old one (4.1.1 Parsing, a technical HTML rule that modern browsers made obsolete) was retired. As one source puts it, "Released in October 2023, WCAG 2.2 builds upon version 2.1 by adding 9 new criteria while removing one (4.1.1 Parsing), bringing the total from 78 to 87 testable requirements."

Six of the nine new criteria live at Level AA, which is the level most legal and regulatory frameworks actually reference. That matters because Level AA is the standard for most legal compliance requirements. In other words, this isn't an academic exercise. If your compliance target is AA (and it should be), you now have six new boxes to check that weren't there a couple years ago.

The new rules, in plain language

Here's the full list, without the spec-speak:

• Focus Not Obscured (Minimum), Level AA: When someone tabs to a button or link with their keyboard, at least part of it needs to stay visible. Sticky headers, cookie banners, and chat widgets are the usual culprits here, since they love to sit right on top of the thing a keyboard user just tabbed to.
• Focus Appearance, Level AAA: Your focus outline needs to actually be visible: thick enough and contrasty enough that people with low vision can tell where they are on the page. ClearPath includes a focus outline tool that visitors can turn on themselves, which helps in the moment even before your own CSS is updated.
• Dragging Movements, Level AA: Anything that relies on drag-and-drop (reordering a list, adjusting a slider, moving a card between columns) needs a single-click or tap alternative. If the user clicks or taps the list item, you can provide up and down arrows that let them move it instead. Someone with hand tremors or limited fine motor control may never be able to drag precisely enough otherwise.
• Target Size (Minimum), Level AA: Clickable buttons and links need to be at least 24 by 24 CSS pixels, or have enough spacing around them so people don't accidentally hit the wrong one. This one alone fixes a huge chunk of mobile usability complaints. ClearPath's widget lets visitors enlarge clickable areas on the fly, though that's a visitor-side workaround and not a substitute for fixing the actual button sizes in your code.
• Consistent Help, Level A: If you offer a help link, chat widget, or contact info on multiple pages, keep it in the same spot every time. Simple rule, easy to break the moment marketing redesigns one landing page.
• Redundant Entry, Level A: Don't make people re-type information they already gave you in the same session. Multi-step checkout forms are the biggest offender.
• Accessible Authentication (Minimum), Level AA: Login and signup can't require a "cognitive function test," like solving a puzzle or remembering a password with no help, unless there's an alternative or some support mechanism. Think password managers, paste-friendly password fields, and email magic links.

For everyday e-commerce and SaaS sites, two of these carry the most weight. As one accessibility testing firm points out, "Target Size and Redundant Entry affect the most users on typical websites." That tracks. Almost every site has small tap targets somewhere, and almost every checkout asks for the same email address or address twice.

Why this matters even if no law names it yet

Right now, most legal frameworks still point to WCAG 2.1. The ADA's Title II rule and the European standard EN 301 549 both currently reference 2.1, not 2.2. But that's expected to change. W3C's own guidance notes that most organizations addressing the European Accessibility Act use WCAG alongside EN 301 549, which currently uses WCAG 2.1, though the next version of EN 301 549 is expected to use the latest WCAG 2.2. Building to 2.2 now means you're not scrambling to retrofit checkout flows and login forms later. There's also a practical reason that has nothing to do with law: these criteria exist because real people run into real walls. WCAG 2.2's new success criteria address real accessibility gaps, issues that users with disabilities encounter daily but previous guidelines didn't explicitly require fixing. A sticky "add to cart" bar that covers your keyboard focus, or a checkout that makes someone re-enter their shipping address three times, isn't just a technical failure. It's friction that costs you a sale.

Where to start

You don't need to fix all nine criteria in one sprint. Prioritize based on impact:

1. Audit your checkout and signup flows for redundant data entry and login "puzzles."
2. Check tap target sizes on mobile, especially in nav menus and product cards.
3. Tab through your site with a keyboard only and watch for anything that disappears under a sticky header or popup.
4. Find every drag-and-drop interaction and ask whether it has a click-based backup.

Most of these are design and front-end decisions, not massive rebuilds. That's actually good news. It's worth noting that most of the new criteria are best addressed during design, rather than later in development or testing, which means the earlier your team catches these, the cheaper they are to fix. While you work through that list, ClearPath can give visitors some relief today by installing with a single line of code and generating an accessibility statement for your site automatically.

WCAG 2.2 isn't a dramatic overhaul, and that's exactly why it's easy to miss. But nine new rules, most of them aimed at forms, focus, and touch targets, are quietly becoming the baseline everyone else is expected to hit. Getting ahead of it now costs a lot less than catching up later.