WCAG & Section 508

2025-10-08 12:00:00 +0000

Many people treat “WCAG” and “Section 508” as interchangeable terms. They are closely related, but they are not the same thing. Understanding the difference helps you choose the right target, produce the right documentation, and avoid common compliance mistakes.

What is WCAG?

The Web Content Accessibility Guidelines (WCAG) are an international technical standard published by the World Wide Web Consortium (W3C). They define how to make web content more accessible to people with disabilities.

Key characteristics:

  • Technology-neutral (can be applied to HTML, PDFs, mobile apps, etc.)
  • Organized around the four POUR principles
  • Contains testable success criteria at three levels: A, AA, and AAA
  • Current recommended versions for most organizations: WCAG 2.1 or 2.2 Level AA

WCAG itself is not a law. It becomes legally relevant when a regulation, contract, or court decision references it.


What is Section 508?

Section 508 is a U.S. federal law (part of the Rehabilitation Act of 1973, refreshed in 2017). It requires federal agencies — and the companies that sell information and communication technology (ICT) to them — to make their digital products accessible.

Key characteristics:

  • Applies to federal agencies and federal contractors
  • Covers websites, software, electronic documents, and other ICT
  • Adopts WCAG 2.0 Level A and AA as the technical standard for web content
  • Requires formal documentation, usually in the form of a Voluntary Product Accessibility Template (VPAT) that becomes an Accessibility Conformance Report (ACR)

Because WCAG 2.1 and 2.2 are backward-compatible with 2.0, meeting the newer versions also satisfies Section 508 requirements.

A11y Roles pie chart

Accessibility Issues (WCAG Failure Type)
Guidelines (WCAG) 2 Failures:

  • Websites with at least one WCAG 2 failure - 95.9%
  • Low Contrast test - 81.0%
  • Missing alt text for images - 54.5%
  • Empty links - 44.6%
  • Missing document language - 17.1%

Side-by-Side Comparison

Aspect WCAG Section 508
Type International technical standard U.S. federal law
Who creates it W3C (Web Accessibility Initiative) U.S. Access Board / Congress
Who must follow it Anyone whose law, contract, or policy references it Federal agencies and their contractors
Technical standard WCAG 2.0 / 2.1 / 2.2 (A, AA, or AAA) WCAG 2.0 Level A and AA (for web content)
Scope Primarily web content (can be applied more broadly) Web + non-web ICT (software, documents, hardware interfaces)
Documentation Conformance claims, audit reports, accessibility statements VPAT / ACR is the expected format
Geographic reach Global United States (federal)

How They Relate to the ADA

The Americans with Disabilities Act (ADA) is a separate civil-rights law. Title II covers state and local governments; Title III covers public accommodations (private businesses). Neither Title originally named a specific technical standard for websites. Courts and the Department of Justice have long looked to WCAG as the most widely accepted measure of accessibility. The 2024 Title II web and mobile rule now explicitly requires WCAG 2.1 Level AA for many public entities.

In short:

  • Section 508 = federal agencies and contractors
  • ADA Title II = state and local government (now with an explicit WCAG 2.1 AA requirement)
  • ADA Title III = private businesses open to the public (WCAG is the de-facto standard used in litigation)

Practical Implications

If you work with federal contracts, you will almost always be asked for a current VPAT/ACR that maps to Section 508 (WCAG 2.0 A/AA). Meeting WCAG 2.1 or 2.2 Level AA satisfies that requirement and also prepares you for broader ADA expectations.

If you are a state or local government entity, school district, or public university, the DOJ Title II rule points you to WCAG 2.1 Level AA. Section 508 documentation practices (clear reporting, independent testing) remain useful even when 508 itself does not apply.

Automated scan reports alone are rarely accepted as sufficient evidence under either framework. Manual evaluation by trained testers produces the kind of documentation that holds up in procurement reviews and legal settings.


Key Takeaway

WCAG is the technical standard. Section 508 is one important U.S. law that adopts part of that standard. Knowing the difference lets you target the right version, produce the right documentation, and avoid treating an automated report as proof of compliance.

In the next post we examine the four POUR principles — the foundation that every WCAG success criterion rests on.

Next in the series: POUR Web Design

Start Your Compliance Journey Today

Speak with a DHS Certified Trusted Tester about securing your Proof of Compliance Certificate (POCC). Learn how to ensure your digital assets confidently meet state, federal, and enterprise procurement requirements under ADA Title II & III, WCAG 2.2, and Section 508 Standards.

Schedule Free Consultation

Kaffeinated Kodemonkey logo seal.

MonkeyHub

  • Aticles & News — Evolving insights on digital accessibility legislation, design practices, and corporate risk mitigation from beginner to enterprise scale. Articles & News
  • Learning Center —

    Learning center

  • MonkeySupport — Have an Accessibility Question? Submit a Ticket and our team will see how we can help. Support Ticket