Section 508

Section 508 refers to a specific provision of the Rehabilitation Act of 1973 (as amended in 1998) that requires federal agencies to ensure that their electronic and information technology (EIT) is accessible to people with disabilities. This includes federal websites, web applications, software, documents, multimedia, telecommunications equipment, and any other technology that federal employees or members of the public use to access federal information and services. The original Section 508 was added to the Rehabilitation Act by the Workforce Investment Act of 1998. It was a landmark requirement because it established, for the first time, that the federal government had a legal obligation to make its technology accessible. The provision filled a gap that the ADA, while broad in scope, did not specifically address in the context of information technology. In January 2017, the U.S. Access Board published a major update to Section 508 standards (effective January 2018), commonly known as the "Section 508 Refresh." This update replaced the original technology-specific standards with a framework that directly incorporates WCAG 2.0 Level A and Level AA success criteria. This alignment with WCAG brought federal accessibility standards in line with international norms and simplified compliance for organizations working across jurisdictions. Section 508 is significant beyond the federal government because of its cascading effect: federal contractors, vendors, and any organization that provides technology to the government must meet these standards. Given that the U.S. federal government is the world's largest buyer of technology, Section 508 effectively shapes the accessibility practices of much of the technology industry.

Section 508 matters because the federal government touches the lives of virtually every American, and its technology must be usable by all of them — including the approximately 73 million adults with disabilities. **Federal employees with disabilities depend on accessible technology.** The federal government is one of the largest employers of people with disabilities in the United States, with a stated goal of being a model employer. Section 508 ensures that internal systems — email, HR portals, document management, collaboration tools — are usable by employees who use screen readers, keyboard navigation, or other assistive technologies. **The public depends on federal digital services.** Citizens interact with federal technology when they file taxes (IRS), apply for Social Security benefits (SSA), access veterans' services (VA), search for jobs (USAJOBS), check weather (NOAA), and much more. If these systems are inaccessible, people with disabilities cannot independently access critical government services. **Section 508 shapes the broader technology market.** Because the federal government spends over $100 billion annually on information technology, its accessibility requirements influence product development across the industry. Companies that want to sell to the government must build accessible products, and those accessibility improvements often carry over to commercial offerings used by the general public. **Section 508 compliance is increasingly audited.** The DOJ publishes biennial assessment reports on federal agency compliance with Section 508. The most recent reports have highlighted significant gaps, leading to increased attention and investment in accessibility programs across agencies. Congressional oversight has also increased, with agencies facing questions about their Section 508 compliance during appropriations hearings.

Section 508 operates through two primary mechanisms: technical standards that define what "accessible" means, and procurement requirements that ensure accessible technology is purchased. ### Technical Standards (The 508 Refresh) Since January 2018, Section 508 technical standards are organized into several chapters: **Web content and electronic documents** must conform to WCAG 2.0 Level A and Level AA success criteria. This applies to federal websites, intranets, web applications, PDFs, Word documents, spreadsheets, presentations, and any other content delivered electronically. **Software applications** must meet requirements for user interface components, including compatibility with assistive technologies through platform accessibility APIs (such as UI Automation on Windows or the Accessibility API on macOS). Native applications must provide text alternatives, keyboard accessibility, proper focus management, and accessible name/role/state information. **Hardware** must meet requirements for physical accessibility, including reach ranges, operable parts, and compatibility with assistive technologies. This covers kiosks, ATMs, copiers, and other physical equipment with digital interfaces. **Support documentation and services** must be accessible. If a product includes user guides, installation instructions, or help desk services, those must also be accessible to people with disabilities. ### Procurement (The "Buy Accessible" Requirement) Section 508 requires federal agencies to consider accessibility when procuring technology. In practice, this means: 1. **Market research**: Agencies must investigate whether accessible products are available. 2. **Solicitation requirements**: RFPs and contracts must include Section 508 requirements. 3. **Evaluation**: Agencies evaluate vendor accessibility claims, typically through VPATs/ACRs. 4. **Acceptance testing**: Agencies should verify accessibility claims during acceptance testing. The exception process allows agencies to invoke an "undue burden" exception if compliance would impose significant difficulty or expense, but this requires documented justification and the agency must still provide alternative access. ### Voluntary Product Accessibility Template (VPAT) The VPAT is a standardized document format in which vendors describe how their product or service meets Section 508 standards. The completed document is called an Accessibility Conformance Report (ACR). Federal procurement officials review ACRs to compare the accessibility of competing products. The ITIC publishes three VPAT versions: one for Section 508, one for EN 301 549 (European standard), and one for WCAG — or an "International" edition that covers all three.

**Federal website redesign**: When the Social Security Administration redesigns its online services portal, it must ensure the new site conforms to WCAG 2.0 Level A and AA. This includes making the benefits application process keyboard accessible, ensuring all forms have proper labels, providing text alternatives for informational images, and making PDF notices available in accessible HTML format. **Software procurement**: A federal agency evaluating cloud-based project management tools requests VPATs from three competing vendors. Vendor A provides a detailed ACR showing full WCAG 2.0 Level AA conformance with supporting audit evidence. Vendor B's ACR shows multiple partial conformance items. Vendor C has no VPAT. The agency selects Vendor A, in part because of its superior accessibility conformance. **Internal document accessibility**: A federal agency publishes policy documents as PDFs. Under Section 508, these PDFs must be tagged with proper heading structure, reading order, alt text for images, and data table markup. The agency trains its staff on creating accessible documents and implements quality checks before publication. **Federal contractor obligations**: A web development firm wins a contract to build a new citizen-facing portal for a federal agency. The contract specifies Section 508 conformance. The firm must test the portal against WCAG 2.0 Level AA, document conformance in a deliverable, and remediate any issues before the agency accepts the work.

**Assuming Section 508 only applies to websites.** Section 508 covers all electronic and information technology: websites, software, mobile apps, documents, multimedia, kiosks, telecommunications equipment, and more. Organizations frequently overlook document accessibility (PDFs, Word files) and internal software systems. **Confusing current Section 508 standards with the original 1998 standards.** The 2017 refresh fundamentally changed the standards by incorporating WCAG 2.0. Organizations still referencing the original "1194" standards (e.g., "1194.22 Web-based intranet and internet information") are working from outdated requirements. **Treating VPATs as a rubber stamp.** Some vendors produce VPATs that overstate conformance. Federal agencies should not accept a VPAT at face value — they should conduct their own testing or hire independent auditors to verify vendor claims. An inaccurate VPAT can lead to purchasing inaccessible technology. **Applying the undue burden exception too broadly.** The undue burden exception is meant for truly exceptional circumstances, not as a general-purpose escape valve. When invoked, the agency must still provide equivalent access through alternative means and must document the justification. Agencies that routinely claim undue burden risk DOJ enforcement action. **Not updating to reflect WCAG 2.1 or 2.2.** While Section 508 technically references WCAG 2.0, the Access Board and GSA have encouraged agencies to look beyond the minimum standard. Given that ADA Title II now references WCAG 2.1, and the broader industry has moved to 2.1/2.2, organizations that only target WCAG 2.0 may find themselves falling behind regulatory expectations.