WCAG 2.1 Level AA is the version of the Web Content Accessibility Guidelines that U.S. courts, regulators, and settlements treat as the practical standard for an accessible website. It’s a set of 50 testable success criteria from the W3C covering everything from color contrast to keyboard navigation.
What WCAG 2.1 AA actually covers
WCAG stands for the Web Content Accessibility Guidelines, maintained by the World Wide Web Consortium (W3C) through its Web Accessibility Initiative. “2.1” is the version, published in 2018; “AA” is the conformance level.
Every criterion is organized under four principles, known by the acronym POUR:
- Perceivable — users can perceive the content (text alternatives, captions, sufficient contrast).
- Operable — users can operate the interface (full keyboard access, no time traps, focus visibility).
- Understandable — content and operation are predictable and clear (labels, error messages, consistent navigation).
- Robust — content works across browsers and assistive technology, now and in the future (valid, well-structured code).
Within those four principles sit 13 guidelines, and under the guidelines sit the testable success criteria. At Level AA there are 50 criteria total: the 30 from Level A plus 20 more at AA. For a deeper look at the four principles, see our POUR principles guide.
Why AA is the legal benchmark
Most business owners want a single answer to “what level do I need?” The answer is almost always AA — not A, not AAA.
Here’s why AA, and not the other levels, became the reference point:
| Level | What it means | Practical use |
|---|---|---|
| A | The bare minimum. Skipping it makes a site unusable for many people. | Too low to be a real target on its own. |
| AA | Removes major barriers for most disabilities. | The standard cited in laws, lawsuits, and contracts. |
| AAA | The strictest level. Some criteria can’t apply site-wide. | A stretch goal, not a site-wide requirement. |
Several forces point to AA specifically:
- Section 508, which governs U.S. federal agencies, formally incorporates WCAG 2.0 AA — and the Section508.gov guidance treats AA as the bar.
- The DOJ has repeatedly referenced WCAG conformance in ADA settlement agreements, and its 2024 rule for state and local governments (Title II) sets WCAG 2.1 AA as the technical standard.
- Plaintiffs’ attorneys in private ADA Title III cases cite WCAG 2.1 AA as the measure of an “accessible” site. Thousands of ADA web lawsuits and demand letters are filed each year, and AA is the yardstick used in nearly all of them.
The ADA itself doesn’t spell out WCAG version numbers for private businesses, so this is the consensus benchmark rather than a line of statute — and none of this is legal advice. For your specific exposure, talk to an attorney. To understand how the standards relate, see ADA vs Section 508 vs WCAG.
Key WCAG 2.1 AA success criteria, in plain English
You don’t need to memorize all 50 criteria, but these are the ones that come up most often in audits and lawsuits.
Perceivable
- 1.1.1 Non-text Content (A): Every meaningful image needs alt text; decorative images get empty alt so screen readers skip them.
- 1.3.1 Info and Relationships (A): Structure has to be in the code, not just visual — real headings, lists, and landmarks, not bold text faking a heading.
- 1.4.3 Contrast (Minimum) (AA): Normal text needs a contrast ratio of at least 4.5:1 against its background; large text needs 3:1.
- 1.4.10 Reflow (AA): Content must reflow to a single column at 320px wide without horizontal scrolling — a mobile and low-vision win added in 2.1.
- 1.4.11 Non-text Contrast (AA): Buttons, form borders, and icons need a 3:1 contrast ratio too, not just text.
Operable
- 2.1.1 Keyboard (A): Everything must work with a keyboard alone — no mouse required. This is the single most common failure we find.
- 2.4.7 Focus Visible (AA): A visible focus indicator must show which element is selected as someone tabs through the page. See our guide to navigation and focus management.
- 2.5.1 Pointer Gestures (A): Anything that uses a complex gesture (like a pinch or swipe) needs a simple single-pointer alternative — new in 2.1.
Understandable
- 3.3.1 Error Identification (A): When a form rejects input, the error must be described in text, not just a red outline.
- 3.3.2 Labels or Instructions (A): Every input needs a programmatic label so screen readers like NVDA, JAWS, and VoiceOver announce its purpose. Our accessible forms guide covers this in depth.
Robust
- 4.1.2 Name, Role, Value (A): Custom widgets (menus, modals, tabs) must expose their name, role, and state to assistive technology — usually through correct ARIA labels and roles.
- 4.1.3 Status Messages (AA): Dynamic updates (like “3 items added to cart”) must be announced without moving focus.
For a full background on these standards, WebAIM maintains excellent reference material.
What’s new in 2.1 versus 2.0
WCAG 2.1 is fully backward-compatible: every 2.0 AA criterion carries forward, and 2.1 adds criteria aimed at three groups that 2.0 underserved.
- Mobile users — orientation, reflow, and touch-target gestures.
- Low-vision users — text spacing, non-text contrast, and content on hover or focus.
- Users with cognitive and learning disabilities — clearer error handling and consistent help.
If you meet 2.1 AA, you automatically meet 2.0 AA. The newer WCAG 2.2 adds a handful more criteria on top — worth knowing about, but 2.1 AA remains the dominant legal reference today.
How to actually meet WCAG 2.1 AA
This is the part overlay vendors don’t want you to hear: a script you paste into your site cannot make you conform.
Automated tools and overlay widgets reliably detect only about 30–40% of WCAG issues. The criteria that get sites sued — keyboard traps, missing form labels, broken focus order, unlabeled custom widgets — almost always require a human testing with a keyboard and a screen reader. That’s why overlays don’t ensure ADA compliance, and why so many overlay users still receive demand letters. If you’re weighing your options, compare overlay versus manual remediation.
Real conformance follows a straightforward path:
- Audit — test all 50 AA criteria, automated plus manual, and document each failure. A professional accessibility audit produces a prioritized issue list.
- Remediate — fix the underlying HTML, CSS, and ARIA by hand. Manual remediation is the only durable fix.
- Verify and document — re-test, then capture conformance in a VPAT (Voluntary Product Accessibility Template) or accessibility statement.
- Monitor — content changes, so periodic re-testing keeps you conformant over time.
Curbcut does the manual work — no widgets, no shortcuts. The fastest way to see where your site stands against WCAG 2.1 AA is a free accessibility scan, and from there a full audit maps out exactly what to fix.
The short version
WCAG 2.1 AA is the 50-criterion standard that defines an accessible website in the eyes of U.S. courts, the DOJ, and Section 508. It’s organized around the POUR principles, it covers contrast, keyboard access, labels, and robust code, and it’s the level you should target. Overlays can’t get you there — manual remediation can.