ADA Title II: What State and Local Governments Need to Know Before the Deadline

In April 2024, the Department of Justice published a final rule under Title II of the Americans with Disabilities Act requiring state and local government entities to make their web content and mobile apps accessible. It's the most significant federal accessibility mandate in years — and a lot of the organizations it covers still don't fully understand what it requires.

This is my plain-language breakdown. No legalese, no hedging, no vague "consult an attorney" deflection. Here's what it says, who it covers, and what you need to do.

Who This Covers

ADA Title II applies to state and local government entities. That includes:

• State agencies and departments
• Cities, counties, and municipalities
• Public school districts and universities
• Public transit agencies
• Courts and judicial bodies
• Public libraries
• Any entity that receives federal financial assistance and is a "public entity" under Title II

If you work for any of these organizations, this rule applies to your web presence. All of it — not just your main website, but every web-based service, form, application portal, document, and mobile app you operate.

The Technical Standard: WCAG 2.1 Level AA

The DOJ rule specifies WCAG 2.1 Level AA as the required technical standard — not 2.2. In practice, WCAG 2.2 is backward-compatible with 2.1 (meeting 2.2 AA means you meet 2.1 AA), so building to the current standard is always the right move. But the legal bar is 2.1 AA.

WCAG 2.1 AA covers the four POUR principles: Perceivable, Operable, Understandable, and Robust. At the AA level, that means things like:

• All images have meaningful text alternatives
• Videos have captions and audio description
• The entire interface is keyboard-navigable without a mouse
• Focus indicators are visible
• Color is never the only means of conveying information
• Text contrast meets a 4.5:1 ratio (3:1 for large text)
• Forms have proper labels and error messages
• Pages work with screen readers and other assistive technology

The Compliance Deadlines

The rule uses a tiered deadline structure based on entity size:

• Large entities (50,000+ population for local governments; state agencies and special districts): April 24, 2026
• Smaller entities (under 50,000 population, special districts): April 26, 2027

If you're a large entity, that first deadline is now. If you haven't started, you're already out of compliance.

What "Web Content" Means in Scope

The rule is intentionally broad. Web content means:

• All pages on your public-facing website
• All pages on intranets used by employees (yes, internal tools count)
• Web-based applications and portals (permit applications, payment systems, registration forms)
• PDFs and other document files published on the web
• Pre-recorded and live video content
• Mobile applications
• Third-party content you integrate into your site, if you have procurement control over it

That last point is important. If your city website embeds a third-party payment portal for utility bills, and that portal is inaccessible, you have a compliance problem — even if you didn't build it. Your procurement contracts need accessibility requirements.

Exceptions and Carve-Outs

The rule does have exceptions, but they're narrower than most organizations hope:

• Archived web content — web content that was created before the compliance date, is not currently used, and is kept solely for reference. This does NOT cover content you continue to rely on or link to.
• Preexisting conventional electronic documents — Word, PDF, and similar files published before the compliance date, if they are not used to apply for, access, or participate in a covered entity's services. If the document is part of a service (a form, a permit application), it's in scope.
• Content posted by a third party — social media posts by the public on your site, for example. Content you post or commission is still in scope.
• Fundamental alteration or undue burden — if compliance would fundamentally alter the nature of the service or impose an undue financial burden, a limited exception applies. This bar is high and requires documentation. Do not assume this applies without legal review.

What Enforcement Looks Like

The DOJ can initiate compliance reviews. Individuals can also file complaints with the DOJ or directly sue under Title II without a filing requirement. Courts have awarded injunctive relief and attorney's fees in Title II accessibility cases.

The more common enforcement pathway in practice is: a constituent files a complaint, the DOJ investigates, the entity enters into a consent decree requiring remediation on a defined timeline. Consent decrees are public record and typically require third-party auditing and ongoing reporting.

Enforcement is real. The National Federation of the Blind, Disability Rights Advocates, and similar organizations actively file complaints and litigation. Public entities that have been in the news for inaccessible services — online services for people with disabilities, public transit apps, court filing systems — have faced significant legal exposure.

Practical First Steps Right Now

If you're reading this and haven't started, here's the most useful sequence:

1. Run an automated baseline scan. Use axe-core or Lighthouse across your top 20–30 pages. This gives you a quick picture of obvious structural violations and a starting point for prioritization.
2. Identify your highest-traffic, highest-stakes pages. Your homepage, your primary service portals, any page where someone applies for something or pays for something. These are your priority 1.
3. Get a manual audit on those priority pages. Automated tools miss 60–70% of real barriers. A manual audit with actual screen reader testing is the only way to know what your users actually experience.
4. Audit your PDF library. Most government entities have thousands of PDFs. Tagged PDFs with proper reading order, alt text for images, and accessible tables are required. Untagged PDFs are completely inaccessible to screen reader users.
5. Review your vendor contracts. Add accessibility requirements to any new procurement. For existing vendors, initiate conversations about their WCAG conformance.
6. Document your work. If you're subject to a complaint investigation, documentation of your remediation efforts matters. Keep records of audits, remediation work, and timelines.

"The earlier you start, the more options you have. An organization that starts remediating 18 months before a deadline can do it methodically. One that starts 30 days out is in triage mode."

Why Manual Testing Still Matters for Compliance

Passing an automated scan does not mean you're compliant with WCAG 2.1 AA. I cannot say this clearly enough. I have personally tested sites with zero axe-core violations that were completely unusable with JAWS — because the reading order was wrong, because focus management was broken, because dynamic content was silent to screen readers.

For organizations that are legally required to meet WCAG 2.1 AA, "we ran Lighthouse" is not a defense. You need a human tester with assistive technology, working through your key user flows, confirming they actually work.

That's exactly what we do at QA11Y Labs.