Section 508 Compliance and Accessibility Standards

Section 508 is a provision of the Rehabilitation Act of 1973 that requires federal agencies to make their information and communication technology accessible to people with disabilities. Unlike ADA Title II and Title III, which apply to government entities and private businesses respectively, Section 508 is a federal procurement and technology law aimed specifically at the federal government itself and the vendors that sell to it.

What is Section 508, in practical terms today? It’s the legal foundation behind why federal websites, software, electronic documents, and IT systems must meet a specific accessibility standard, and why any company hoping to sell technology to a federal agency needs to prove that standard is met before a contract is signed.

What Is Section 508?

Understanding how Section 508 evolved, and how it differs from the related Section 504, helps explain why the law works the way it does today.

A Brief History — From 1973 to the 2018 Refresh

Section 508 was added to the Rehabilitation Act of 1973, but its most significant accessibility requirements came from a 1998 amendment, which required federal agencies to make electronic and information technology accessible to employees and members of the public with disabilities. For nearly two decades, Section 508 operated under its own separate, product-specific technical criteria rather than a globally recognized standard.

That changed with the Section 508 Refresh, published by the U.S. Access Board in January 2017 and effective January 18, 2018. The refresh replaced the older product-specific rules with a direct incorporation of Web Content Accessibility Guidelines (WCAG) 2.0 Level AA as the technical standard for federal web content and software, reorganizing requirements around functional performance rather than product type. This aligned Section 508 with the same globally recognized standard used elsewhere, rather than maintaining a separate U.S.-only checklist.

Section 508 vs. the Broader Rehabilitation Act

Section 508 is often confused with Section 504, another provision of the same Rehabilitation Act. The distinction is straightforward: Section 508 requires federal agencies to make their own technology accessible, while Section 504 prohibits disability discrimination by any organization receiving federal funding, a category that includes public schools, universities, and healthcare systems well beyond the federal government itself. The two provisions share a legal origin but apply to different types of organizations. This is why making education websites accessible is often discussed under Section 504 rather than Section 508, and why healthcare website accessibility follows the same distinction for many federally funded healthcare organizations.

Who Must Comply

Section 508’s reach depends heavily on an organization’s relationship to the federal government, whether as an agency, a vendor, or neither. Each of these positions carries a different compliance obligation.

Federal Agencies

Section 508 directly applies to federal agencies, as defined under 29 U.S.C. § 794d, requiring that the information and communication technology (ICT) they develop, procure, maintain, or use is accessible. This spans federal websites, internal software systems, electronic documents, and public-facing digital services.

Federal Contractors and Vendors

Section 508 doesn’t directly regulate private companies, but it reaches them indirectly through federal procurement. Any vendor selling ICT products or services to a federal agency must demonstrate that its offering meets Section 508 standards, typically through a completed Voluntary Product Accessibility Template (VPAT), which becomes an Accessibility Conformance Report (ACR) once finalized. A vendor without a current, accurate ACR risks losing a contract or being disqualified from a bid before pricing is even discussed.

Who Is Not Covered

Section 508 does not directly apply to private businesses, nonprofits, or state and local governments operating outside a federal contract or federally funded program. This is one of the more common points of confusion: a private company’s public-facing website is governed by ADA Title III, not Section 508, and a state or local government’s website is governed by ADA Title II. Section 508 only enters the picture when federal money, a federal agency, or a federal contract is directly involved.

What It Requires for Websites and Digital Content

Section 508’s technical requirements apply across three distinct areas: live websites and applications, static electronic documents, and the procurement process vendors go through to sell into the federal government.

Federal Websites and Web Applications

Federal agency websites and web applications must meet WCAG 2.0 Level AA, covering areas like text alternatives for images, keyboard accessibility, sufficient color contrast, and accessible navigation. Because WCAG 2.1 AA is backward-compatible with WCAG 2.0 AA, many agencies now build toward the newer version as a practical matter, even though 2.0 AA remains the formally codified floor under the current standard.

Electronic Documents (PDFs, Word, PowerPoint)

Section 508’s requirements extend well beyond websites to electronic documents, including PDFs, Word files, PowerPoint presentations, and Excel spreadsheets. A federal agency’s inaccessible PDF report or an unremediated internal Word document can trigger the same conformance obligation as an inaccessible webpage, which makes document remediation a frequently overlooked but legally significant part of Section 508 compliance. 

Procurement Requirements for Vendors

Section 508 conformance is typically checked early in the federal buying process, often before a contract is finalized or sometimes before pricing is even discussed. Agencies generally require a VPAT covering the relevant WCAG 2.0 AA criteria, and once reviewed and finalized, that VPAT becomes the ACR used to evaluate the purchase. This document is also increasingly requested by private-sector buyers, particularly during contract renewals, extending its relevance beyond federal procurement alone. An outdated or missing ACR can stall a sale regardless of how accessible the product actually is, since buyers need current documentation on file, not a verbal assurance.

Enforcement and Compliance Risk

Section 508 compliance risk plays out differently depending on whether the organization involved is the federal agency itself or a vendor trying to sell to one.

Administrative Complaints

Individuals who believe a federal agency’s technology fails to meet Section 508 standards can generally file a complaint directly with that agency, which is required to have a formal complaint process, or escalate the matter to the U.S. Access Board, the body responsible for developing and maintaining the Section 508 technical standards. This process differs meaningfully from the private lawsuit model that dominates ADA Title III enforcement, since it runs through an administrative channel tied to the specific agency involved.

Legal and Contractual Risk for Vendors

For vendors, the practical risk of Section 508 non-conformance is less about litigation and more about lost business. A federal agency can decline to award or renew a contract based on an incomplete or unfavorable ACR, and non-conformant vendors risk being excluded from a procurement process entirely before any legal claim is ever filed. That risk compounds over time, since agencies tend to treat a weak ACR history as a signal of how seriously a vendor takes conformance going forward.

This article provides general information only and is not legal advice. Agencies or vendors facing a complaint, procurement dispute, or compliance question related to Section 508 should consult qualified legal counsel.

FAQ

What is Section 508?

Section 508 is a provision of the Rehabilitation Act of 1973 that requires federal agencies to make their information and communication technology, including websites, software, and electronic documents, accessible to people with disabilities. It also indirectly applies to vendors selling ICT products or services to the federal government through procurement requirements.

What is the difference between Section 508 and Section 504?

Section 508 requires federal agencies to make their own technology accessible, while Section 504 prohibits disability discrimination by any organization that receives federal funding, including public schools, universities, and healthcare providers. Both are part of the Rehabilitation Act of 1973, but they apply to different types of organizations.

Does Section 508 require WCAG compliance?

Yes. Since the 2017 Section 508 Refresh took effect in 2018, the U.S. Access Board’s standards directly incorporate WCAG 2.0 Level AA as the required technical benchmark for federal web content and software. Many federal agencies now expect WCAG 2.1 AA in practice, since it’s backward-compatible with the 2.0 AA standard that Section 508 formally requires.

Does ADA Section 508 apply to private companies?

Not directly. Section 508 generally applies to federal agencies and, indirectly, to vendors selling technology to those agencies through procurement requirements. Private companies without a federal contract or federal funding relationship are instead governed by ADA Title III for their public-facing websites.

What does “Section 508 compliance level access” mean?

This phrase generally refers to the specific conformance level, Level AA, that Section 508 requires under its WCAG 2.0 basis, as opposed to the less stringent Level A or the more comprehensive Level AAA. Meeting Level AA means an organization’s technology satisfies both the Level A and Level AA success criteria within WCAG, which is the threshold the Access Board set as the compliance floor.

Is Section 508 the same as the ADA?

No, though the two are frequently confused. Section 508 is a provision of the Rehabilitation Act of 1973 that applies specifically to federal agencies and their vendors, while the ADA is a separate law that applies to state and local governments under Title II and private businesses under Title III. Both reference similar WCAG-based technical standards, but they’re distinct laws with different covered entities.