Latest News – Industry Standards and Software Updates

Automating ADA Compliance for Local Government: What It Can and Can’t Do

Reading time: 5 min

Document Outline

Manually tagging a single document for accessibility takes two to three hours. Automating ADA compliance shouldn’t. A state facing 75,000 documents is looking at roughly 150,000 hours and a cost above $2 million. A county of about 500,000 residents with 12,000 documents faces something near $400,000 in labor alone, figures reported by Route Fifty in its coverage of state and local accessibility efforts.

No municipal IT department has that capacity. Automation is the only way most cities reach their deadline. But automation has a ceiling, and vendors are not always candid about where it sits.

Entity Type

Original Deadline

Current Deadline

Population 50,000 or more April 24, 2026 April 26, 2027
Population less than 50,000 April 24, 2027 April 26, 2028
Special district governments April 24, 2027 April 26, 2028

The DOJ’s April 2024 final rule set WCAG 2.1 Level AA as the standard. An Interim Final Rule in April 2026 extended the compliance dates by one year and changed nothing else. The scope still covers PDFs, forms, meeting minutes, public notices, video, and online applications.

What automating ADA compliance actually covers

Automating ADA compliance remediation reaches roughly 80% WCAG conformance on a first pass, per the same Route Fifty reporting. That 80% is concentrated in the mechanical, high-volume failures: missing alt attributes, broken heading hierarchies, contrast violations, untagged PDF structure and reading order, and unlabeled form fields.

On documents specifically, the shift is from two to three hours per file to minutes. Across 12,000 documents that is the difference between a multi-year project and a quarter. It also changes what your staff spend time on: from mechanical tagging to the judgment work that actually requires a person.

Where automation stops

The remaining 20% is not a rounding error, and it contains most of what genuinely blocks residents. Both MRSC and the Route Fifty reporting emphasise that automated tools cannot detect every conformance issue.

Specifically, automation cannot tell you whether:

  • Alt text is contextually meaningful, or merely present
  • Video captions are accurate, or auto-generated nonsense
  • A custom dropdown or modal announces itself coherently to a screen reader
  • Reading order matches visual order in a complex layout
  • A multi-step permit application can actually be completed end to end without a mouse
  • Language and structure are clear enough for cognitive accessibility

A city that automates and stops has a site that scores well and still fails residents. Plan for periodic manual audits at minimum after major content changes or redesigns — and involve people who use assistive technology.

What non-compliance actually exposes a city to

This is widely misreported, including by accessibility vendors, so it is worth stating precisely.

The civil penalty schedule often quoted in this context; $75,000 for a first violation and $150,000 for subsequent violations, adjusted upward for inflation, belongs to Title III of the ADA, which the DOJ enforces against private places of public accommodation. It does not apply to state and local governments.

As a Title II entity, your city’s exposure is different in kind:

  • Private lawsuits brought by residents, and DOJ investigations
  • Mandatory injunctive relief — court-ordered remediation on a court’s timetable rather than your own
  • Compensatory damages and attorneys’ fees, which frequently exceed the cost of the underlying remediation
  • Ongoing federal oversight through settlement agreements, sometimes lasting years
  • Federal funding risk where accessible services are a condition

A concrete example is more useful than a penalty ceiling. In Price v. Manatee County, Florida, the county paid the plaintiff $16,000 and agreed to bring its websites into compliance within fourteen months or face $1,500 per day until it did. One municipality in the county, Bradenton, took its entire website offline for several months rather than risk further litigation, which is its own kind of service failure.

The point is not the size of any single number. It is that remediation on a court’s schedule costs more, and offers less control, than remediation on yours.

Most governments are not staffed for this

NASCIO’s 2025 survey found that two-thirds of states have hired a technology accessibility coordinator, but only 46% reported dedicated funding for accessibility improvements and just one state said it had fully implemented its accessibility plan.

That gap between designating an owner and funding the work is the practical case for automation. It is not that automated remediation is better than skilled human remediation. It is that the human remediation most cities would need has no funded headcount attached to it, and the deadline does not move for that reason.

Frequently asked questions

What is the difference between WCAG 2.1 and WCAG 2.2?

WCAG 2.2 adds success criteria covering target size, focus appearance, dragging movements, and consistent help, among others. The DOJ’s 2024 Title II rule requires WCAG 2.1 Level AA, that is the conformance standard. Building to 2.2 exceeds it and reduces future remediation cycles, but a vendor claiming the DOJ requires 2.2 has misread the rule.

Can automation alone make our website compliant?

No. Automating ADA compliance remediation reaches roughly 80% on a first pass. The remainder requires human judgment: meaningful alt text, caption accuracy, screen reader navigation of custom components, and completability of multi-step service paths. A combined approach is the only reliable route.

Which content is covered?

All web content and mobile apps a state or local government offers to the public: informational pages, PDFs, forms, agendas, notices, video, audio, and maps. Third-party content and embedded widgets are covered where the government offers them under a contractual or licensing arrangement.

What happens if we miss the deadline?

Title II entities face private lawsuits, DOJ investigation, court-ordered remediation, compensatory damages, attorneys’ fees, and potential federal funding consequences. The Title III civil penalty schedule does not apply to municipalities. Note also that Title II’s underlying nondiscrimination duty is already in force and claims can be brought before the 2027 and 2028 dates arrive.

General information, not legal advice. Confirm your city’s obligations with counsel.

Picture of Eric Oliver

Eric Oliver

Eric Oliver is the founder and CEO of City of Anywhere, the all-in-one digital platform that helps state and local governments launch fast, ADA-compliant websites and consolidated resident services in weeks, not monthss. He founded the company after 20 in government technology and public-sector web design, where he saw cities struggling with aging websites, fragmented vendor stacks, and looming accessibility mandates. Under Eric Oliver's leadership, City of Anywhere has helped municipalities modernize their digital presence and meet WCAG and ADA Title II requirements ahead of the DOJ's compliance deadlines. Eric Oliver speaks and writes regularly on government website accessibility, civic technology, and resident-first digital services.

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 weeks, not months – from signed agreement to live, resident-ready site.