WCAG 2.2 Level AA is the middle conformance tier of the Web Content Accessibility Guidelines (WCAG) — the technical standard, published by the W3C, that defines what an accessible website looks like in practice. Level A is the bare minimum, Level AAA is aspirational, and Level AA sits in between: rigorous enough to make a site genuinely usable by people with disabilities, practical enough to achieve on a real budget. It is the level courts, the U.S. Department of Justice, and the European Union all point to — when a demand letter or settlement mentions an "accessible website," WCAG Level AA is the measuring stick.
What do the three WCAG conformance levels mean?
WCAG organizes its requirements into testable rules called success criteria, each assigned one of three levels:
- Level A — the floor. Images with no text alternative, video without captions, or pages a keyboard cannot operate all fail Level A.
- Level AA — everything in Level A plus the criteria that remove the most common barriers: sufficient color contrast, visible keyboard focus, consistent navigation, clear form errors.
- Level AAA — aspirational. Some AAA criteria are impractical for most organizations; even the W3C does not recommend requiring it site-wide.
Versions matter too. WCAG 2.0 dates to 2008, WCAG 2.1 to 2018, and WCAG 2.2 became the current W3C Recommendation on October 5, 2023, adding nine success criteria. WCAG 3.0 exists only as an early draft — years away from being a requirement anywhere. ADA Fail audits against WCAG 2.2 AA: the newest stable version, at the level the law cares about.
What does WCAG 2.2 Level AA actually require?
The full standard runs to dozens of criteria; a few examples show how concrete and testable they are:
- Color contrast: at least 4.5:1 for normal text, 3:1 for large text, and 3:1 for buttons, icons, and form-field borders.
- Captions: prerecorded video needs captions at Level A; live captions and audio description land at AA.
- Keyboard access: everything must work with a keyboard alone, with a visible indicator showing which element has focus.
- Forms: every field needs a programmatic label, and errors must be identified in text — not just a red outline.
- New in 2.2: touch targets of at least 24×24 CSS pixels, alternatives to drag-and-drop gestures, and login flows that do not force users to solve puzzles or transcribe codes.
Each of those maps to a real person who otherwise cannot use your site — and over 1 in 4 U.S. adults live with a disability (CDC). The nine new criteria are covered in what changed in WCAG 2.2; the official text lives at the W3C's WCAG 2.2 Recommendation.
Why do courts keep citing WCAG Level AA?
Here is the odd part: for private businesses, no federal regulation names a web standard at all. ADA Title III requires places of public accommodation to be accessible, and the DOJ's longstanding position — backed by most courts — is that business websites are covered — but the statute never says how. Courts and plaintiffs' lawyers needed a yardstick, and WCAG AA became it.
National Federation of the Blind v. Target settled in 2008 with a $6 million class fund plus a remediation commitment. Robles v. Domino's Pizza (9th Cir. 2019; the Supreme Court declined review) confirmed that the ADA reaches a website and app connected to physical locations. In settlement after settlement since, WCAG AA is the standard defendants agree to meet.
Regulators then made it official where they could:
- The DOJ's Title II rule, published April 24, 2024, adopts WCAG 2.1 AA for state and local government websites and mobile apps — the first time WCAG appears in a binding federal regulation. In April 2026 the DOJ extended the compliance deadlines to April 26, 2027 for entities serving 50,000+ people and April 26, 2028 for smaller ones. Details in the DOJ web accessibility rule, explained.
- The European Accessibility Act, enforceable since June 28, 2025, covers services sold to EU consumers — explicitly including e-commerce — via a technical standard that incorporates WCAG 2.1 AA. US companies selling into the EU are in scope.
- California's Unruh Act attaches minimum statutory damages of $4,000 per violation to any ADA violation, which is a major reason California website demand letters are so common.
The pressure is not hypothetical. More than 5,000 digital-accessibility lawsuits were filed in 2025, up roughly 20% over 2024 — and when settlements specify a technical target, it is WCAG AA.
Does meeting Level AA make a site "ADA compliant"?
Be careful with that phrase. Because no federal Title III regulation defines web compliance for private businesses, nobody can honestly certify a business website as "ADA compliant" — not a tool, not a widget, not an agency. What WCAG 2.2 AA conformance does is put a business in the strongest defensible position: it is the benchmark every court, regulator, and settlement references.
Getting there takes more than software. Automated scanning can detect only roughly a third of WCAG success criteria; the rest — keyboard traps, focus order, meaningful alt text, screen-reader usability — need human testing. That is why "passes automated scans" and "conforms to WCAG 2.2 AA" are very different claims — and the gap between them is where most sites quietly fail: WebAIM's 2025 million-homepage analysis found detectable WCAG failures on 94.8% of the top one million homepages, led by low-contrast text, missing image alt text, missing form labels, and empty links and buttons.
How do you find out where your site stands?
Start with a real audit, not a promise. A meaningful WCAG 2.2 AA assessment combines an automated scan — which catches the machine-detectable third — with expert human testing: keyboard-only navigation, screen-reader passes, and the judgment calls a scanner cannot make. ADA Fail's free accessibility audit covers the automated layer and flags where human review is needed — a concrete picture of your exposure before you spend a dollar.
Whatever you do, skip the shortcuts. Overlay scripts sold as one-line compliance fixes do not deliver WCAG conformance: the FTC fined overlay vendor accessiBe $1 million (announced January 3, 2025) over exactly that kind of claim, and UsableNet keeps finding hundreds of companies sued each year with a widget or overlay already installed. The distinction that matters: a user-facing preference widget — contrast and text-size controls on a site that is already accessible at the code level, making no compliance claims — is fine, and ADA Fail's own site runs one. The problem is the compliance claim, not the preference button. More in accessibility widget vs. overlay.
WCAG Level AA is not legal trivia — it is the standard your site will be measured against, whether by a regulator, a plaintiff's lawyer, or a customer who simply cannot check out. Find out where you stand: request a free accessibility audit from ADA Fail and get a plain-English report of what passes, what fails, and what to fix first.
Frequently asked questions
Is WCAG Level AA legally required for private businesses in the United States?
Not by explicit regulation — ADA Title III has no formal web standard for private businesses. But the DOJ's position and most court decisions treat business websites as covered by the ADA, and WCAG AA is the de facto benchmark in demand letters and settlements. In practice, WCAG 2.2 AA conformance is how a business demonstrates accessibility — no competing standard exists.
Should a site target WCAG 2.1 AA or 2.2 AA?
Target 2.2 AA. WCAG versions are backward-compatible, so a site that conforms to 2.2 AA also satisfies 2.1 AA — the version named in the DOJ's Title II rule and the EU's technical standard. WCAG 2.2's nine added criteria — minimum target size and accessible authentication among them — reflect how people actually use sites today, and building to the older version just means redoing work later.
What happens if a website doesn't meet WCAG Level AA?
Usually a demand letter or lawsuit from a plaintiff's firm, often after an automated scan of the site turned up detectable failures. Most web-accessibility cases settle for between $10,000 and $75,000 plus a remediation commitment — average settlement costs run $30K+ before attorney's fees — and in California, Unruh Act statutory damages start at $4,000 per violation.
Beyond litigation, an inaccessible site turns away paying customers every day it stays broken. Remediating to Level AA addresses both problems at once.