What Is Section 508 Compliance?
Section 508 is a US federal law — part of the Rehabilitation Act of 1973 — that requires federal agencies to make their electronic and information technology, including websites, accessible to people with disabilities. The 2018 refresh of its standards formally adopts WCAG 2.0 Level AA as the technical benchmark. Section 508 directly governs federal agencies and often extends to their contractors and grant recipients, making it a key standard for any business working with the federal government.
- Legal basis
- Section 508 of the Rehabilitation Act of 1973, amended 1998 (U.S. law)
- Technical standard
- 2018 refresh incorporates WCAG 2.0 Level AA (U.S. Access Board)
- Who it binds
- Federal agencies, and commonly their contractors and vendors (industry-typical)
- Related law
- Distinct from the ADA, which covers private businesses (U.S. law)
What is Section 508 and who must comply? #
Section 508 is a provision of the Rehabilitation Act of 1973, significantly strengthened by a 1998 amendment, that requires US federal agencies to ensure their electronic and information technology is accessible to people with disabilities — both federal employees and members of the public who use government services. This covers websites, web applications, software, documents, and other digital content. The direct legal obligation falls on federal agencies, but its reach is broader in practice: companies that sell technology or services to the federal government, and organizations receiving federal funds, are frequently required by contract to meet Section 508 standards. So while a typical local plumber or dentist is governed by the ADA rather than Section 508, any business bidding on federal contracts, building government websites, or partnering with agencies must understand it. For businesses in that position, we build to Section 508 standards through /services/web-design and /services/web-app-development from the outset.
Section 508 and WCAG #
For much of its history, Section 508 had its own set of technical accessibility requirements. That changed with the 2018 'refresh' issued by the US Access Board, which modernized the standards and, crucially, adopted WCAG 2.0 Level AA as the technical benchmark for web content and many other electronic documents. This harmonization means that in practice, complying with Section 508 for a website largely means meeting WCAG 2.0 AA — the same internationally recognized success criteria used elsewhere. Because WCAG 2.1 and 2.2 build on and include 2.0, a site meeting the newer WCAG 2.1 AA also satisfies the Section 508 web requirements. This alignment simplifies things enormously: a business does not need to satisfy two entirely different rulebooks, but rather one core standard. Our /wiki/what-is-wcag entry explains those success criteria in depth, and understanding WCAG is effectively understanding the technical heart of Section 508 for web content.
Section 508 versus the ADA #
Section 508 and the Americans with Disabilities Act are both US disability laws, but they apply to different entities and it is important not to confuse them. Section 508 governs the federal government's own technology and, through contracts, those who supply it. The ADA is a broad civil-rights law prohibiting disability discrimination by private businesses open to the public — restaurants, gyms, law firms, retailers, and service providers — as well as state and local governments. A local business's website is almost always an ADA matter, not a Section 508 matter, unless it works with federal agencies. The practical convergence is that both effectively point to WCAG AA as the technical standard: Section 508 formally adopts it, and courts apply it under the ADA. So regardless of which law applies to you, building to WCAG 2.1 AA satisfies the technical expectation. Our /wiki/what-is-ada-website-compliance entry covers the private-business side, and together the two explain the full US accessibility landscape.
What Section 508 covers technically #
Because the 2018 refresh adopts WCAG 2.0 AA for web content, Section 508's technical requirements for websites mirror WCAG's four principles. Content must be perceivable — text alternatives for images, captions for video, sufficient color contrast, and content that adapts to different presentations. It must be operable — full keyboard access, no keyboard traps, enough time to complete tasks, and no seizure-inducing flashing. It must be understandable — readable text, predictable behavior, and input assistance that helps users avoid and correct errors, which matters for /wiki/what-are-accessible-forms. And it must be robust — valid, well-structured code that works reliably with assistive technologies like screen readers. Beyond web pages, Section 508 also addresses electronic documents such as PDFs, software applications, and hardware, but for most website work the WCAG-aligned web requirements are the focus. Meeting these criteria is the same technical effort as any WCAG AA project, which is why our accessible build process serves both audiences.
Why Section 508 matters to private businesses #
Even though Section 508 directly binds federal agencies, it matters to many private companies for concrete reasons. First, the federal government is an enormous purchaser of technology and services, and 508 compliance is typically a hard requirement to win or keep those contracts — a non-compliant website or application can disqualify a bid. Second, organizations receiving federal grants or funds are often contractually obligated to meet 508 standards. Third, some state governments have adopted their own laws mirroring Section 508 for state agencies and their vendors, extending the reach further. For a business pursuing government work — a contractor, a software vendor, a consultancy, or a nonprofit with federal funding — Section 508 conformance is a gating requirement, not an optional nicety. Building to the standard from the start avoids costly rework later. We help businesses in these situations meet the requirement through accessible /services/web-design, /services/web-app-development, and ongoing /services/care-plans that keep conformance intact.
How Section 508 conformance is documented #
In the federal procurement world, accessibility conformance is often documented using a standardized template. Vendors selling to the government commonly provide a VPAT (Voluntary Product Accessibility Template), which produces an Accessibility Conformance Report describing how a product meets each applicable Section 508 and WCAG requirement — noting whether each criterion is supported, partially supported, or not supported, with explanations. Agencies use these reports to evaluate whether a product meets their obligations before purchasing. For a business selling software or web services to the government, being able to produce an accurate, honest conformance report is often part of the sales process. This documentation is grounded in the same testing an accessibility audit provides — combining automated scanning with manual keyboard and screen reader evaluation. Our /tools/website-grader and /tools/ada-compliance-checker offer a starting point for assessing web content, while a full manual review supports the detailed reporting that federal buyers expect. Accurate documentation matters, since overstating conformance can create contractual and legal exposure.
Testing for Section 508 compliance #
Because Section 508's web standard is WCAG 2.0 AA, testing for it uses the same methodology as any WCAG audit. It begins with automated scanning to quickly surface detectable issues like missing alt text, low contrast, empty controls, and missing form labels. It then requires manual testing that automation cannot replace: navigating with only a keyboard to confirm full operability and visible focus, testing with screen readers such as JAWS, NVDA, and VoiceOver to verify content is announced meaningfully, checking reading order and heading structure, and validating that forms and dynamic content are accessible. Documents like PDFs distributed by the site must be tested for proper tagging and structure too. The combination of automated breadth and manual depth produces an accurate conformance picture. Since automated tools catch only part of the criteria, manual evaluation is essential for a defensible 508 conformance claim. This is the same rigorous process described in /wiki/what-is-an-accessibility-audit, applied with federal reporting requirements in mind.
Meeting Section 508 in practice #
For a business that needs to meet Section 508, the path is clear and aligns with general accessibility best practice. Build or remediate the website to WCAG 2.1 AA, which fully satisfies the 508 web requirements and future-proofs against updates. Use semantic HTML, ensure complete keyboard operability with visible focus, provide text alternatives and captions, maintain sufficient contrast, and make forms and dynamic content accessible with correct labels and, where needed, ARIA. Test with both automated tools and manual keyboard and screen reader evaluation, and remediate PDFs and other documents you distribute. Produce accurate conformance documentation such as a VPAT if you sell to the government. Then maintain conformance over time, since new content and updates can introduce barriers. Whether you are a contractor building a federal site or a vendor needing a compliant product, we deliver Section 508-aligned work through /services/web-design and /services/web-app-development and keep it compliant with ongoing monitoring via /services/care-plans.
FAQ
Does Section 508 apply to my private business?
Usually only if you work with the federal government. Section 508 directly binds federal agencies and, through contracts, their vendors and grant recipients. A typical local business is governed by the ADA instead. However, if you bid on federal contracts, build government sites, or receive federal funds, Section 508 compliance is often a contractual requirement you must meet.
What is the difference between Section 508 and the ADA?
Section 508 requires federal agencies (and often their contractors) to make technology accessible, formally adopting WCAG 2.0 AA. The ADA is a broader civil-rights law covering private businesses open to the public. Most local business websites fall under the ADA, not Section 508. In practice both point to WCAG AA as the technical standard, so building to it satisfies either.
Which WCAG version does Section 508 require?
The 2018 refresh of the Section 508 standards, issued by the US Access Board, adopts WCAG 2.0 Level AA as the technical benchmark for web content. Because WCAG 2.1 and 2.2 include and extend 2.0, meeting the newer WCAG 2.1 AA also satisfies the Section 508 web requirements while providing additional mobile and cognitive accessibility coverage.
What is a VPAT?
A VPAT (Voluntary Product Accessibility Template) is a standardized document vendors use to report how a product meets Section 508 and WCAG requirements, producing an Accessibility Conformance Report. It states whether each criterion is supported, partially supported, or not supported, with explanations. Federal agencies use VPATs to evaluate products before purchase, so vendors selling to the government often must provide one.
How do I test my website for Section 508 compliance?
Test it the same way you would for WCAG 2.0 AA. Start with automated scanning to catch detectable issues, then perform manual testing: keyboard-only navigation, screen reader testing with JAWS, NVDA, or VoiceOver, and checks of contrast, structure, forms, and any PDFs. Automated tools alone are insufficient, so manual evaluation is essential for a defensible conformance claim.
Do PDFs and documents fall under Section 508?
Yes. Section 508 covers electronic documents, including PDFs distributed through a website, as well as software and hardware. PDFs must be properly tagged with headings, alt text, and logical reading order to be accessible. Untagged or scanned PDFs that are effectively images fail the standard and must be remediated or offered as accessible HTML alternatives.
Was this helpful?