WCAG 2.2 is the current version of the Web Content Accessibility Guidelines — the technical standard that defines what an accessible website looks like. Courts use WCAG 2.1 Level AA as their benchmark when evaluating ADA web accessibility claims against private businesses. WCAG 2.2 is the current best practice that goes further. Here is what both versions actually require, in plain language.
WCAG stands for Web Content Accessibility Guidelines. They are published by the World Wide Web Consortium (W3C) — the international standards body for the web. WCAG is not a law itself, but it is the technical measuring stick that courts, regulators, and accessibility auditors apply when determining whether a website meets ADA obligations.
The guidelines are organized around three conformance levels — A (minimum), AA (the standard most businesses target), and AAA (enhanced, generally not required). When someone refers to “WCAG compliance” in a business or legal context, they almost always mean Level AA conformance.
Every success criterion in WCAG maps back to four principles. These are worth knowing because they explain why the requirements exist, not just what they are.
Perceivable
Visitors must be able to perceive all content on your site, regardless of their sensory abilities. This is the principle behind alt text for images (blind users cannot see them), captions for video (deaf users cannot hear the audio), and color contrast requirements (low-vision users cannot read text that blends into the background).
Operable
Visitors must be able to operate and navigate your site using whatever input method works for them. This covers keyboard navigation (users who cannot use a mouse), skip navigation links, and time limits on interactive elements. If a user cannot tab through your checkout process, your site fails this principle.
Understandable
Content and navigation must be clear and predictable. Forms need to tell users what went wrong and how to fix it. Pages need to behave consistently. Labels need to clearly describe what input is required. This principle is especially relevant for users with cognitive disabilities.
Robust
Content must work reliably across different browsers, devices, and assistive technologies — including screen readers like JAWS and NVDA. Proper use of HTML and ARIA attributes is the foundation of robustness.
WCAG 2.2 adds nine new success criteria beyond WCAG 2.1. Four of them apply at Level AA — the level most businesses need to target. Here is what each one means in practice:
When a user navigates your site by keyboard, the element that currently has focus must be at least partially visible. Sticky headers and fixed footers frequently hide the focused element behind their own content. If a keyboard user cannot see what they have focused on, they cannot navigate.
Any function that requires a user to click and drag — sorting lists, sliders, carousels — must also have a non-dragging alternative. This supports users with motor impairments who cannot perform precise drag gestures. Adding button-based controls alongside drag interfaces is the standard fix.
Interactive elements like buttons and links must have a minimum touch/click target of 24x24 CSS pixels. This was previously only required at the AAA level. The practical impact is on small icon buttons, closely spaced navigation items, and links packed tightly together in mobile layouts.
Login and authentication processes must not require users to complete a cognitive function test — like solving a puzzle or transcribing distorted characters — without offering an alternative. Password manager support, magic links, and passkeys all satisfy this criterion. Standard CAPTCHAs often do not.
For private businesses, WCAG 2.1 Level AA is the current court benchmark for ADA compliance. For state and local governments, WCAG 2.1 Level AA is the formally mandated standard under the DOJ’s 2024 Title II rule.
WCAG 2.2 is backward compatible — every 2.1 success criterion is retained in 2.2 (except 4.1.1 Parsing, which was removed because modern browsers handle it automatically). Meeting WCAG 2.2 AA means meeting WCAG 2.1 AA. The W3C recommends organizations adopt 2.2 as their target even when regulatory obligations reference 2.1.
For a deeper look at what the law requires and how courts apply these standards, see our guide to ADA website compliance requirements for US businesses.
For a practical way to add support for contrast, alt text, font controls, and more without touching your code, explore web accessibility solutions built for WordPress and Shopify.
