WCAG vs ADA vs Section 508

Three Different Things

WCAG, the ADA, and Section 508 are mentioned together so often that they are frequently treated as interchangeable. They are not. One is a technical standard, one is a civil rights statute, and one is a federal procurement and technology requirement. They come from different bodies, cover different organizations, and are enforced through different mechanisms.

Getting the distinction right matters in practice. It determines which rules apply to an organization, which version of a technical standard it is measured against, what a vendor claim actually promises, and what an accessibility statement can honestly say.

This page explains what each one is, how they connect, and where the common shortcuts break down.

WCAG: The Technical Standard

The Web Content Accessibility Guidelines are published by the World Wide Web Consortium through its Web Accessibility Initiative. They describe testable conditions that digital content must meet to be usable by people with disabilities, organized under four principles and sorted into conformance levels A, AA, and AAA.

WCAG has no legal force on its own. It is a standard that laws, regulations, contracts, and policies can adopt. When a regulation adopts WCAG, it names a specific version and level, and that named version is what the regulation requires until the regulation itself is changed.

Three versions of WCAG 2 are in active use: WCAG 2.0 from 2008, WCAG 2.1 from 2018, and WCAG 2.2, which reached W3C Recommendation status in October 2023 and was updated in December 2024. They are backward compatible, so content meeting WCAG 2.2 also meets WCAG 2.1 and WCAG 2.0.

The ADA: A Civil Rights Statute

The Americans with Disabilities Act is a federal civil rights law prohibiting discrimination on the basis of disability. It is organized into titles that cover different kinds of entities, and the title that applies determines both the obligation and the enforcement path.

Title I addresses employment and applies to covered employers. Its core duties concern nondiscrimination and reasonable accommodation rather than conformance to a named technical standard.

Title II addresses state and local government entities and the programs, services, and activities they provide.

Title III addresses places of public accommodation operated by private entities, a category that includes many businesses open to the public.

For most of the ADA's history, the statute and its regulations did not name a technical standard for web content. Courts and the Department of Justice treated digital services as falling within the programs and services the ADA covers, but organizations had no regulation telling them what accessible actually meant in technical terms.

The Title II Web and Mobile Rule

That changed for state and local governments. In April 2024 the Department of Justice issued a rule, codified at 28 CFR part 35, subpart H, establishing a technical standard for the web content and mobile applications of public entities.

The standard is WCAG 2.1 at Level A and Level AA.

Compliance dates depend on the entity's total population as the rule defines that term. Public entities other than special district governments with a total population of 50,000 or more have a compliance date of April 26, 2027. Public entities with a total population under 50,000, and any special district government, have a compliance date of April 26, 2028. Both dates reflect a one-year extension the Department adopted in an interim final rule published in April 2026, replacing the original dates of April 24, 2026 and April 26, 2027.

This rule is specific. It applies to public entities under Title II. It does not establish a general federal WCAG requirement for private businesses, and it does not change what Section 508 requires of federal agencies.

Section 508: Federal Technology

Section 508 of the Rehabilitation Act requires federal agencies to make their information and communication technology accessible. It applies when agencies develop, procure, maintain, or use that technology, and it covers access for both federal employees and members of the public who interact with agency technology.

The technical requirements are set out in the Revised Section 508 Standards maintained by the U.S. Access Board. Those standards incorporate WCAG 2.0 at Level A and Level AA for electronic content.

Section 508 is a requirement on federal agencies. It reaches contractors and vendors through federal procurement, because agencies must buy technology that conforms, which is why suppliers to the federal government are frequently asked for conformance documentation. Section 508 does not, on its own, impose accessibility requirements on private businesses generally, on state and local governments, or on private nonprofits. Organizations that receive federal financial assistance may have separate obligations under Section 504 of the Rehabilitation Act, which is a different provision with its own framework.

Side by Side

The differences are easier to hold onto when the same four questions are asked of each.

What it is. WCAG is a technical standard published by the W3C. The ADA is a federal civil rights statute enforced through its implementing regulations. Section 508 is a federal statutory requirement for agency information and communication technology, implemented through standards issued by the U.S. Access Board.

Who it covers. WCAG covers no one by itself, because adoption is what gives it force. The ADA covers employers under Title I, state and local government entities under Title II, and places of public accommodation under Title III. Section 508 covers federal agencies, and reaches vendors through federal procurement.

Which technical standard applies. WCAG is the standard. The Title II web and mobile rule adopts WCAG 2.1 Level A and AA for public entities. The Revised Section 508 Standards adopt WCAG 2.0 Level A and AA for electronic content. Title I and Title III do not currently adopt a specific WCAG version by regulation.

How it is enforced. WCAG has no enforcement mechanism of its own. ADA obligations are enforced through federal complaint investigation, agency action, and private litigation, with the specific path depending on the title. Section 508 is addressed through agency compliance processes, federal procurement, and an administrative complaint process.

Why WCAG Compliant Does Not Mean Legally Compliant

A claim that content is WCAG compliant leaves three questions unanswered: which version, which level, and whether the law that applies to this organization adopts that version.

A state agency that conforms to WCAG 2.2 Level AA satisfies the Title II rule's requirement of WCAG 2.1 Level AA, because of backward compatibility. A federal agency that conforms to WCAG 2.1 Level AA satisfies the Revised Section 508 requirement of WCAG 2.0 Level A and AA for the same reason. A private business that conforms to WCAG 2.2 Level AA has met a widely referenced technical benchmark, but has not satisfied a federal regulation that names a WCAG version for Title III web content, because current Department of Justice regulations do not specify one.

Conformance to a technical standard also does not resolve every obligation an organization may have. Effective communication, reasonable accommodation, reasonable modification of policies, and the availability of alternative means of access are separate requirements that a conformance claim does not address.

Why Section 508 and ADA Compliance Are Not Synonyms

The phrase Section 508 compliant is used loosely, often by vendors describing products sold to organizations that are not federal agencies.

Section 508 and the ADA have different legal sources, different covered entities, and different incorporated WCAG versions. A product described as Section 508 conformant has been assessed against WCAG 2.0 Level A and AA. For a state or local government subject to the Title II rule, the applicable standard is WCAG 2.1 Level A and AA, which includes criteria that WCAG 2.0 does not.

A vendor statement about Section 508 is therefore not a substitute for evaluating the product against the standard that actually applies to the buying organization.

Private Businesses and Title III

Title III of the ADA applies to places of public accommodation operated by private entities. Litigation involving websites and mobile applications has been substantial.

For Title III web content, the Department of Justice's current regulations do not specify a WCAG version and conformance level as the technical standard. DOJ nevertheless takes the position that Title III obligations apply to the goods and services public accommodations offer through the web. In the absence of such a regulation, WCAG conformance is commonly used as the practical benchmark, including in settlement agreements and consent decrees, without being a federally specified technical requirement for those entities.

Descriptions suggesting that all private businesses are legally required to meet a particular WCAG version under the ADA should be treated with caution. The safer and more accurate framing is that Title III obligations exist, that WCAG is the standard most commonly used to measure and demonstrate accessibility, and that the specific technical expectation in any given matter depends on its circumstances.

Choosing a Target in Practice

Organizations generally get a clearer result by separating two decisions.

The first is the legal question of what applies. A state or local government entity should identify its compliance date and design to WCAG 2.1 Level A and AA at minimum. A federal agency, or a vendor selling to one, works to the Revised Section 508 Standards. A private employer or business has obligations under the ADA that are not expressed as a named WCAG version, and should consider what its own risk position, contracts, and users require.

The second is the design and procurement question of what to build. Many organizations choose WCAG 2.2 Level AA as the target because it is the most current published version, it satisfies earlier versions through backward compatibility, and it reduces the work needed if a future regulation moves to a newer version.

Naming the specific version and level in requirements, contracts, and accessibility statements removes the ambiguity that the shorthand terms create.

Related AssistiveTechnology.org Resources

For what WCAG is and how it is structured, see WCAG Overview. For the practical differences between the two most recent versions, see WCAG 2.1 vs 2.2. For the Title II rule in full detail, see ADA Title II Digital Accessibility for State and Local Governments, and for the K-12 context, see ADA Title II Digital Accessibility for Public Schools. For employer-facing digital accessibility, see Digital Accessibility for Employers. For a general orientation, see Digital Accessibility, and for further reading across topics, see Resources.

Request accessibility services

Authoritative Sources

World Wide Web Consortium, Web Accessibility Initiative: WCAG 2 Overview, for version status and conformance levels.

28 CFR part 35, subpart H, Web and Mobile Accessibility, and U.S. Department of Justice, ADA.gov: Fact Sheet on the rule for web content and mobile applications of state and local government entities.

Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities, 89 FR 31337, April 24, 2024, as amended by the interim final rule published April 20, 2026.

U.S. Access Board: Revised Section 508 Standards, including the incorporation of WCAG 2.0 Level A and Level AA for electronic content.

Section508.gov: Laws and Policies, for the scope of Section 508 and the entities it covers.

U.S. Department of Justice, ADA.gov: guidance on the Americans with Disabilities Act and its titles.

Last Regulatory Review

Last regulatory review: September 21, 2026. On that date the WCAG versions incorporated by the Department of Justice Title II rule and by the Revised Section 508 Standards, the Title II compliance dates, the scope of Section 508, and the status of Department of Justice regulations on a Title III web technical standard were verified against current Department of Justice, U.S. Access Board, Section508.gov, and W3C sources.

About This Page

This page provides general educational information about how the Web Content Accessibility Guidelines, the Americans with Disabilities Act, and Section 508 of the Rehabilitation Act relate to one another in the United States. It is prepared by The Accessibility Clinic Inc. as educational information only. It is not legal advice, and it does not determine which laws apply to any particular organization or whether any specific website, application, or product meets a legal requirement. Organizations should evaluate their own obligations in light of their specific circumstances and consult qualified counsel when needed. Regulations and standards change; the last regulatory review date above indicates when the statements on this page were most recently verified against primary sources.