Skip to main content

Digital Accessibility and Section 508: Keeping Government Services Accessible After Launch

Section 508 responsibility does not end at launch. How agencies assign accessibility ownership across procurement, delivery, and maintenance.

Max Syed
November 3, 2026

For the team running an online government application, accessibility means more than passing a pre-launch review. A person using a screen reader should be able to complete the form without help. So should someone who navigates by keyboard because they cannot use a mouse.

Yet an accessible service can become difficult to use after a routine update. A new form may have fields without proper labels. A PDF may be published without the structure needed by assistive technology. A software update may change how keyboard navigation works. These problems often appear after the original accessibility review has been completed.

Section 508 of the Rehabilitation Act requires federal agencies to make covered information and communication technology (ICT) accessible to people with disabilities. The responsibility applies when technology is developed, purchased, maintained, or used. For organizations managing digital services, that means accessibility must remain part of procurement, software delivery, content publishing, and ongoing maintenance.

What Federal Accessibility Assessments Found

Federal assessments show that accessibility requirements are more consistently included in procurement than verified after delivery.

The General Services Administration’s (GSA) Fiscal Year 2025 Governmentwide Section 508 Assessment, published in March 2026, examined accessibility practices across federal organizations.

Among 60 reporting agencies:

  • 48% said they almost always included accessibility requirements in solicitations.
  • Fewer than one in three said they almost always verified that delivered technology met Section 508 requirements.
  • 26% said they rarely or never verified accessibility conformance when technology was delivered.

The difference matters. A contract may include the correct accessibility language, but that does not establish whether the software or document delivered under the contract meets the standard.

Testing results from the same assessment showed another concern. Of the electronic documents tested by reporting agencies, only 38% were fully conformant. For tested public-facing web pages, the figure was 72%.

These percentages describe tested items reported by participating agencies, not all federal documents and websites. GSA also notes that agencies self-reported their data without independent validation. The results show why accessibility work extends beyond software development. Content authors, procurement staff, document publishers, and employees responsible for maintaining existing services all influence whether people can use them.

A separate 2024 Government Accountability Office (GAO) report identified a different concern: agencies in an earlier GSA assessment that had no formal ICT accessibility program or were still developing one. The assessment methods changed between reporting years, so these findings should be treated as separate snapshots rather than evidence of improvement or decline.

The practical concern remains: accessibility requirements need a process for confirming that the work was completed.

Start by Understanding What Technology Needs Review

Before arranging accessibility testing across every existing system, an organization should establish what technology it owns, which standards apply, and what has changed. GSA’s FY 2025 assessment found that 19 of the 60 reporting agencies could not estimate how many public-facing web pages they operated. Other agencies could not estimate their holdings in categories such as software, hardware, or electronic documents.

An incomplete technology inventory makes accessibility planning harder. Without knowing which services and documents exist, an organization cannot reliably determine which ones have been tested or need attention. The first review should establish which systems are currently in use, when they were last assessed, and whether changes have affected their accessibility.

For older technology, this also means examining Section 508’s safe-harbor provision.

How Section 508 Safe Harbor Works

The Revised 508 Standards took effect on January 18, 2018. They include a provision for certain existing ICT that complied with the previous standards.

Under this provision, qualifying older components generally do not have to be updated to meet the revised standards if they have remained unaltered. The exception applies to individual components rather than automatically covering an entire system.

An alteration includes a change affecting interoperability, the user interface, or access to information or data. When a qualifying component is altered, the changed portion must meet the Revised 508 Standards. A minor maintenance activity that does not affect those characteristics does not necessarily remove safe-harbor eligibility.

Organizations relying on the provision need evidence that the older component met the applicable original standards and that subsequent changes have not removed its eligibility. Section508.gov advises against relying on safe harbor where that earlier conformance cannot be demonstrated.

An inventory that records previous testing, system changes, and affected components helps teams determine which technology may qualify and where additional review is needed. The purpose is to establish the work required under the applicable standard, using evidence rather than assumptions about a system’s age.

Section 508 and WCAG 2.2

The Revised 508 Standards incorporate the Web Content Accessibility Guidelines (WCAG) 2.0 Level A and AA requirements for covered web content.

WCAG 2.2, published by the World Wide Web Consortium in October 2023, adds nine success criteria beyond WCAG 2.1. It also builds on earlier versions. Federal Section 508 requirements do not automatically change to WCAG 2.2 because that newer standard exists.

An organization may choose to use WCAG 2.2 as an internal standard or include it in contracts. Such a decision should be distinguished from the baseline established by the Revised 508 Standards.

Assign Responsibility Across Procurement, Delivery, and Maintenance

Accessibility responsibilities are often shared between several departments. The work becomes harder to manage when nobody knows who must review a particular change or approve a correction.

A useful approach is to establish clear ownership across three stages.

Procurement: Acquisition staff should identify the accessibility requirements that apply to a purchase, obtain relevant vendor conformance information, and arrange for that information to be evaluated before accepting the deliverable.

Delivery: The team responsible for releasing a service should confirm what was tested, which standards were used, what problems remain, and who approved the release under applicable procedures.

Maintenance: After launch, someone needs to review changes that may affect accessibility. This includes software updates, new content, replacement documents, and changes to third-party components.

The handoffs matter. Procurement records should reach the delivery team, and testing results should remain available to those maintaining the service.

A policy may clearly state that accessibility is required. The engineer shipping Tuesday’s release still needs to know who can answer an accessibility question, which findings block release, and who can authorize the next step.

Section508.gov describes the Section 508 Program Manager as a coordinating role across the organization. That role helps provide oversight, while individual teams remain responsible for their assigned work.

Give Content Authors and Procurement Staff the Right Training

Employees who create documents should understand headings, reading order, alternative text, and accessible forms. Procurement staff should know how to examine accessibility documentation and arrange appropriate acceptance checks. Engineers need to understand keyboard operation, accessible names, and how changes affect assistive technology.

Training should reflect each employee’s responsibilities.

An organization with an existing accessibility program may need clearer assignments and better follow-up rather than an entirely new program.

Keep Accessibility Evidence Connected to the Work

Accessibility testing produces useful information, but the record can become outdated when a system changes.

A service might pass its launch assessment and later introduce an inaccessible form. The earlier test remains valid evidence of what was checked at the time, although it no longer describes every part of the current service.

Organizations should maintain a record connecting accessibility requirements to test results, findings, corrective actions, approvals, and later changes. For example, when a vendor delivers a software update, the release record can identify which components changed, whether accessibility testing was required, what was tested, and whether any findings remain unresolved.

This gives managers a way to review current issues without reconstructing the history from emails and separate documents. For evidence requiring stronger integrity protection, GovSoft recommends considering measures such as append-only logs, write-once-read-many storage, or cryptographic hashing to help detect unauthorized changes.

Which approach makes sense depends on the organization’s existing systems and the kind of evidence it needs to preserve.

Section 508 does not generally mandate those specific storage methods. The objective is to maintain reliable records of accessibility work and decisions.

Where AI and Automated Testing Can Help

Automated accessibility tools can identify certain problems more quickly than checking every page or document manually.

They may detect missing alternative text, some labeling errors, structural problems, or code patterns that violate accessibility rules. AI may also help organize findings, compare versions of a document or interface, and prepare summaries for reviewers.

However, automated testing cannot establish complete accessibility conformance.

A tool may recognize that an image has alternative text without knowing whether that description is meaningful. It may detect the technical structure of a form without confirming that someone using assistive technology can complete the transaction.

Human testing remains important, including testing with people who use assistive technology.

The FY 2025 GSA assessment found that only 12% to 17% of reporting agencies conducted usability testing with people with disabilities before deployment, depending on the type of technology. Automated tools are useful for identifying potential problems and helping teams decide what needs review. Qualified people must still evaluate findings and confirm whether corrective work addresses the user’s difficulty.

How GovSoft Approaches Digital Accessibility

GovSoft focuses on helping government and regulated organizations organize accessibility responsibilities, findings, and follow-up work around the services they operate.

The approach begins by reviewing the organization’s existing accessibility program, technology inventory, and available testing records. This helps establish which systems need assessment, which older components may qualify for safe harbor, and where responsibilities are unclear.

GovSoft works with the organization’s accessibility specialists and, when necessary, appropriate third-party testing tools or services. The proposed workflow connects accessibility requirements to the employees responsible for procurement, delivery, and maintenance. It also supports tracking findings and recording the decisions made as problems are addressed.

Training can be included for employees whose responsibilities affect accessibility, including document authors, procurement staff, and engineering teams. For organizations already operating an accessibility program, the starting point is reviewing where existing processes lose information or leave issues without clear ownership.

The first useful question is which services people currently struggle to use and whether the organization has a documented process for resolving those problems.

Accessibility work should ultimately be measured by what people can accomplish. A completed review matters, but so does whether someone using a screen reader can finish an application, read a notice, or submit a required form.

To discuss an accessibility program review, say hi at hello@govsoft.com or visit govsoft.com.

Key Takeaways

  • Section 508 responsibilities continue through procurement, development, maintenance, and use of covered technology.
  • Safe harbor applies only to qualifying older ICT components. Changes affecting accessibility-related characteristics require careful review.
  • GSA’s FY 2025 findings show a gap between including accessibility requirements in contracts and verifying delivered technology.
  • Accessibility responsibilities should be assigned across procurement, delivery, content publishing, and maintenance.
  • Automated testing can identify many problems, but human evaluation and reliable records remain necessary.

Frequently Asked Questions

What Section 508 requires

Section 508 requires federal agencies to make covered ICT accessible to employees and members of the public with disabilities, subject to applicable standards and exceptions.

Section 508 and PDFs

Covered electronic documents, including PDFs, must meet applicable accessibility requirements. This may involve readable text, correct document structure, accessible tables, and appropriate descriptions of non-text content.

How often to test for Section 508

Testing should be incorporated into the development and maintenance process, particularly when changes may affect accessibility. Section 508 does not establish one universal testing interval for every system.

What automated tools can prove

Automated testing identifies certain technical problems but cannot evaluate every accessibility requirement or confirm that people using assistive technology can complete a task.

References & sources

  1. Section 508 of the Rehabilitation Act, 29 U.S.C. § 794d, Laws and Policies , Section508.gov, U.S. General Services Administration
  2. Information and Communication Technology (ICT) Standards and Guidelines, Revised 508 Standards , U.S. Access Board
  3. Federal Accessibility: OMB Is Tracking Agency Implementation of Its Guidance on Information and Communication Technology (GAO-24-107031) , U.S. Government Accountability Office
  4. Fiscal Year 2025 Governmentwide Section 508 Assessment , U.S. General Services Administration
  5. Revised 508 Standards, Safe Harbor, and FAR Update , Section508.gov, U.S. General Services Administration
  6. Web Content Accessibility Guidelines (WCAG) 2.2 , World Wide Web Consortium (W3C)

Written by

Max Syed, Government Solutions

Talk with GovSoft