Section 508 vs ADA vs WCAG: How the Three Actually Fit Together

Three terms get used as if they were synonyms in almost every accessibility RFP, and they are not interchangeable. Section 508 is a federal procurement law. The ADA is a civil rights law. WCAG is a technical standard that neither of them wrote. Understanding which one applies to you decides what you have to do, who can enforce it, and what evidence you need to produce.

Here is the short version, then the detail.

	What it is	Who it binds	The technical bar
Section 508	Amendment to the Rehabilitation Act	Federal agencies, and vendors selling ICT to them	WCAG 2.0 Level AA, incorporated by reference
ADA	Civil rights statute	State/local government (Title II), public accommodations (Title III)	WCAG 2.1 Level AA for Title II under DOJ rulemaking
WCAG	W3C technical standard	Nobody, on its own	Itself — A, AA, AAA levels

WCAG is the ruler, not the law

The Web Content Accessibility Guidelines are published by the World Wide Web Consortium, a standards body with no enforcement power whatsoever. WCAG cannot make you do anything.

What makes WCAG matter is that regulators kept pointing at it rather than inventing their own criteria. It is organized around four principles — content must be Perceivable, Operable, Understandable, and Robust — and each principle contains testable success criteria at three levels: A (minimum), AA (the practical target almost everyone is held to), and AAA (aspirational, rarely required wholesale).

When someone says “we need to be WCAG compliant,” the useful follow-up questions are which version and which level. “WCAG 2.1 AA” and “WCAG 2.2 AA” are different obligations. See what changed in WCAG 2.2.

Section 508 is about what the federal government buys

Section 508 of the Rehabilitation Act requires federal agencies to make their information and communication technology accessible — both what they build and, critically, what they buy.

That second half is why 508 reaches far beyond government payrolls. If you sell software, documents, training content, video, or a web application to a federal agency, 508 conformance shows up as a contract requirement. The 2017 “Section 508 Refresh” restructured the standards and incorporated WCAG 2.0 Level AA by reference for electronic content — which is why a procurement officer can ask for WCAG conformance while citing a statute that never mentions the W3C.

Section 508 obligations typically arrive as a request for a conformance report. That is a VPAT, and it is worth understanding what you are signing.

Section 508 also travels. Many states passed “little 508” laws adopting the federal standards for state procurement, and federal grant conditions frequently flow the requirement down to recipients. A school district or nonprofit that has never sold anything to a federal agency can still be bound through a grant.

The ADA is about discrimination, and it has teeth

The Americans with Disabilities Act never mentions websites — it predates the commercial web. Its relevance comes from how courts and the Department of Justice have applied its non-discrimination requirements to digital services.

• Title II covers state and local government entities. DOJ rulemaking has set WCAG 2.1 Level AA as the standard for web content and mobile apps, with staged compliance dates by population size. Those dates, and what they mean operationally, are covered in WCAG & ADA compliance for websites.
• Title III covers private “public accommodations” — retailers, banks, healthcare providers, hotels, and increasingly their websites and apps. There is no single web regulation under Title III, which is precisely why litigation has driven so much of it.

The enforcement difference matters more than the technical one. A Section 508 failure is usually a contract problem: a finding, a remediation plan, a lost bid. An ADA failure is a civil rights claim, and private plaintiffs can bring it. You do not need a government contract to be sued.

Which one applies to you

• Federal agency — Section 508, directly.
• Selling to a federal agency — Section 508, through your contract. Expect to produce a conformance report.
• State or local government — ADA Title II, and quite possibly a state procurement law mirroring 508.
• Public school district, university, or a grant recipient — often all three at once, depending on funding sources.
• Private business serving the public — ADA Title III, plus 508 if you sell to government.
• Healthcare provider taking federal funds — ADA, plus Section 504 obligations, which have their own accessibility requirements.

Most organizations we work with are in more than one row. The practical consequence is less complicated than it sounds: conform to WCAG 2.1 AA at minimum, document what you did, and you have satisfied the technical substance of all of them. The differences resurface in who audits you and what paperwork they want, not usually in what you have to build.

Where the paperwork diverges

This is the part that surprises people who have already done the engineering work.

• Section 508 wants a conformance report tied to specific standards, usually a VPAT, refreshed when the product changes.
• ADA Title II wants a demonstrable conformance posture and, in practice, a remediation plan showing you are addressing what is not yet conformant.
• Both benefit enormously from dated audit records. “We fixed it” is worth far less than “we audited on this date against these criteria, found these issues, and closed them on these dates.”

If your documents and PDFs are part of what you deliver — and for most agencies they are the largest part by volume — see our guide to PDF remediation and how to make Word, PowerPoint, and Excel files accessible.

Getting help

Taika provides Section 508 remediation, PDF & document accessibility, ADA website accessibility, accessible video, and captioning & subtitling.

If you are not sure which framework applies or where you currently stand, request an accessibility assessment and we will map your obligations to what your content actually does today.