Section 508 compliance
Testing, document remediation and ACRs for federal agencies, contractors and vendors.
Federal · Updated October 2026
Section 508 requires federal agencies to develop, buy, maintain and use accessible information and communication technology — and that requirement flows down to every vendor that sells to them.
Section 508 was added to the Rehabilitation Act in 1986 and strengthened in 1998. It requires federal departments and agencies to ensure that the information and communication technology (ICT) they develop, procure, maintain or use is accessible to federal employees and members of the public with disabilities, unless doing so would impose an undue burden.
The US Access Board refreshed the standards in January 2017, and they took effect on January 18, 2018 (36 CFR part 1194). The key changes:
Federal procurement rules (FAR Subpart 39.2) require agencies to consider accessibility when buying ICT. In practice, vendors need:
Section 508 still references WCAG 2.0. Newer laws reference WCAG 2.1 (ADA Title II, HHS Section 504) and the European standard EN 301 549 tracks WCAG 2.1. Because each newer version includes everything in the older ones (apart from the obsolete 4.1.1 Parsing criterion, which 2.2 removed and which modern browsers make moot), testing to WCAG 2.2 AA covers all of them at once.
Each federal agency is responsible for its own compliance. Individuals can file complaints with the agency, and the law provides a private right of action. GSA supports agencies through Section508.gov, and the DOJ reports to Congress on federal compliance.
Not directly. But many states have adopted Section 508 or WCAG by law or policy for their own agencies, and state and local governments are now covered by the ADA Title II rule.
Send us a few URLs or sample PDFs. Within two business days you get a free, plain-English snapshot of your biggest accessibility risks and what it takes to fix them.