Ability Bazaar guide
What is Section 508 compliance?
The short answer
Section 508 of the Rehabilitation Act requires U.S. federal agencies to make covered information and communication technology accessible to employees and members of the public with disabilities. It affects technology agencies develop, procure, maintain or use, subject to the statute and standards.
For covered web content and software, the Revised 508 Standards incorporate WCAG 2.0 Level A and AA by reference. Procurement teams use market research, solicitation requirements, vendor accessibility information and acceptance testing; a VPAT-based ACR is evidence to review, not automatic proof.
Important: This is a practical overview, not legal or procurement advice. Federal buyers and vendors should use their agency's current Section 508 process.
Who has Section 508 responsibilities?
The direct statutory duty falls on U.S. federal agencies. Agency program owners, acquisition teams, developers, content authors and Section 508 coordinators each have roles across the technology life cycle.
Vendors are affected because agencies need information and contract terms that let them evaluate and acquire accessible technology. A vendor may be asked for an ACR, accessibility roadmap, test evidence or remediation commitments.
What does the Revised 508 standard require for websites?
The Revised 508 Standards use WCAG 2.0 Level A and AA for covered web content and apply relevant requirements to non-web software and electronic documents as specified by the standards. Agencies may set newer or additional requirements in a procurement, so vendors should read the solicitation rather than assuming WCAG 2.0 is the only target.
How is Section 508 different from the ADA?
Section 508 is a federal-government technology accessibility law. ADA Title II covers state and local government programs and now has a web and mobile-app rule using WCAG 2.1 Level A and AA. ADA Title III addresses businesses open to the public, but its web obligations are not the same procurement framework as Section 508.
An organization may face more than one accessibility requirement through law, contract or policy. Record each applicable baseline instead of using 'ADA,' '508' and 'WCAG' interchangeably.
What does a sound federal acquisition process include?
- Identify user needs and applicable technical requirements before market research.
- Compare vendor ACRs critically and ask for clarification where remarks are vague.
- Put measurable accessibility requirements, deliverables and remedies in the solicitation and contract.
- Test the delivered product in the agency environment; do not rely only on a document.
- Track defects, remediation dates, exceptions and changed product versions.
- Include people with disabilities and the agency Section 508 program in acceptance decisions.
Frequently asked questions
- Who must comply with Section 508?
U.S. federal agencies have the direct duty for covered information and communication technology they develop, procure, maintain or use.
- Which WCAG version is incorporated into Revised Section 508?
The Revised 508 Standards incorporate WCAG 2.0 Level A and AA, while a solicitation or agency policy may add newer requirements.
- Does an ACR prove Section 508 compliance?
No. It is vendor-provided conformance information that buyers should evaluate alongside the product, procurement requirements and test evidence.
Sources
- U.S. Access Board, Revised 508 Standards and 255 Guidelines
- Section508.gov, IT Accessibility Laws and Policies
- Section508.gov, Buy Accessible Products and Services
- ADA.gov, First Steps Toward Complying with the Title II Web Rule
- ADA.gov, Guidance on Web Accessibility and the ADA
- Section508.gov, Test Websites
Sources were checked on August 21, 2026. Regulations, standards and product documentation can change; follow the linked source for the latest version.