Skip to main content
Simkins and Elgazar

Section 508 vs. ADA vs. WCAG: Understanding the Differences

Maximilian Simkins, Simkins & Elgazar
Section 508ADAWCAGCompliance

Federal contractors, software vendors, and government agencies routinely encounter three terms, Section 508, the ADA, and WCAG, used interchangeably, as if they describe the same requirement. They do not. Each has a distinct legal basis, a defined scope of applicability, and different enforcement mechanisms.

Understanding the differences matters for practical reasons: the wrong framework assumption can leave an organization exposed to legal risk it did not know it was carrying, or produce a compliance program that satisfies the letter of one requirement while missing another entirely.

What Section 508 Is

Section 508 is a provision of the Rehabilitation Act of 1973, as amended in 1998 and refreshed in 2017. It requires federal agencies to ensure that the information and communications technology (ICT) they develop, procure, maintain, or use is accessible to people with disabilities, both employees and members of the public.

Section 508 is enforced through federal procurement. The technical requirements are defined by the U.S. Access Board in the ICT Accessibility Standards, which were updated in the 2017 refresh to incorporate WCAG 2.0 Level AA as the technical baseline. The scope is specific: the law applies directly to federal agencies and, by contract, to vendors delivering ICT under a federal contract.

Who Section 508 applies to:

  • Federal executive agencies
  • Prime contractors and subcontractors delivering digital products or services under a federal contract
  • Organizations receiving federal financial assistance, under related statutes

Section 508 does not apply directly to private companies operating outside the federal supply chain. A commercial e-commerce site has no direct Section 508 obligation, unless it is also under contract with a federal agency.

What the ADA Is

The Americans with Disabilities Act (ADA) is a civil rights law enacted in 1990. It prohibits discrimination against people with disabilities across a much broader range of contexts than Section 508. For digital accessibility, the relevant titles are:

  • Title II, applies to state and local governments. Covers websites, apps, and digital services operated by cities, counties, transit authorities, public universities, and similar entities.
  • Title III, applies to places of public accommodation. Courts have consistently held that websites and mobile apps operated by businesses open to the public qualify as places of public accommodation under Title III, regardless of whether they have a physical location.

The ADA does not prescribe a specific technical standard for digital accessibility. For years, the Department of Justice (DOJ) deferred to WCAG as the de facto benchmark in enforcement actions and consent decrees. In 2024, the DOJ issued final rules under Title II formally adopting WCAG 2.1 Level AA as the required technical standard for state and local government websites and mobile apps. Title III rulemaking has not produced a final rule establishing a specific standard, though WCAG 2.1 AA remains the reference standard courts and the DOJ apply in practice.

Who the ADA applies to:

  • State and local government agencies (Title II)
  • Private businesses open to the public, including companies with public-facing websites and mobile applications (Title III)
  • Employers with 15 or more employees (Title I, covering employment, outside the scope of this discussion)

What WCAG Is

WCAG, the Web Content Accessibility Guidelines, is not a law. It is a technical standard developed and maintained by the World Wide Web Consortium (W3C) through its Web Accessibility Initiative (WAI). WCAG defines specific, testable success criteria organized under four principles: Perceivable, Operable, Understandable, and Robust (the POUR framework).

The current operative version for most compliance purposes is WCAG 2.1. WCAG 2.2 was published in October 2023 and adds nine new success criteria, with Level AA criteria including enhanced focus visibility requirements. WCAG 3.0 is in early development and is not yet adopted into any law or regulation.

WCAG success criteria are organized into three conformance levels:

  • Level A, minimum requirements; failure at this level means significant barriers for users with disabilities
  • Level AA, the standard referenced in Section 508, the DOJ's Title II rule, and most legal and contractual requirements
  • Level AAA, the highest level; not required by any current law or regulation, though specific criteria at this level are occasionally specified in contracts

WCAG is what Section 508 and the ADA both point to as the technical definition of what "accessible" means. It is the shared vocabulary of digital accessibility compliance.

How the Three Standards Relate

The relationship between these three frameworks can be described precisely:

Section 508 incorporates WCAG. The 2017 refresh of the Section 508 standards adopted WCAG 2.0 Level AA by reference for web content and software. Organizations complying with Section 508 are, by definition, meeting a substantial portion of WCAG 2.0 AA.

The ADA references WCAG in enforcement. The DOJ's 2024 Title II rule formally adopts WCAG 2.1 AA for state and local government. For Title III enforcement, courts and the DOJ apply WCAG 2.1 AA as the practical standard, even without a formal rule.

WCAG 2.1 extends WCAG 2.0. WCAG 2.1 adds 12 success criteria beyond WCAG 2.0, primarily addressing mobile accessibility and cognitive disabilities. Section 508 technically requires only WCAG 2.0 AA, but most agencies and prime contractors now specify WCAG 2.1 AA as the minimum, and WCAG 2.1 is what the DOJ's Title II rule requires.

The practical consequence: an organization targeting WCAG 2.1 AA conformance will satisfy the technical requirements of Section 508 (which requires WCAG 2.0 AA) and will meet the standard applied in ADA enforcement. This is why most compliance programs use WCAG 2.1 AA as a single unifying target.

Recent DOJ Enforcement Trends

DOJ enforcement of digital accessibility has accelerated meaningfully since 2022. Several patterns are relevant:

The Title II final rule (published April 2024) sets specific compliance deadlines for state and local governments: entities with populations of 50,000 or more have two years to comply; smaller entities have three years. This rule converts what was previously a best-practice expectation into a binding regulatory obligation with defined timelines.

The DOJ has pursued enforcement actions against entities ranging from large hospital systems and universities to county government websites. Consent decrees consistently require WCAG 2.1 AA conformance, independent auditing, and multi-year remediation plans.

Private litigation under Title III has continued at high volume. A significant portion of ADA website cases are filed in a small number of federal districts, but courts across the country have held that inaccessible websites constitute ADA violations. Settlements typically require WCAG 2.1 AA conformance and ongoing monitoring.

State attorneys general have also begun enforcing state-level analogues to the ADA, particularly in California, New York, and Massachusetts, often with broader private rights of action than the federal statute.

Why the Distinctions Matter for Federal Contractors

For organizations in the federal contracting space, understanding the boundaries of each framework has direct practical consequences.

A federal contractor focused only on Section 508 may be unaware that its public-facing commercial website carries ADA Title III exposure. The compliance program built for one requirement does not automatically cover the other.

Conversely, a state or local government agency subject to the ADA Title II rule needs to understand that its obligation runs directly from federal civil rights law, not from a contract with a federal agency. The enforcement mechanism, the remediation timeline, and the documentation requirements differ from those of a Section 508 procurement context.

Organizations that operate in both worlds, commercial and federal, need a compliance posture that addresses both frameworks. The technical work largely overlaps (both point to WCAG 2.1 AA), but the documentation, audit methodology, and legal exposure are distinct.

Simkins & Elgazar conducts independent accessibility evaluations for federal contractors, state and local government agencies, and organizations navigating multi-framework compliance requirements. Our manual accessibility audit service covers WCAG 2.1 AA conformance using DHS Trusted Tester methodology. Contact us to discuss your specific compliance obligations.