For 25 years, Section 508 has required federal agencies to make their information and communication technology accessible to people with disabilities.

June 21, 2026, marked the 25th anniversary of the original enforcement date of the Section 508 Standards. During that quarter century, digital accessibility has evolved from a specialized federal requirement into a broader procurement, compliance, usability, and business-risk issue.

The anniversary is worth recognizing—but it should not be mistaken for evidence that accessibility requirements have become settled, routine, or less important.

The opposite is happening.

Government services are increasingly delivered through websites, mobile applications, electronic documents, software platforms, online forms, digital kiosks, video, and cloud-based systems. At the same time, accessibility expectations are spreading across federal procurement, state and local government, healthcare, education, and the private marketplace.

For organizations that sell to government agencies—or hope to—the next phase of digital accessibility will be less about whether accessibility is required and more about whether vendors can prove that it was addressed.

Section 508 Is More Than a Website Requirement

Many businesses still associate Section 508 exclusively with federal websites.

That is far too narrow.

Section 508 applies to information and communication technology developed, procured, maintained, or used by federal agencies. Depending on the product or engagement, that can include:

• Websites and web applications
• Software and cloud platforms
• Mobile applications
• Electronic documents and forms
• Training materials
• Videos and multimedia
• Support documentation
• Hardware interfaces
• Internal employee systems
• Public-facing digital services

The current Section 508 Standards incorporate substantial portions of WCAG 2.0 Level A and AA by reference. That means federal accessibility reviews commonly examine familiar requirements involving keyboard access, form labels, color contrast, headings, alternative text, error identification, captions, focus order, and other accessibility fundamentals.

Organizations should not assume that passing an automated website scan is sufficient. Automated testing can identify certain code-level problems, but it cannot reliably determine whether every control works with a keyboard, whether instructions are understandable, whether focus moves logically, or whether a complex application is usable with assistive technology.

The ADA Title II Deadline Changed—The Direction Did Not

Another important development occurred on April 20, 2026.

The Department of Justice extended the compliance deadlines for its ADA Title II web and mobile application accessibility rule. State and local government entities serving populations of 50,000 or more now have until April 26, 2027. Smaller public entities and special district governments generally have until April 26, 2028.

The extension gives public entities additional time.

It does not eliminate the requirement.

The DOJ rule generally establishes WCAG 2.1 Level AA as the technical standard for covered state and local government web content and mobile applications. Public entities will therefore need to evaluate not only the content they create internally, but also digital products and services supplied by outside contractors.

That distinction matters to vendors.

A city, county, public university, transit authority, school district, library system, or other public entity may operate the service, but contractors often build the website, provide the software, produce the documents, manage the portal, or maintain the application.

As compliance planning accelerates, buyers are likely to ask vendors more detailed questions:

• Does the product conform to WCAG 2.1 Level AA?
• Has it been manually tested?
• Was assistive technology testing performed?
• Is there a current Accessibility Conformance Report?
• Who is responsible for correcting accessibility defects?
• Are accessibility obligations addressed in the contract?
• Does the vendor have a remediation process?
• Can the vendor provide accessible support documentation and training?

Businesses that prepare credible answers now will be better positioned than competitors who wait for accessibility language to appear in a solicitation.

WCAG 2.2 Is the Better Operational Target

The DOJ Title II rule points to WCAG 2.1 Level AA, and the current Section 508 Standards continue to reference WCAG 2.0.

That does not mean businesses should design only to those older baselines.

W3C encourages organizations to use the latest version of WCAG. WCAG 2.2 builds on earlier versions by adding requirements addressing issues such as focus visibility, dragging movements, target size, redundant entry, consistent help, and accessible authentication. Content that conforms to WCAG 2.2 is designed to remain backward compatible with WCAG 2.1 and WCAG 2.0, subject to W3C’s documented treatment of the obsolete Parsing criterion.

For most organizations, targeting WCAG 2.2 Level AA is the more defensible operational strategy.

It allows the organization to address newer interaction patterns while remaining aligned with the foundational requirements used in existing federal and ADA frameworks.

This does not mean every contract legally requires WCAG 2.2. It means WCAG 2.2 can provide a more future-conscious standard for design, development, testing, and remediation.

The Real Change Is Procurement Accountability

The most important accessibility trend may not be a new law or success criterion.

It is the growing expectation that organizations document what they have done.

A vendor may claim that its product is “ADA compliant” or “508 compliant.” But sophisticated buyers increasingly want evidence.

That evidence may include:

• A completed Voluntary Product Accessibility Template, or VPAT
• An Accessibility Conformance Report
• Manual test results
• Assistive technology test results
• A list of known accessibility limitations
• A remediation roadmap
• Accessibility language in development requirements
• Quality-assurance procedures
• An accessibility point of contact
• A process for responding to user-reported barriers

A VPAT should not be treated as a marketing brochure. It is a disclosure document. Unsupported claims, vague responses, and outdated test results may create more risk than an honest report that identifies limitations and explains how they will be corrected.

The goal is not to claim perfection.

The goal is to demonstrate control.

What Government Contractors Should Do Now

Organizations that sell digital products or services to federal, state, or local government should take several practical steps.

1. Identify the accessibility requirements in your contracts

Review solicitations, statements of work, technical requirements, procurement clauses, and deliverable specifications.

Do not assume that accessibility is irrelevant because the contract does not prominently mention WCAG. Accessibility requirements may be incorporated through agency policy, procurement language, Section 508 clauses, civil-rights obligations, or broader performance requirements.

2. Test the product beyond the homepage

A homepage scan does not establish product accessibility.

Test representative user journeys, including:

• Registration
• Login
• Search
• Navigation
• Form completion
• Error correction
• Checkout or payment
• Document download
• Account management
• Help and support

Complex workflows often contain the most serious barriers.

3. Combine automated and manual testing

Automated tools are useful for identifying repeatable issues, but they are only one part of an effective review.

Manual keyboard testing, screen-reader testing, visual inspection, code review, and workflow evaluation are needed to understand actual usability.

4. Review documents and multimedia

Accessibility obligations do not stop at the website.

PDFs, Word documents, spreadsheets, presentations, videos, training materials, and downloadable forms may also need to be accessible.

5. Document known limitations honestly

Do not hide known defects or make broad claims that cannot be supported.

Maintain a prioritized list of accessibility issues, assign responsibility, document corrective actions, and communicate material limitations to relevant buyers.

6. Build accessibility into future releases

Remediation after launch is usually slower and more expensive than integrating accessibility into design, development, content production, and quality assurance.

Accessibility criteria should be included in:

• Design requirements
• User stories
• Acceptance criteria
• Development standards
• Content templates
• Testing procedures
• Vendor agreements
• Release approvals

What Business Owners Should Understand

Even businesses that do not sell directly to the federal government should pay attention.

Accessibility standards influence procurement expectations, contractual obligations, platform requirements, litigation risk, customer experience, and brand reputation.

A business may become responsible for accessibility through a client relationship, a subcontract, a public-sector partnership, a software implementation, or a digital service used by a covered organization.

The strongest approach is not to wait until someone demands a compliance statement.

It is to understand the current condition of the digital product, identify the highest-risk barriers, and create a documented plan for improvement.

Twenty-Five Years Later, Accessibility Is Becoming More Measurable

Section 508’s 25th anniversary is not merely a historical milestone.

It marks a transition.

The first era of digital accessibility focused heavily on awareness: explaining why people with disabilities must be able to use digital information and services.

The next era is increasingly about operational evidence:

• What standard did you use?
• What did you test?
• Who performed the testing?
• What barriers were identified?
• What has been fixed?
• What remains unresolved?
• How will accessibility be maintained?

Organizations that can answer those questions clearly will be better prepared for government procurement, client reviews, regulatory deadlines, and future accessibility requirements.

Organizations that cannot may discover that accessibility is no longer just a technical issue.

It is a qualification issue.

Start With a Clear Picture of Your Risk

You do not need to remediate every digital property in a single day.

You do need to know where the greatest risks are.

The 508 Help Desk Accessibility Risk Snapshot provides a focused evaluation of your digital presence to identify material accessibility barriers, procurement concerns, and recommended next steps.

Before promising compliance, determine what your website or digital product can actually support.

Know the risk. Prioritize the work. Document your progress.