Loading…
Loading…
U.S. federal law requiring government digital products to be accessible to people with disabilities.
stellae.design
Section 508 of the US Rehabilitation Act (1973, refreshed 2017) mandates that federal agencies make their information and communications technology (ICT) accessible to people with disabilities. The 2017 Refresh aligned Section 508 with WCAG 2.0 Level AA for web content and added requirements for software, hardware, and support documentation. In practice, DOJ and GSA guidance increasingly references WCAG 2.1. Section 508 affects federal agencies directly but has massive ripple effects: any vendor selling technology to the US government must demonstrate accessibility through a Voluntary Product Accessibility Template (VPAT) / Accessibility Conformance Report (ACR). The Access Board (access-board.gov) maintains the standards.
Section 508 of the Rehabilitation Act requires all information and communication technology developed, procured, or maintained by U.S. federal agencies to be accessible to people with disabilities, including both federal employees and members of the public. The 2017 refresh aligned Section 508 requirements with WCAG 2.0 AA and incorporated EN 301 549's ICT accessibility framework, creating a consistent baseline that extends beyond web content to software, hardware, and electronic documents. For any organization selling technology to the U.S. government — a market worth hundreds of billions annually — Section 508 conformance is a non-negotiable procurement requirement that directly determines contract eligibility.
A cloud services company bidding on a Department of Veterans Affairs contract is required to submit a VPAT documenting the accessibility conformance of its platform against WCAG 2.0 AA and applicable EN 301 549 clauses. The company's existing VPAT, maintained and updated with each release, demonstrates strong conformance with clearly documented exceptions and remediation timelines. Competing vendors without a current VPAT are unable to complete the procurement evaluation, giving the prepared company a significant competitive advantage.
A federal agency discovers during an internal Section 508 audit that hundreds of public-facing PDF forms lack proper tag structure, reading order, and form field labels, making them unusable for screen reader users. The agency establishes a remediation pipeline that prioritizes the most-downloaded forms first, retagging them with proper heading structure, form labels, and reading order while converting the highest-volume forms to accessible HTML alternatives. The systematic approach clears the critical backlog in six months rather than attempting to fix everything simultaneously.
A software vendor submits a VPAT created for version 2.0 of its product when bidding on a contract that will use version 5.0, assuming that accessibility conformance has not changed across three major releases. The contracting officer discovers significant discrepancies during acceptance testing — new features introduced in versions 3 through 5 have never been evaluated for accessibility, and several introduce barriers that did not exist in the original assessment. The vendor faces contract remediation requirements and risks losing the renewal.
• The most common mistake is treating Section 508 as identical to WCAG 2.0 AA — while the web content requirements align, Section 508 also covers non-web software, hardware, electronic documents, and support documentation, all of which require separate evaluation. Organizations frequently submit VPATs that are outdated, vague, or dishonestly optimistic, only to face consequences during federal acceptance testing when actual conformance does not match the claims. Another error is focusing exclusively on new development while ignoring legacy systems and existing document libraries that are equally subject to Section 508 requirements and equally likely to generate complaints.
Was this article helpful?