ADA Title II Deadline 2027: What Local Government Websites Must Do Now

In April 2024, the Department of Justice published its final rule under Title II of the Americans with Disabilities Act, setting enforceable WCAG 2.1 Level AA standards for state and local government websites and mobile applications. The rule ended years of ambiguity. For the first time, local governments have a specific technical standard, a compliance date, and clear DOJ enforcement authority behind it.

The deadlines are tiered by population. State and local governments serving populations of 50,000 or more had until April 24, 2026. Those serving populations under 50,000 have until April 26, 2028. Both deadlines are now either passed or imminent and enforcement complaints have already begun.

What ADA Title II Actually Requires

The DOJ rule requires that all public-facing web content and mobile apps published after June 24, 2024 meet WCAG 2.1 Level AA. Content published before that date must also be remediated by the compliance deadline. The rule covers the entire digital estate, not just the homepage or the top ten pages.

WCAG 2.1 AA is not a checkbox. It is a framework of 50 success criteria organised around four principles: Perceivable, Operable, Understandable, and Robust (POUR). For most government websites, the failure points cluster in predictable places: missing alt text on images, inaccessible PDF documents, poor colour contrast, missing form labels, keyboard navigation traps, and, critically, inaccessible search interfaces.

Why Search Is the Highest-Risk Component

Search is the single most-used feature on most government websites and the component most likely to fail an accessibility audit. Legacy search implementations are frequently built as inaccessible widgets: results announced inconsistently to screen readers, no keyboard navigation to filter options, autocomplete suggestions that disappear before a screen reader can read them, and results pages that rely on colour to indicate relevance.

The DOJ's rule makes clear that the search interface itself, not just the content it finds, must be accessible. An accessible search widget requires ARIA live regions to announce result counts, keyboard-operable filter controls, logical focus management when results load, and sufficient colour contrast across all interactive states.

A resident using a screen reader who cannot operate your search box cannot access your services. That is not a technical edge case, it is a Title II violation.

DOJ technical guidance, April 2024

The PDF Problem Is Bigger Than You Think

Most government websites are sitting on thousands of PDFs published over the past two decades. Many are scanned images with no machine-readable text. Others are generated from untagged InDesign or Word files that produce PDFs with no reading order, no alt text, and no heading structure. Every one of these is a potential Title II violation.

The DOJ rule applies to PDFs if they are web content, which virtually all government PDFs are. Remediation options include tagging PDFs for accessibility, replacing them with accessible HTML pages, or providing an accessible alternative format. For agencies with thousands of documents, a content audit is the essential first step.

A Practical Compliance Roadmap

1. 1Inventory your digital estate, list every domain, subdomain, and third-party embedded tool. Many agencies discover they have far more web properties than they realised.
2. 2Run an automated scan, tools like axe, WAVE, or Keyspider's audit tool catch roughly 30-40% of WCAG failures automatically. This is the baseline, not the finish line.
3. 3Commission a manual audit, automated tools cannot assess keyboard navigation flows, screen reader announcements, or cognitive load. A manual audit by an accessibility specialist is required for meaningful compliance.
4. 4Prioritise by user impact, fix the highest-traffic pages and the most-used components first. Your search interface, contact forms, and service application pages affect the most users.
5. 5Remediate your search widget, if your current search is not keyboard-operable and screen-reader-friendly, replace or upgrade it. This is a compliance requirement, not a preference.
6. 6Address PDFs in order of traffic, start with the most-downloaded documents. A complete PDF remediation programme typically takes six to eighteen months.
7. 7Establish ongoing monitoring, WCAG compliance is not a one-time project. Every content update is a potential regression. Embed accessibility testing into your content publishing workflow.
8. 8Document your conformance, maintain an accessibility statement listing your known conformance level, any exceptions, and your contact process for users who encounter barriers.

How AI Search Supports ADA Compliance

A properly built AI search interface is more accessible than most legacy search implementations, because it is built to modern standards from the ground up. Keyspider's search widget meets WCAG 2.1 AA out of the box: keyboard-operable, with ARIA live regions announcing result counts, logical focus management on result load, and sufficient contrast across all interactive states.

Beyond the interface, AI search helps residents with disabilities in a more fundamental way: it understands natural language queries. A resident who uses voice input, an augmentative communication device, or assistive typing software often cannot construct precise keyword queries. AI search handles natural language, 'how do I appeal a parking ticket' and returns a direct answer, reducing the burden on users who find navigation and keyword formulation difficult.

Exceptions Under the Rule

The DOJ rule includes limited exceptions. Archived web content that is not currently used and is not modified after the compliance date is exempt. Content on password-protected intranets is exempt. Third-party content posted by third parties without the agency's modification is exempt, though this exception is narrow and does not cover content embedded in the agency's own pages.

Agencies may also claim an 'undue burden' exception for specific compliance requirements, but the bar is high. Undue burden must be documented, must consider the agency's total resources, and must offer an accessible alternative. Blanket undue burden claims covering entire websites are unlikely to withstand DOJ scrutiny.

The Cost of Non-Compliance

Title II complaints are filed with the DOJ or relevant federal funding agencies. The DOJ may investigate, require a corrective action plan, or, for egregious or repeated violations, seek civil monetary penalties of up to $75,000 for a first violation and $150,000 for subsequent violations. Beyond penalties, agencies that receive federal funding risk losing that funding for non-compliance.

Private right of action under Title II means individuals can also sue directly. Several high-profile settlements against local governments have included website remediation requirements, monitoring periods, and damages. The legal risk is real and growing.