---
title: "Section 508 explained: U.S. federal ICT accessibility | Quantlix"
description: "Section 508 requires U.S. federal agencies to make the technology they buy and use accessible. See what the Revised 508 Standards cover and how they shape software."
canonical: "https://quantlix.com/en/standards/section-508/"
last-updated: 2026-11-16
---

Source: https://quantlix.com/en/standards/section-508/
Language: en
Description: Section 508 requires U.S. federal agencies to make the technology they buy and use accessible. See what the Revised 508 Standards cover and how they shape software.

**Section 508** [Accessibility](https://quantlix.com/en/standards/#accessibility)

# Section 508: accessible technology in the U.S. federal government

Section 508 is the U.S. law that requires federal agencies to make the information and communication technology they develop, buy, maintain or use accessible to people with disabilities.

[Discuss your project](https://quantlix.com/en/contact/) [Read the key points](https://quantlix.com/en/standards/section-508/#standard-overview)

## At a glance

**Full name**

Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d), implemented through the Revised 508 Standards in 36 CFR Part 1194

**Published by**

U.S. Congress (law) and the U.S. Access Board (standards); GSA supports agencies through Section508.gov

**Type**

U.S. federal law with binding technical standards

**Current version**

Revised 508 Standards, final rule published 18 January 2017, with compliance required from 18 January 2018; incorporates WCAG 2.0 Level A and AA by reference

**Applies to**

Federal departments and agencies, including the U.S. Postal Service, and in practice the vendors whose ICT they buy

**Last reviewed**

November 16, 2026 (2026-11-16)

## In plain terms

### Key points

- Section 508 applies to federal agencies, and procurement carries its requirements to the vendors who sell ICT to them.
- The Revised 508 Standards cover hardware, software, electronic content, documentation and support services.
- Web and non-web content and software must meet WCAG 2.0 Level A and AA, with a few defined exceptions for non-web items.
- ICT that met the earlier 508 standards and has not been altered since 18 January 2018 does not have to be upgraded.

### What is Section 508?

Section 508 is **the part of the U.S. Rehabilitation Act that requires federal agencies to make their information and communication technology (ICT) accessible**. Employees and members of the public with disabilities must be able to use it with access comparable to people without disabilities. The U.S. Access Board writes the technical standards, and the General Services Administration supports agencies through Section508.gov.

The law exists because government technology is unavoidable. A veteran checking benefits, a job applicant or a federal employee using an internal system should not be shut out by a form that a screen reader cannot read. Because agencies buy most of their technology, the law reaches far into the private sector through procurement.

### What the Revised 508 Standards require

- **Functional performance criteria.** Outcomes for users without vision, with limited vision, without hearing, without speech, with limited manipulation or reach and with limited cognitive abilities, applied where the technical requirements do not cover a function.
- **Electronic content.** Public-facing content, plus nine categories of internal agency communication such as emergency notices, decisions on claims, training materials and templates, must meet WCAG 2.0 Level A and AA.
- **Software.** Applications, platforms and mobile apps meet WCAG 2.0 Level A and AA and use platform accessibility services, with authoring tools able to produce accessible content.
- **Hardware.** Devices such as kiosks and printers meet requirements for operable parts, reach, speech output and privacy.
- **Support documentation and services.** Help desks, training and documentation must themselves be accessible and describe accessibility features.

### Key dates and related rules

The original 508 standards date from 2000. The Access Board published the **Revised 508 Standards** as a final rule on 18 January 2017, and agencies have had to follow them since 18 January 2018. The refresh moved from product categories to functions and adopted WCAG 2.0 by reference for both web and non-web content.

A legacy provision protects earlier work: existing ICT that met the original standards and has not been altered since 18 January 2018 does not have to be modified. Once you change its interface, interoperability or access to its data, the altered part must meet the revised standards.

Section 508 is often confused with other U.S. rules. State and local governments follow the ADA Title II rule, which uses WCAG 2.1 Level AA, and telecommunications equipment falls under the separate Section 255 guidelines. Federal guidance on Section508.gov still points to WCAG 2.0 Level AA, so that remains the formal baseline for agencies.

### How it shows up in software projects

- **Conformance reporting.** An Accessibility Conformance Report, usually on the VPAT template, is prepared for each product version and kept current as releases ship.
- **Testing methods.** Automated scans are combined with manual keyboard and screen reader testing, ideally following the testing baselines that federal teams use.
- **Documents.** Generated PDFs, spreadsheets and office files need tags, reading order and alternative text, because non-web documents are in scope.
- **Alterations.** Changes to older systems are tracked, since an altered part loses the legacy protection.
- **Contracts.** Accessibility requirements, acceptance tests and remediation timelines are written into statements of work.

### How we work with Section 508

We help vendors and agency teams build, test and document accessible software: [web applications](https://quantlix.com/en/services/web-application-development/) designed for keyboard and screen reader use, accessible components from our [UX and UI design](https://quantlix.com/en/services/ux-ui-design/) practice, audits of existing products and clear conformance reports. Because we build to [WCAG 2.2](https://quantlix.com/en/standards/wcag-2-2/), the same work also supports European buyers who reference [EN 301 549](https://quantlix.com/en/standards/en-301-549/).

Whether ICT conforms is decided by the agency that procures or uses it, often with independent testing. This page is a plain summary, not legal advice. Our part is accurate testing and evidence that holds up to review. See our wider work in [public and social services](https://quantlix.com/en/industries/public-and-social-services/).

## Where it applies

Industries where this standard often shapes the work.

- ### [Public & Social Services](https://quantlix.com/en/industries/public-and-social-services/)

  Accessible public services, case management and community programs

## Related standards

[All standards](https://quantlix.com/en/standards/)

- WCAG 2.2

  ### [Web content accessibility guidelines](https://quantlix.com/en/standards/wcag-2-2/)

  WCAG 2.2 is the W3C Recommendation that sets testable success criteria for making websites, web apps and digital content usable by people with disabilities, at conformance levels A, AA and AAA.
- EN 301 549

  ### [European ICT accessibility standard](https://quantlix.com/en/standards/en-301-549/)

  EN 301 549 is the European standard that sets accessibility requirements for ICT products and services, from websites and apps to software, documents, hardware and support services.

## Services that support this work

The services we usually bring to projects that involve this standard.

[View all services](https://quantlix.com/en/services/)

### [Web application development](https://quantlix.com/en/services/web-application-development/)

Quantlix designs and builds web applications with responsive interfaces, business logic and system integrations, balancing accessibility, performance and maintainability.

### [UX/UI design](https://quantlix.com/en/services/ux-ui-design/)

Quantlix designs digital experiences through user research, interaction design and visual systems, connecting understandable interfaces to real user tasks.

### [Technology assessment](https://quantlix.com/en/services/technology-assessment/)

Assess operational workflows, data, integrations and AI readiness. Quantlix helps define a bounded Proving Ground and evidence for the next investment decision.

## Questions, answered

What teams usually ask us about this standard.

**Who must comply with Section 508?**

Federal departments and agencies, including the U.S. Postal Service, for ICT they develop, procure, maintain or use. Vendors are not regulated directly, but agencies write the requirements into contracts, so suppliers usually need to show how their products conform.

**Does Section 508 require WCAG 2.1 or WCAG 2.2?**

No. The Revised 508 Standards incorporate WCAG 2.0 Level A and AA by reference. Building to WCAG 2.2 Level AA is still a good choice, because the W3C states that content conforming to 2.2 also conforms to 2.0.

**Does Section 508 apply to state and local governments?**

Not directly. State and local governments fall under the Department of Justice ADA Title II rule, which references WCAG 2.1 Level AA. In April 2026 its compliance dates were extended to 26 April 2027 for larger entities and 26 April 2028 for smaller ones.

**What is a VPAT or an ACR?**

An Accessibility Conformance Report (ACR) documents how a product meets each requirement. Vendors usually build it with the Voluntary Product Accessibility Template (VPAT) from the Information Technology Industry Council, and agencies use it when evaluating offers.

**Is there an official Section 508 certification?**

No. The government does not certify products. Agencies judge conformance through testing and documentation, and Section508.gov publishes guidance, test methods and an ACR library to help.

## Official sources

Read the official text before relying on any detail. What applies to you depends on your role, your location and the version in force.

- [Revised 508 Standards from the U.S. Access Board](https://www.access-board.gov/ict/)
- [Applicability and conformance at Section508.gov](https://www.section508.gov/develop/applicability-conformance/)
- [Extension of ADA Title II web rule compliance dates (2026)](https://www.federalregister.gov/documents/2026/04/20/2026-07663/extension-of-compliance-dates-for-nondiscrimination-on-the-basis-of-disability-accessibility-of-web)

These guides explain each standard in plain terms. They are not legal advice, and they do not state that any product or organization conforms to a standard.

## Planning software around this standard?

Tell us which systems are involved and what you need to show. We will help you build the requirements in from the start.

[Discuss your project](https://quantlix.com/en/contact/)
