Skip to content
wcagc
←Back to blog
ADAWCAGSection 508Title II

Does the ADA require WCAG, and which level?

The ADA never names WCAG. Here is where WCAG is actually binding in US law, which level applies, and which version to build toward.

P

Pavel Charkasau

Does the ADA require WCAG? Not in its own text. The statute was signed in 1990, it never mentions websites, and no federal regulation tells a private business which version of WCAG to meet. The Justice Department says this plainly: it "does not have a regulation setting out detailed standards," and businesses "have flexibility in how they comply" (ADA.gov). The same guidance then points at WCAG as one of the "existing technical standards" that "provide helpful guidance."

WCAG does become binding in two places. Under ADA Title II, state and local governments must meet WCAG 2.1 Level AA for web content and mobile apps, with compliance dates now in 2027 and 2028 (ADA.gov). Under Section 508, federal agencies must meet WCAG 2.0 Level A and AA (U.S. Access Board). The level is AA in both. Nothing in US law requires AAA. If you run a private business, the working answer is WCAG 2.2 Level AA, and the rest of this post explains why that is the right target even though no rule names it.

Does the ADA itself name WCAG anywhere?

No. Title III covers "public accommodations" and the goods and services they offer, and DOJ has long read that to include what those businesses offer online (ADA.gov). What it does not do is name a technical standard. There is no version number, no conformance level, and no deadline written into the law for private companies.

That gap is why the question keeps coming up, and why so many compliance pages answer it badly. "The ADA requires WCAG 2.1 AA" is a sentence you will read on dozens of vendor sites. It is not true as written. What is true is that WCAG is the yardstick everyone reaches for when the question turns concrete: DOJ in its guidance, courts in consent decrees, and procurement teams in their contracts.

Where is WCAG actually required by US law?

Two federal rules name it. A third context, Title III litigation, imports it by practice rather than by regulation.

RuleWho it bindsWCAG version and levelDate
ADA Title II web rule (28 CFR part 35, subpart H)State and local government web content and mobile appsWCAG 2.1, Level AAApril 26, 2027 (population 50,000+); April 26, 2028 (under 50,000 and special districts)
Revised Section 508 Standards (E205.4)Federal agency ICT, and what agencies buyWCAG 2.0, Level A and AAIn force since January 18, 2018
ADA Title IIIPrivate businesses open to the publicNone namedNone

The Title II rule is the only ADA regulation with a WCAG version in it. It also carries five exceptions, which matter more than people expect: archived web content, conventional electronic documents posted before the compliance date, third-party content posted by members of the public, individualized password-protected documents such as a utility bill, and social media posts published before the date (ADA.gov). Those exceptions do not switch off the general duty of effective communication.

Section 508 is older and points at an older version. E205.4 requires that electronic content "conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0" (U.S. Access Board). The Access Board has not updated that reference to 2.1 or 2.2. If you sell software to a federal agency, WCAG 2.0 AA is the contractual floor, and the buyer will usually ask you to document it in a VPAT. I go through that document in Section 508 vs WCAG.

Title III is the one with no number attached. Federal enforcement and private suits still land on a WCAG version, because a settlement needs something measurable to point at, and WCAG 2.1 AA is what recent Title II agreements have used.

Which WCAG level does the ADA point to: A, AA, or AAA?

AA. Every US rule that names a level names Level A and AA together, and none of them reaches AAA. That is not an oversight. W3C's own conformance guidance says: "It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA success criteria for some content" (W3C). Some AAA criteria simply cannot apply to some content, so a site-wide AAA requirement would be unmeetable by design.

One detail from the same page trips up almost everyone: "Conformance (and conformance level) is for full web page(s) only, and cannot be achieved if part of a web page is excluded" (W3C). A page is not "AA except the booking widget." If the widget is on the page, the page fails. Here is my opinion, and it is the one I argue with clients most: a partial conformance claim is worse than no claim, because it invites someone to check the part you left out. If the levels themselves are fuzzy, WCAG levels A, AA, AAA explained has the breakdown.

Which WCAG version should a US business build toward in 2026?

WCAG 2.2 Level AA.

Start with the mechanical reason: 2.2 is a superset. W3C states that "content that conforms to WCAG 2.2 also conforms to WCAG 2.0 and WCAG 2.1" (W3C). Build to 2.2 AA and you have met the 2.1 AA the Title II rule requires and the 2.0 AA that Section 508 requires. One target instead of three.

Picking the newer version also does not put you at odds with the rule. DOJ's small entity compliance guide explains that a public entity may use a future standard "if the standard provides the same or more accessibility and usability than WCAG 2.1, Level AA" (ADA.gov).

Then there is what 2.2 adds. Target size at a 24-by-24 CSS pixel minimum (2.5.8), focus indicators a sticky header does not cover (2.4.11), and authentication that does not force someone to recall a code from memory (3.3.8) (W3C). Those are checkout and login problems, which is where complaints usually start.

WCAG 2.2 has been a W3C Recommendation since 2023, republished in December 2024 (W3C). It is stable. Waiting for a rule to catch up to it costs you more than adopting it does.

What if the same site also sells into the EU?

Then a version is named for you, and the ambiguity disappears. EN 301 549 is the harmonised European standard behind the European Accessibility Act, and it "includes WCAG 2.1 Level AA verbatim without modifications for Web content" (W3C WAI). For a US company shipping to European customers, that is a concrete requirement with a specified conformance level, which is more than Title III gives you at home. Our EN 301 549 pillar covers how the clauses map, and EN 301 549 vs WCAG 2.1 covers the parts of the standard that go beyond the web.

Building to WCAG 2.2 AA covers both jurisdictions at once, which is the practical argument for picking the newer version rather than the one your local rule happens to cite.

How do I check whether my site meets WCAG 2.2 AA?

Start with a scan to get the map, then triage by what blocks a task. An automated pass finds the machine-detectable failures fast: form fields with no accessible name, images with no text alternative, contrast below 4.5:1, focus order that jumps. That is the layer demand letters cite first, and the layer you can fix in a sprint.

It is also not the whole picture. Automated tools catch roughly 30 to 57% of issues depending on the study, and Deque's own analysis of its rule set put full automated coverage at 57% (Deque). Our scanner will not tell you whether an error message makes sense when a screen reader reads it aloud, or whether your custom dropdown behaves the way a keyboard user expects. Full conformance needs a human review, and any vendor who tells you otherwise is selling you something the FTC has already fined a competitor over: accessiBe paid $1 million in 2025 for claiming its widget could make a site WCAG compliant automatically (FTC).

Use the WCAG checklist as the working reference while you triage by criterion and level.

FAQ

Does the ADA require WCAG 2.1 AA?

For state and local governments, yes: the ADA Title II web rule requires WCAG 2.1 Level AA for web content and mobile apps, with compliance dates of April 26, 2027 and April 26, 2028 (ADA.gov). For private businesses under Title III, no regulation names a WCAG version, though WCAG 2.1 AA is the benchmark settlements use.

Which WCAG level do I need for ADA compliance?

Level AA. Both the ADA Title II rule and the Revised Section 508 Standards require Level A and AA success criteria, and no US rule requires Level AAA. W3C advises against requiring AAA site-wide because some AAA criteria cannot be satisfied for some content (W3C).

Is WCAG 2.2 required by the ADA?

No rule requires WCAG 2.2, but meeting it satisfies the versions that are required. W3C states that content conforming to WCAG 2.2 also conforms to WCAG 2.0 and 2.1 (W3C), and DOJ's compliance guide allows a standard that provides the same or more accessibility than WCAG 2.1 Level AA (ADA.gov).

Does Section 508 require WCAG?

Yes. E205.4 of the Revised Section 508 Standards requires electronic content to conform to WCAG 2.0 Level A and AA success criteria, and those standards have been in force since January 18, 2018 (U.S. Access Board). Section 508 applies to federal agencies and to the ICT they procure, not to private websites generally.

Is a small business required to follow WCAG?

No WCAG version is written into the law for private businesses of any size, but the ADA's nondiscrimination and effective communication duties still apply to what you offer online (ADA.gov). WCAG 2.2 Level AA is the standard to build toward, because it is the measure a court, a customer, or a procurement team will use.

See which WCAG criteria your pages fail today

There is no ADA certificate to earn, so the useful question is narrower: which WCAG 2.2 AA failures are on your pages right now, and which of them block someone from finishing a task. A scan gives you that list with the exact selector for each finding, so you can fix the blocking issues before the cosmetic ones. Run a free accessibility scan and start there.

Written by Pavel Charkasau, founder of wcagc.com. I read what the agencies actually publish, so the guidance here matches the rule text rather than the marketing around it.

Last updated: August 26, 2026

Sources