Latest News – Industry Standards and Software Updates

Automating ADA Compliance: More Than Manual

Document Outline

In April 2024, the Department of Justice (DOJ) published a final rule requiring state and local governments to meet Web Content Accessibility Guidelines (WCAG) 2.1 Level AA for websites and mobile apps. The original compliance deadlines have since been extended, but the pressure on local governments to make their digital services accessible has not eased. Manual fixes, tagging documents, auditing pages, remediating code one at a time, are simply not sustainable given the volume of content most municipalities manage. Automating ADA compliance offers a practical path forward, but it must be paired with human oversight to truly serve all residents.

The DOJ’s Updated Deadlines for WCAG Compliance

The DOJ rule initially set a compliance deadline of April 24, 2026, for entities with a population of 50,000 or more. Smaller jurisdictions and special district governments had until April 26, 2027. However, an Interim Final Rule published on April 20, 2026, extended those dates. Entities with a population of 50,000 or more now have until April 26, 2027, to comply. Entities with fewer than 50,000 residents, as well as special district governments, must meet the requirements by April 26, 2028.

These deadlines apply to a wide range of government content, including PDFs, forms, meeting minutes, public notices, and online applications. The scope of work required to bring everything into compliance is massive, and many local governments are only beginning to assess the gap.

Entity Type

Original Deadline

Extended Deadline

Population 50,000 or more

April 24, 2026

April 26, 2027

Population less than 50,000

April 26, 2027

April 26, 2028

Special district governments

April 26, 2027

April 26, 2028

The Real Cost of Manual Accessibility Fixes

Manually remediating digital content is labor-intensive and expensive. According to estimates cited in a Route Fifty article, manual tagging of a single document takes 2 to 3 hours. For a large state that may need to tag over 75,000 documents, that translates to roughly 150,000 hours of work and a cost exceeding $2 million. Even a smaller city or county with about 500,000 residents might face around 12,000 documents requiring tagging, at a cost of approximately $400,000 in manual labor alone.

These figures do not include the ongoing work of maintaining compliance as new documents are posted, forms are updated, and third-party widgets are added. Most local governments operate with lean IT teams and limited budgets, making manual remediation at this scale unrealistic. The need for a more efficient approach is clear.

How Automating ADA Compliance Changes the Equation

Automation can dramatically reduce the time and expense of achieving basic compliance. As noted in the same Route Fifty article, automating the accessibility process can achieve approximately 80% WCAG compliance on the first pass. This means the bulk of issues, such as missing alt text, improper heading structures, color contrast errors, and document tagging, can be caught and fixed automatically without tying up staff for months.

Automated tools scan websites and documents against WCAG success criteria, flagging violations and often applying remediation. For example, PDFs can be auto-tagged with proper reading order and semantic structure, forms can be checked for keyboard accessibility, and contrast ratios can be adjusted. This first-pass cleanup allows staff to focus their limited time on the remaining 20% of issues that require human judgment, such as testing with assistive technologies or reviewing complex interactive elements.

Automation Reduces Document Remediation Costs

By handling the most common document accessibility issues automatically, local governments can cut the cost of compliance significantly. Instead of spending 2–3 hours on each PDF, automated tagging can reduce that to minutes per document. For a city with 12,000 documents, the savings can reach hundreds of thousands of dollars, funds that can be redirected to other critical services or more nuanced accessibility work.

The Limits of Full Automation: Manual Testing Is Still Required

Relying solely on automated tools is not enough. Both the MRSC and the Route Fifty article stress that automated tools cannot detect all compliance issues. For instance, automated tools may miss whether a video has accurate captions, whether a custom dropdown menu works logically for screen reader users, or whether the text alternatives provided for images are truly equivalent in context. Some accessibility problems, like those involving user experience and cognitive accessibility, require human evaluation.

Best practice combines automated scanning with manual testing by people who use assistive technologies or who are trained in accessibility audits. This hybrid model ensures that the automated 80% coverage is verified and that the remaining issues are caught. Local governments should plan for periodic manual audits, especially after major content updates or website redesigns.

Risks of Non-Compliance: Lawsuits, DOJ Investigations, and Penalties

The consequences of failing to meet WCAG requirements are serious. Non-compliance can lead to private lawsuits, DOJ investigations, and penalties that, in some cases, reach up to $150,000 per violation. These costs far exceed the investment needed to build an accessible digital presence from the start. Additionally, litigation often requires cities to commit to expensive remediation plans under court supervision.

Beyond legal risk, inaccessible government services create a real barrier for citizens with disabilities. Local governments have a legal and ethical responsibility to ensure equal access to public information, online forms, and communication channels. Automating core compliance tasks helps reduce the backlog of inaccessible content and demonstrates a good-faith effort to meet the DOJ’s updated standards.

The Current State of Accessibility Funding and Staffing

Despite the growing urgency, many governments are underprepared. According to a 2025 survey from the National Association of State Chief Information Officers (NASCIO), two-thirds of states have hired a technology accessibility coordinator. However, only 46% of states reported having dedicated funding for accessibility improvements, and just one state said it had fully implemented its accessibility plan. This gap between intention and action underscores the need for efficient, scalable solutions that do not overwhelm already stretched IT budgets.

Automating ADA compliance can help bridge that gap by reducing reliance on large, specialized teams. When combined with a platform that bakes in compliance from the start, such as a website CMS designed for WCAG 2.2 and ADA Title II compliance, local governments can meet deadlines without a proportional increase in staff or spending.

Frequently Asked Questions

What is the difference between WCAG 2.1 and WCAG 2.2?

WCAG 2.2 adds new success criteria for mobile accessibility, target size, and focus appearance, among others. The DOJ’s 2024 rule requires WCAG 2.1 Level AA, but many vendors and governments are already working toward WCAG 2.2 to stay ahead. Local governments should adopt the most current version their platform supports to avoid future remediation cycles.

Can automation alone make my city’s website fully compliant?

No. Automated tools can achieve about 80% compliance on a first pass, but they cannot detect all issues. Manual testing by trained users, including people with disabilities, is necessary to catch context-sensitive problems like meaningful alt text, logical reading order, and screen reader navigation. A combined approach is the only reliable method.

What types of content need to be made accessible?

The DOJ rule covers all websites and mobile apps operated by state and local governments. This includes PDF documents, online forms, meeting agendas, public notices, video and audio content, maps, and any interactive tools. Even third-party content and widgets embedded on a government website must meet WCAG standards if the government offers them to the public.

What happens if we miss the compliance deadline?

Non-compliance can lead to private lawsuits, DOJ investigations, and civil penalties up to $150,000 per violation in certain cases. Courts may also require the government to adopt a compliance plan under monitoring. The extended deadlines (April 2027 for large entities, April 2028 for smaller ones) provide extra time, but proactive steps should begin immediately to avoid last-minute scrambling.

Automating ADA compliance for local government is no longer optional, it is a strategic necessity. Manual fixes alone are too slow and too costly to address the volume of digital content that municipalities manage. By combining automated tools with targeted manual testing, local governments can meet the DOJ’s updated deadlines, reduce legal risk, and deliver equitable access to all residents. The key is to start now, evaluate available platforms that include built-in compliance features, and build a sustainable process that extends well beyond the first remediation pass.

Ready When You Are

Let's get started.

Schedule a personalized demo and see how City of Anywhere can help your city and community thrive.

Launch in 30 days or less – from signed agreement to live, resident-ready site.