April 2026 ADA Title II Deadline: What State and Local Governments Need to Know

The Clock Is Ticking

On April 24, 2024, the Department of Justice published a final rule under Title II of the Americans with Disabilities Act establishing specific technical standards for web and mobile accessibility for state and local government entities. The rule gives these entities until April 24, 2026, to bring their digital properties into compliance with WCAG 2.1 Level AA.

This is not a suggestion or a best practice recommendation. It is a legally binding federal regulation with enforcement mechanisms and consequences for non-compliance.

Who Must Comply

The rule applies to all state and local government entities covered by ADA Title II. This includes state agencies, county governments, city and municipal offices, public school districts and state universities, public libraries, public transit authorities, courts and judicial systems, public hospitals and health departments, and any other entity that functions as a state or local government.

If your organization receives public funding or operates as a governmental body, this rule almost certainly applies to you.

What the Rule Requires

The rule adopts WCAG 2.1 Level AA as the technical standard that state and local governments must meet. This standard encompasses four principles of accessibility. Content must be perceivable, meaning users must be able to perceive all information and interface components. Content must be operable, meaning all functionality must be usable via keyboard and other input methods. Content must be understandable, meaning information and operation of the interface must be understandable to users. And content must be robust, meaning it must be compatible with current and future assistive technologies.

In practical terms, this means all images need descriptive alt text, all videos need captions and audio descriptions, all forms need proper labels and error handling, all interactive elements need keyboard accessibility, color contrast must meet minimum ratios, and documents published online must be accessible.

What Is Covered

The rule covers all web content that a state or local government entity makes available to the public through its websites and web applications. This includes main government websites, online portals for services like permits, payments, and registrations, mobile applications, PDF documents and other digital files linked from websites, social media content that serves as an official communication channel, and third-party content embedded on government sites.

The rule includes limited exceptions for archived web content, content posted by third parties on government platforms where the government does not control the content, and preexisting conventional electronic documents under certain conditions. However, these exceptions are narrow and should not be relied upon as a broad shield against compliance.

Steps to Take Now

Government entities that have not yet begun their compliance efforts need to move quickly. The recommended approach starts with conducting a comprehensive audit of all public-facing web content against WCAG 2.1 AA criteria. This audit should cover not just the main website but all subdomains, applications, and linked documents.

Following the audit, entities should develop a prioritized remediation plan that addresses the most critical barriers first. High-priority items include anything that blocks access to essential services such as emergency information, benefit applications, public meeting participation, and complaint or feedback mechanisms.

Concurrent with remediation, entities should implement accessibility into their content creation and procurement processes. Every new piece of content published, every new vendor tool adopted, and every website update should be evaluated for accessibility before deployment.

Staff training is another essential component. Content authors, web developers, communications staff, and IT personnel all need to understand their role in maintaining accessibility compliance.

Consequences of Non-Compliance

State and local governments that fail to meet the April 2026 deadline face several potential consequences. The DOJ can investigate complaints and initiate enforcement actions. Private individuals can file lawsuits seeking injunctive relief. Federal funding may be at risk for entities found to be in violation. Additionally, the reputational damage of being publicly identified as non-compliant can be significant.

Practical Budget Guidance

Compliance costs vary widely based on the size and complexity of a government entity's digital presence. Small municipalities with a single website might spend between $15,000 and $50,000 for an initial audit and remediation. Larger entities with multiple sites, applications, and extensive document libraries could face costs ranging from $100,000 to $500,000 or more.

Ongoing compliance will also require budget allocation for regular monitoring, staff training, and remediation of new content. Most entities should budget for at least annual accessibility audits and continuous automated monitoring tools.

Resources and Next Steps

The DOJ has published guidance documents explaining the rule and its requirements. The Web Accessibility Initiative from W3C provides extensive technical resources on meeting WCAG 2.1 criteria. And organizations like the National Association of State Chief Information Officers have developed frameworks specifically for government digital accessibility programs.

The April 2026 deadline is close. Now is the time to act.