Section 508 vs WCAG 2026 | How the Federal Standard Uses WCAG

Last updated: 2026-07-09

People often ask whether they should follow Section 508 or WCAG, as if the two were rival checklists. In reality, they are layered on top of each other. WCAG (the Web Content Accessibility Guidelines) is the underlying technical standard that spells out, criterion by criterion, what makes digital content accessible. Section 508 is a section of the US Rehabilitation Act that requires federal agencies and organizations receiving federal funding to make their electronic and information technology accessible — and when the standard was refreshed in 2017, it explicitly adopted WCAG 2.0 Level A and AA as the technical requirements you must meet. In other words, complying with Section 508 largely means conforming to WCAG. The distinction matters because Section 508 adds a legal and procurement layer that plain WCAG does not have: it applies to a specific set of organizations, it operates through administrative enforcement and contracting requirements rather than private lawsuits, and it introduces documentation obligations such as the VPAT (Voluntary Product Accessibility Template). This comparison clarifies exactly how the two relate, which version of WCAG Section 508 currently references, and what each means for your accessibility program in 2026.

At a Glance

Feature Section 508 WCAG (Web Content Accessibility Guidelines)
What it is A US federal law/procurement standard The underlying international technical standard it adopts
Technical requirement WCAG 2.0 Level A and AA (via the 2017 refresh) Its own success criteria; latest version is WCAG 2.2
Who must comply Federal agencies, contractors, and federally funded organizations No one by default; whoever a law or contract obligates
Enforcement Administrative complaints and procurement/contract conditions None directly — depends on the referencing law
Documentation VPAT / Accessibility Conformance Report expected for procurement No standardized document; accessibility statement is best practice
Geographic scope United States (federal sphere) International
Currency of standard Pinned to WCAG 2.0 until the standard is next refreshed Actively maintained; 2.1 and 2.2 add newer criteria

Section 508

Type: US federal accessibility law (Section 508 of the Rehabilitation Act, 29 U.S.C. § 794d) Pricing: No license fee; costs come from auditing, remediation, and producing VPAT/ACR documentation for procurement. Expenses scale with the size and complexity of the systems covered. Best for: Federal agencies, government contractors, universities and organizations receiving federal funding, and technology vendors that sell to the US government and must produce VPAT documentation.

Pros

  • Provides a clear legal mandate with a defined scope: federal agencies and federally funded organizations must make their ICT accessible, removing ambiguity about whether the obligation applies
  • Adopts WCAG 2.0 Level A and AA directly through the 2017 Section 508 Refresh, so the technical requirements are precise and already documented
  • Introduces the VPAT/Accessibility Conformance Report framework, giving vendors a standardized way to disclose how well their product meets the standard during procurement
  • Enforcement is primarily administrative (complaints to agencies or the Access Board), which is typically less financially punishing than the private litigation that drives ADA compliance

Cons

  • Applies only to federal agencies, contractors, and federally funded entities — a private business with no federal ties has no Section 508 obligation
  • It references WCAG 2.0 (from the 2017 refresh), which is now two versions behind WCAG 2.2, so 508 conformance alone may miss newer criteria for mobile and cognitive accessibility
  • The procurement and documentation requirements (VPATs, contract language) add administrative overhead that pure WCAG conformance does not require
  • Enforcement is complaint-driven and can be slow, offering weaker day-to-day compliance pressure than the ADA's private right of action

WCAG (Web Content Accessibility Guidelines)

Type: International technical standard published by the W3C Pricing: Free to read and apply; costs are limited to auditing your content against the criteria and fixing what fails. Best for: Everyone building or maintaining a website; it is the universal technical benchmark whether or not any particular law applies to you.

Pros

  • The actual technical definition of accessibility that Section 508 (and most other laws) point to — meeting WCAG is what 'complying' concretely means
  • Continuously updated: WCAG 2.1 added criteria for mobile, low vision, and cognitive accessibility, and WCAG 2.2 added further improvements, so it reflects current best practice
  • Applicable everywhere, not just to federally connected organizations, making it the right target for any website regardless of who owns it
  • Organized into A/AA/AAA levels so you can set a proportionate goal — most organizations, including Section 508, target Level AA

Cons

  • It carries no legal force by itself; without a law or contract requiring it, WCAG conformance is voluntary
  • Does not include any procurement or reporting framework — there is no WCAG equivalent of the VPAT
  • Full conformance requires manual testing with assistive technology, since automated tools verify only a portion of the criteria
  • Version differences (2.0 vs 2.1 vs 2.2) mean you must confirm which version a specific legal requirement, like Section 508, actually references

Our Verdict

Section 508 and WCAG are not competing checklists — Section 508 is a law that borrows WCAG as its technical yardstick. If you are subject to Section 508, complying with it means, at minimum, conforming to WCAG 2.0 Level A and AA, plus producing the procurement documentation (a VPAT/ACR) that 508 expects. The practical wrinkle is that Section 508 is pinned to WCAG 2.0, while the wider accessibility world — including the ADA's de facto benchmark and the EU's requirements — has moved on to WCAG 2.1 AA and beyond. Our recommendation is to build to WCAG 2.1 Level AA (or 2.2 AA where feasible) as your baseline: doing so automatically satisfies Section 508's WCAG 2.0 requirement, covers the newer mobile and cognitive criteria that 2.0 lacks, and aligns you with the standard that ADA litigation and international law increasingly assume. For federally connected organizations, layer the 508-specific obligations on top: maintain accurate VPATs for the technology you build or buy, include accessibility clauses in vendor contracts, and keep an audit-and-remediation cycle running so conformance does not decay. Treat WCAG as the engine and Section 508 as the legal wrapper around it, and you satisfy both without duplicated effort.

Further Reading

Other Comparisons