Case Studies

Accessible Government Websites: Section 508 Compliance in Practice

By EZUD Published · Updated

Accessible Government Websites: Section 508 Compliance in Practice

Section 508 of the Rehabilitation Act requires U.S. federal agencies to ensure that their information and communication technology is accessible to people with disabilities. Despite being law since 1998, with updated technical standards adopted in 2017, federal compliance remains uneven. This article examines the current state of Section 508 implementation, what agencies are doing well, and where significant gaps persist.

What Section 508 Requires

The Revised 508 Standards, maintained by the U.S. Access Board, incorporate WCAG 2.0 Level A and AA success criteria as the baseline for web content. In practice, most agencies now target WCAG 2.1 Level AA to stay ahead of likely future updates. The standards cover all ICT procured, developed, maintained, or used by federal agencies, including websites, mobile apps, documents, software, kiosks, and telecommunications equipment.

Under Section 508, agencies must give employees and members of the public with disabilities access to information comparable to the access available to others. This applies to both internal systems used by federal employees and public-facing services.

Recent Policy Developments

In December 2023, the Office of Management and Budget issued Memorandum M-24-08, “Strengthening Digital Accessibility and the Management of Section 508 of the Rehabilitation Act.” This memorandum requires federal agencies to:

  • Maintain a public accessibility statement on their websites.
  • Designate a Section 508 program manager.
  • Report accessibility metrics annually through the GSA.
  • Incorporate accessibility requirements into procurement processes for all ICT.

The GSA has released three annual reports on federal Section 508 compliance, finding that while acquisition and procurement practices have strengthened, the federal government continues to fall short of its legal obligations to ensure equal access.

Where Agencies Succeed

Several agencies have built strong accessibility programs that serve as models:

The Department of Veterans Affairs has one of the most mature Section 508 programs, with dedicated accessibility testing teams, mandatory training for web developers, and an established process for handling accessibility complaints.

GSA’s Section508.gov serves as the central resource for the entire federal government, providing training, tools, and policy guidance. The site itself demonstrates compliance with the standards it promotes.

The Social Security Administration offers its online services with screen reader compatibility, keyboard navigation, and alternative formats for documents, reflecting the fact that a significant portion of its user base includes people with disabilities.

Where Agencies Fall Short

The GSA’s compliance reports reveal persistent gaps:

  • Legacy systems. Many federal agencies run internal applications built decades ago on platforms that predate modern accessibility standards. Retrofitting these systems is expensive and technically challenging.
  • PDF documents. Federal agencies publish millions of PDF documents, and a large percentage lack proper tagging, reading order, and alternative text. PDFs remain one of the most common sources of inaccessible government content.
  • Third-party procurement. When agencies purchase commercial software or contract with outside developers, accessibility requirements are sometimes omitted from contracts or not enforced during acceptance testing.
  • Mobile apps. While many agencies have launched mobile apps, accessibility testing for mobile platforms is less mature than for web content.

The Broader Government Accessibility Landscape

Section 508 applies only to federal agencies, but the accessibility requirements for state and local government are tightening as well. In April 2024, the Department of Justice published a final rule under Title II of the ADA requiring state and local government websites and mobile apps to conform to WCAG 2.1 Level AA. Entities serving populations of 50,000 or more must comply by April 2026, with smaller entities having until April 2027.

This rule is particularly significant for public services like libraries, public transit systems, courts, and local government portals. For the first time, there are specific technical standards, not just general nondiscrimination obligations, for state and local government digital content.

Practical Recommendations

Organizations working with or within government can improve accessibility by building 508 requirements into RFPs and contracts from the start, not as an afterthought. Automated testing tools can catch roughly 30-40% of accessibility issues, but manual testing with screen readers and keyboard-only navigation remains essential for full compliance. Training content creators, not just developers, on accessible document practices addresses the PDF problem at its source.

For related case studies in regulated industries, see our articles on banking and finance accessibility and healthcare digital accessibility. For the broader landscape, visit the universal design case studies guide.

Key Takeaways

  • Section 508 requires federal ICT to meet WCAG 2.0 Level A and AA standards, with most agencies now targeting WCAG 2.1 Level AA.
  • OMB Memorandum M-24-08 (2023) added requirements for public accessibility statements, designated program managers, and annual reporting.
  • Legacy systems, inaccessible PDFs, and inconsistent procurement practices remain the most common compliance gaps.
  • The 2024 ADA Title II rule extends specific WCAG 2.1 Level AA requirements to state and local government digital content for the first time.

Sources