Skip to main content
WCAGrules
Quick navigation

Guides · Comparisons

WCAG vs. the ADA: One Is a Standard, One Is a Law

People use the two words as if they were interchangeable. Understanding the difference tells you exactly what you are on the hook for.

Last reviewed August 31, 2026

WCAG is a technical standard published by the W3C, a standards body with no enforcement power. The ADA is a US federal civil rights law with courts behind it. WCAG cannot require anything. The ADA can, and does.

They connect because the ADA never says what an accessible website is, so everybody involved reaches for the only credible technical definition available.

WCAGADA
What it isA technical standardA civil rights law
Published byThe W3CThe US Congress, 1990
CoversWeb content, anywhere in the worldUS businesses and governments
Mentions websitesThat is all it doesNever
EnforcementNonePrivate lawsuits and the DOJ
Says what to doPrecisely, in 55 A and AA criteriaNot at all, for private businesses
WCAG and the ADA compared

How the Gap Gets Filled

Because Title III of the ADA names no technical standard for private businesses, plaintiffs plead WCAG, expert witnesses test against WCAG, and settlements specify WCAG conformance as the remedy. It is become the de facto standard by consensus rather than by regulation.

For government, that changed. The Department of Justice's Title II rule sets WCAG 2.1 Level AA as a formal legal requirement for state and local government. The deadlines are April 2027 for larger entities and April 2028 for smaller ones. There, the standard is named in the regulation.

One phrase in that regulation does more work than the version number, and almost nobody quotes it. The rule asks for the Level A and AA success criteria and conformance requirements. Not the criteria alone. The conformance requirements are the five clauses at the back of WCAG that most people skip: the level you are claiming, whole pages rather than parts of them, every page in a process, only technologies that assistive technology can actually use, and non-interference from everything else on the page. So for a covered public entity, "we pass the 50 checks" is not what the regulation asked for. It asked for those plus the machinery that says what passing means.

The same regulation then tightens one of them. WCAG lets you meet a criterion with a conforming alternate version freely. The rule permits that route only where making the content directly accessible is not possible for technical or legal reasons. A law can adopt the standard and then ask for more, and this one does.

What That Means for You

  • "ADA compliant website" is not a defined thing for a private business. The Title II rule names a standard for state and local government, and nothing equivalent names one for everybody else. There is no certification either, and nobody who could issue one, so a vendor selling ADA certification is selling something that does not exist.
  • WCAG 2.1 AA is the practical answer for private businesses, because it is what complaints plead and settlements require.
  • Testing against WCAG 2.2 covers it, since the versions are backwards compatible. With one asterisk for a covered public entity: 2.2 retired 4.1.1 Parsing and the Title II rule keeps it, so that rule needs checking on top of a 2.2 audit.
  • Meeting WCAG is not immunity. It is strong evidence of good faith and a much better position than not having tested, and it is not a legal shield.

The phrase to be careful with

"ADA compliant" implies a pass mark that does not exist for websites. "Tested against WCAG 2.2 Level AA on these pages, on this date" is a claim you can actually support.

The Rest of the World

The same pattern repeats nearly everywhere. Laws point at WCAG rather than writing their own rules. The European Accessibility Act through EN 301 549, the UK Equality Act, Ontario's AODA, France's RGAA, and Section 508 in US federal procurement.

That is the useful conclusion: one technical target satisfies most of the world's accessibility law at once. Our laws section covers 38 of them with the version each names.

One honest limit

Nothing here is legal advice, and we are not lawyers. What we can tell you is what your site does and does not do against WCAG, with evidence attached. What that means for your legal position is a question for somebody qualified to answer it.

Common questions

What is the difference between WCAG and the ADA?
WCAG is a technical standard published by the W3C with no enforcement power. The ADA is a US civil rights law with courts behind it. The ADA never mentions websites, so WCAG has become the measure courts and plaintiffs use.
Does the ADA require WCAG?
For state and local government, yes. The DOJ's Title II rule names WCAG 2.1 AA with deadlines in April 2027 and April 2028. For private businesses there is no codified standard, but WCAG is what complaints plead and settlements specify.
Can my website be ADA certified?
No. There is no ADA certification for websites, no accrediting body, and no pass mark. Any vendor offering one is selling something that does not exist.
Does meeting WCAG protect me from a lawsuit?
It does not make you immune, and it is a much stronger position than not having tested. An audit gives you dated evidence of where you stand and a record of what you fixed.

Sources

Keep reading

More on comparisons

Reading about it is the cheap part.

Find out where your site actually stands. The free scan checks 10 pages in a real browser against all 90 supported automated rules, keeps its 27 best-practice checks separate from WCAG findings, and names the rule behind every finding. The full audit adds an expert review and a real blind screen-reader user. From $499, with the report in 5 business days on Rapid and 10 on Standard, and the clock starting at cleared payment.

Go somewhere useful

Find tools, resources and your workspace.

29 destinations