ADA Compliance for State and Local Government

The Department of Justice published its long-awaited final rule on web and mobile accessibility for state and local government on April 24, 2024, bringing decades of uncertainty to a close. The rule, codified at 28 CFR Part 35, makes WCAG 2.1 Level AA the binding technical standard for any web content or mobile app provided by a public entity, with compliance dates staggered by population served. Public entities serving 50,000 or more people had to comply by April 24, 2026 — that deadline is now in the past. Public entities serving fewer than 50,000 people, and special district governments, have until April 26, 2027. The rule covers every website, every mobile app, every third-party platform a government uses to deliver services to the public, and the universe of municipal, county, and state functions that ride on those platforms — permits, payments, emergency alerts, public records, GIS, court calendars, transit schedules, school district communications. DOJ enforcement is direct and assertive, and a steady stream of settlement agreements with cities and counties since 2017 has set the working template.

This page is informational and is not legal advice. ADA, federal regulations, and state-law obligations vary by jurisdiction and business type — consult qualified counsel for case-specific guidance.

What the Title II final rule actually requires

The rule's core obligation is that all web content and mobile applications provided, made available, or used by a public entity must conform to the Web Content Accessibility Guidelines version 2.1, Level AA. "Provided, made available, or used by" is broader than it sounds: it captures content the entity creates directly, content hosted on third-party platforms (a city's YouTube channel, a county's Eventbrite page, a school district's Facebook posts), and content that contractors create on behalf of the entity (a permit- management vendor's portal, a tax-payment processor, a transit-tracking app).

The rule includes seven exceptions. The most-discussed are (1) archived web content created before the rule's effective date and not actively used; (2) preexisting conventional electronic documents (PDFs, Word) created before the compliance date, except those used for applying for or receiving a benefit; (3) content posted by third parties not subject to the entity's control; (4) individualized password-protected content (a specific student's grade, a specific resident's permit file) that does not also serve as a benefit application; (5) preexisting social media posts; (6) content related to archived materials; and (7) certain emergency situational content. None of these exceptions is broad enough to swallow the rule, and DOJ has been clear in commentary that entities should not interpret the exceptions expansively.

Critically, the rule explicitly captures third-party content if the entity uses it to provide services. A city cannot escape the rule by routing residents through a non-conformant SaaS permit-management platform; the obligation runs to the entity that holds out the service to the public.

Online services: permits, payments, public records

Most municipal and county digital services run on a small handful of vendor platforms. The accessibility profile of any given city is largely determined by which platforms it licenses and how those platforms have been configured.

Permit management typically runs on Accela, Tyler EnerGov, OpenGov, ViewPoint Cloud, or CivicGov. Of these, OpenGov and ViewPoint generally pass WCAG 2.1 AA in default configuration; Accela and Tyler EnerGov pass for the unauthenticated browse pages but have documented gaps in the form-driven application flow, particularly in conditional-logic forms where the visible field set changes based on previous answers.

Online tax and utility payment runs on Tyler MUNIS, Invoice Cloud, Paymentus, Paymentech, or ACI Speedpay. Payment-flow accessibility has improved substantially in 2024-2025 across all major vendors, but the typical failure mode is a custom "branded" wrapper the city has applied that breaks the underlying vendor's accessibility (overriding focus styles, adding autoplay video backgrounds, embedding map widgets without alt text).

Public records portals running on GovQA (Granicus), JustFOIA, NextRequest (CivicPlus), or custom forms generally pass automated scans on the request- submission interface but consistently fail on the response-document delivery: responsive records are delivered as untagged PDFs, often image-only scans, with no accessible alternative format process documented.

City and county council meeting portalsrunning on Granicus, Swagit, CivicClerk, or Legistar embed video and document content. Live-streamed meetings need captions in real time; recorded meetings need accurate captions on demand; agenda packets and meeting minutes need to be in accessible formats (HTML or tagged PDF, not scanned PDF). Many cities still post scanned PDFs of handwritten or marked-up minutes — a clear violation under the rule for any document used to apply for or receive a benefit (which includes most public meeting records).

GIS, mapping, and visualization tools

Government websites lean heavily on interactive maps for zoning, parcels, transit routes, voting precincts, school attendance zones, capital improvement projects, and emergency response. The major platforms — Esri ArcGIS Online, ArcGIS Hub, Google Maps with custom overlays, Mapbox-based custom solutions, CARTO — each have known accessibility limitations because the core interaction (drag and zoom on a visual canvas) is fundamentally visual.

The Title II rule does not require that interactive maps be made operable by screen reader. It does require that equivalent information be available in an accessible non-map alternative — typically a searchable list, a structured data table, or a text-based tool that produces the same answer the map produces visually. A zoning map is compliant if a resident can also enter their address into an accessible form and get a text response of their zoning designation. A precinct map is compliant if a voter can enter their address and get a text response of their polling location. A transit map is compliant if a rider can search for a stop and get a text response of the routes that serve it.

Esri's ArcGIS Hub has made the most explicit investment in accessible alternatives, providing built- in list-and-table views for most map widgets. Custom Mapbox solutions almost always need to be paired with a separately-built accessible alternative, and the build- it-yourself reality is one of the more common gaps in municipal accessibility audits.

Emergency alerts and public-safety communications

Emergency alerts are the highest-stakes accessibility surface in government. The federal Wireless Emergency Alerts system has its own technical specifications, but the city- or county-level emergency notification systems (Everbridge, AlertMedia, Genasys, Smart911) deliver alerts via SMS, voice call, email, push, and web. Each channel has its own accessibility profile, and gaps can be life-safety issues for residents with disabilities.

The Title II rule applies to web content used to deliver emergency information. Practical compliance includes captioning on emergency-related video content (press conferences, evacuation instructions); alt text on evacuation-route maps; HTML alternatives to PDF evacuation orders; and clear text descriptions on social- media-posted alerts. The rule's narrow exception for certain time-sensitive emergency content does not generally cover the predictable, planned emergency preparedness content that most municipalities maintain year-round.

DOJ enforcement: what settlements look like

DOJ enforces Title II directly through Project Civic Access investigations and through complaint-driven actions. Recent settlement agreements that specifically include web-accessibility obligations include theCity of Houston, theCity of Cincinnati, theCity of Chesterfield (Missouri), theTown of Denton (Maryland), and several counties in Texas, Florida, and California. These agreements generally require WCAG 2.1 AA conformance on a phased timeline, an accessibility coordinator with specific authority, public posting of an accessibility statement and feedback mechanism, training for content authors, and periodic audits with reporting to DOJ.

Cash penalties in DOJ Title II settlements are typically modest (compensation to specific complainants and a civil penalty), but the corrective-action obligations and the multi-year monitoring substantially exceed the cash component in actual cost. The City of Houston agreement, for instance, ran years and covered the entire municipal web ecosystem.

Outside DOJ, private litigation under Title II is available but uncommon (relative to Title III); the primary private-action vector is Section 504 OCR complaints to the Department of Education for school districts and to other federal agencies for entities receiving their funding.

Cost and timeline reality for government

Government remediation cost depends heavily on whether the entity has a centralized web team or distributed content authoring across departments. Centralized teams can drive consistent results faster; distributed environments need governance work alongside technical remediation.

What to do today

If your entity serves 50,000 or more residents, the April 2026 deadline has already passed. The most valuable thing you can do this week is document your current state and remediation roadmap. DOJ investigators do not expect perfection on the first visit, but they do expect a public accessibility statement, a designated coordinator, an accessible- format-request process, and an active remediation plan. Most of the entities that get hit hardest in DOJ actions are the ones that have none of those documents.

If you serve fewer than 50,000 residents, you have until April 2027. Run an automated WCAG 2.1 AA scan on your three most-trafficked pages — typically the homepage, the online-payment landing page, and the most recent council or board meeting page. Those three URLs will tell you whether you have detectable violations a complainant could screenshot in five minutes. From there, prioritize the services-delivery flows (payments, permits, public records requests, voter and election information) ahead of static informational pages, because that is where an inaccessibility translates most clearly into a denied benefit.