ADA Title II / Compliance Timeline

ADA Title II Compliance Deadline for Government Websites

Updated April 2026 — deadlines, requirements, penalties, and cost comparison

On April 24, 2024, the U.S. 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 applications conform to WCAG 2.1 Level AA. This is the first time the DOJ has set a specific technical standard and hard deadlines for government web accessibility.

This page covers the two compliance deadlines, what "compliance" means in practice, the consequences of non-compliance, and a comparison of the tools available to help your municipality meet the requirement.

The two deadlines

The population threshold is based on U.S. Census Bureau data. If your entity is uncertain about which tier it falls into, the Census Bureau's population estimates by county subdivision and incorporated place provide the definitive figures.

What ADA Title II requires

The final rule applies to all "web content" of public entities covered by Title II. This includes:

• The entity's primary website and all subdomains
• Web-based services (online bill pay, permit applications, meeting minutes)
• Documents posted on the website (PDFs, Word documents, spreadsheets)
• Mobile applications published by the entity
• Social media content, to the extent it is used to provide government services

The technical standard is WCAG 2.1 Level AA. This means every page must conform to all 50 success criteria at Level A and Level AA. There is no partial compliance option in the rule, though DOJ enforcement has historically considered good-faith remediation efforts.

Limited exceptions

The rule includes narrow exceptions for:

• Archived web content — Content that is no longer actively maintained, is kept for reference, and is clearly labeled as archived. Must still be available in an accessible format upon request.
• Preexisting conventional electronic documents — Documents created before the compliance date that are not currently used to access government services. If someone requests an accessible version, the entity must provide one.
• Content posted by third parties — User-generated content (e.g., public comments on a blog) where the entity does not control the content. The platform itself must still be accessible.
• Undue burden — An entity may claim fundamental alteration or undue burden for specific requirements, but must document the basis, have the head of the entity approve it, and provide an accessible alternative. This is an extremely high bar.

What "compliance" means in practice

Compliance is not a one-time event. Government websites are updated regularly with meeting minutes, agendas, news, and staff changes. Every update can introduce new accessibility issues. Practical compliance requires:

1. Baseline audit. Run an automated scan to identify all detectable WCAG 2.1 AA violations. This catches 30-40% of issues. Follow with a manual audit (keyboard testing, screen reader testing) for the remaining 60%.
2. Remediation plan. Prioritize violations by severity. Critical and serious issues (images without alt text, color contrast failures, form labels) should be fixed first.
3. Ongoing monitoring. Automated rescans on a weekly or monthly basis to catch regressions. Train staff who publish content on basic accessibility practices.
4. Accessibility statement. Publish a statement on your website describing your commitment, the standard you are targeting, and how users can report barriers.
5. Documentation. Keep records of audit results, remediation actions, and staff training. This documentation is critical in any enforcement proceeding.

Penalties for non-compliance

The ADA does not impose automatic fines. Enforcement occurs through the following channels:

DOJ complaints and investigations

Any member of the public can file a complaint with the DOJ Civil Rights Division. There is no standing requirement. The DOJ investigates and may enter into a settlement agreement or consent decree requiring remediation on a supervised timeline. Consent decrees often require annual reporting, third-party auditing, and can run for 3-5 years.

Private lawsuits

Individuals can file lawsuits under Title II seeking injunctive relief (a court order to fix the website). While Title II does not provide for monetary damages in most circuits, prevailing plaintiffs can recover attorney fees, which creates significant financial exposure. Some states have additional statutes that do allow damages.

Federal funding implications

Government entities that receive federal financial assistance are also subject to Section 504 of the Rehabilitation Act, which requires the same accessibility standards. Non-compliance can put federal grant funding at risk, though this is typically a separate enforcement track.

The practical risk level varies by community. Jurisdictions with active disability rights organizations, universities with disability law clinics, and areas where ADA plaintiff's firms are active tend to see complaints earlier. However, the broader trend is increasing enforcement. The DOJ has resolved more web accessibility cases in the last two years than in the previous decade.

Cost comparison: compliance monitoring tools

Government entities face a wide range of pricing for automated accessibility monitoring. Below is a comparison of options based on publicly available pricing and our market research:

For a municipality with a single primary website, A11yGov provides the automated scanning and monitoring layer at a fraction of the cost. This does not replace the need for manual testing by a qualified accessibility professional, but it covers the 30-40% of issues that are automatically detectable and provides the continuous monitoring that manual audits cannot.

Steps to get compliant

Whether your deadline has passed or is approaching, the process is the same. The key is to start, document your progress, and maintain ongoing monitoring.

See also: What Is WCAG 2.1 AA? | Government Website Accessibility Checklist