WCAG 2.2 became official in October 2023. If your accessibility program is still on 2.1, you’re already a version behind — and that gap matters.
The Web Content Accessibility Guidelines are the global standard for digital accessibility. Here in the US, they’re the primary framework referenced in ADA Title III lawsuits and the technical basis for Section 508 federal compliance. When a business gets sued over website inaccessibility, WCAG conformance is the first thing a plaintiff’s attorney asks about.
WCAG 2.2 AA is now the compliance target. Here’s what changed — and what your website needs to address.
What Was Added in WCAG 2.2
WCAG 2.2 introduced nine new success criteria. Six of them are required at Level AA. These aren’t optional nice-to-haves. They’re the baseline for legal defensibility.
2.4.11 Focus Not Obscured (Minimum). Keyboard focus indicators can’t be completely hidden by sticky headers, banners, or overlapping elements. Users navigating by keyboard need to see which element is actually focused. It sounds obvious until you’re testing a site with a massive sticky header that eats the top 200 pixels.
2.4.12 Focus Appearance (Minimum). The focus indicator — that outline showing which element is selected via keyboard — now has minimum size and contrast requirements. Thin or low-contrast outlines won’t cut it anymore.
2.5.3 Target Size (Minimum). Interactive elements like buttons, links, and form controls need a minimum target area of 24×24 CSS pixels. This sounds small until you’re testing on mobile or working with a user who has tremor or limited fine motor control.
3.2.6 Consistent Help. If your website offers help mechanisms — chat, contact info, help links — they need to show up consistently in the same location across pages. No exceptions.
3.3.7 Redundant Entry. Users shouldn’t have to re-enter information they’ve already provided in the same session. It reduces cognitive load, especially for users with memory or attention disabilities.
3.3.8 Accessible Authentication (Minimum). Login and authentication processes can’t require users to solve cognitive tests like CAPTCHAs without providing an accessible alternative.
What Was Removed
WCAG 2.2 deprecated Success Criterion 4.1.1 Parsing — which required valid, well-formed HTML. Modern browsers handle HTML parsing errors automatically now, making this criterion redundant. If your accessibility documentation still references 4.1.1, update it.
What This Means for Your Website Right Now
Here’s what we see consistently in audits: over 70% of SMB websites we’ve audited still have at least one WCAG 2.2-specific failure, even when they’ve been previously audited against 2.1. That gap isn’t small.
If your site was built or last audited against WCAG 2.1 AA, you’ve probably got gaps in at least three of these six new criteria. The most common issues we see in the field:
Focus indicators are still the thin default browser outline — they fail the new appearance requirements.
Mobile navigation menus and sticky headers obscure focused elements when you’re keyboard navigating.
Login forms use standard CAPTCHA with no accessible alternative.
Small icon-only buttons fall below the 24x24px minimum target size.
A Quick Self-Check
Open your website. Press Tab to navigate without using your mouse. That’s it. Ask yourself a few questions:
Can you see clearly which element is currently focused? At all times?
Does the focus indicator have a visible outline with adequate contrast against both the element and the background?
Can you interact with every button, link, and form using only the keyboard?
Does your login process work without requiring you to identify distorted images or sounds?
If any of these fail, you’ve got WCAG 2.2 AA gaps that need fixing.
The Bigger Picture
WCAG 2.2 isn’t the end of the road. WCAG 3.0 is in active development, though widespread adoption is still years out. Right now, 2.2 AA is the compliance target and the defensible standard. Organizations building programs against 2.2 today will adapt faster when the next version lands.
Accessibility compliance isn’t a checkbox. It’s an ongoing operational function. The businesses that treat it that way? They rarely get sued.
Staying current with WCAG 2.2 AA requires more than a one-time fix — it requires ongoing monitoring as your site evolves. Bixli’s Fractional Accessibility Services provide consistent compliance oversight without the overhead of a full-time hire. We keep your digital properties current so you’re not scrambling after a complaint. Find us on our Accessibility Base profile.