ADA Title II Compliance Deadline April 24, 2026: Step-by-Step Checklist for US State & Local Governments

The clock has run out. On April 24, 2026, the US Department of Justice's updated ADA Title II rule takes effect for state and local government entities serving populations of 50,000 or more. Every public-facing website, mobile application, and digital service operated by these entities must conform to WCAG 2.1 Level AA — or face federal enforcement action, private lawsuits, and loss of federal funding.

This step-by-step checklist is designed to help cities, counties, school districts, transit authorities, and public agencies navigate exactly what is required and how to achieve compliance quickly.

What the Title II Rule Requires

The DOJ's final rule, published April 24, 2024, codifies web and mobile app accessibility under Title II of the Americans with Disabilities Act for the first time. The technical standard is WCAG 2.1 Level AA. Key requirements include:

• All public-facing web content must conform to WCAG 2.1 Level AA
• Mobile applications that provide access to government services or information are in scope
• Password-protected portals (tax payment, utility billing, permit applications) are covered
• Embedded third-party content (maps, payment processors, scheduling tools) must also conform
• Archived content posted before the rule is exempt unless it is the only source of that information
• A limited “fundamental alteration” or “undue burden” defence exists, but entities must still provide access via an alternative means

Who Must Comply by April 24, 2026?

The rule uses a phased timeline based on population:

• April 24, 2026— Entities with a total population of 50,000 or more (includes cities, counties, school districts, special-purpose districts, and any entity whose jurisdiction covers 50,000+ people).
• April 24, 2027— Entities with a total population under 50,000.

If you are unsure whether your entity qualifies under the first phase, the DOJ has indicated that the most recent US Census data should be used. When in doubt, err on the side of the earlier deadline.

Step-by-Step Compliance Checklist

Follow this process to move from assessment to full ADA Title II digital accessibility compliance:

1. Inventory all digital properties— List every public-facing website, subdomain, web application, and mobile app your entity operates. Include third-party portals used to deliver services (online permitting, utility billing, court records).
2. Conduct a preliminary audit— Run an automated scan to identify the most common accessibility barriers across all properties. This gives you a baseline scope of work.
3. Commission a full WCAG 2.1 AA audit— Engage IAAP-certified professionals to perform manual testing with screen readers (NVDA, JAWS, VoiceOver), keyboard-only navigation, and assistive technology testing. Automated tools catch roughly 30% of issues; manual testing covers the rest.
4. Prioritise remediation— Triage issues by severity and user impact. Critical items typically include: navigation failures, missing form labels, absent alt text on critical images, inaccessible PDF documents, and broken keyboard focus management.
5. Fix third-party content— Work with vendors to confirm that embedded maps, payment portals, scheduling tools, and other third-party widgets meet WCAG 2.1 AA. If they cannot, find accessible alternatives or provide an accessible alternative means.
6. Address PDF and document accessibility— Government entities often have hundreds of PDF documents on their sites. Prioritise forms, notices, and documents that have no HTML equivalent.
7. Publish an accessibility statement— Include a clear description of your accessibility efforts, the standard you are conforming to (WCAG 2.1 AA), and a feedback mechanism (phone, email, or form) for users to report barriers.
8. Establish an ongoing monitoring plan— Compliance is not a one-time event. Set up quarterly re-audits and integrate accessibility testing into your development and content publishing workflows.

Common Failure Areas for Government Websites

Based on our audits of state and local government digital properties, the most frequently encountered issues are:

• Inaccessible PDF forms — scanned images without OCR or tagged structure
• Missing or generic alt text on images (e.g., “image.jpg” instead of a description)
• Form inputs without associated labels (screen readers announce them as “edit text” with no context)
• Embedded maps and interactive features with no keyboard access
• Low colour contrast on navigation menus, footer links, and call-to-action buttons
• Videos without captions or audio descriptions
• Tables used for layout instead of data, confusing screen reader users
• Inconsistent or absent skip-navigation links

Penalties for Non-Compliance

The consequences of failing to meet the Title II digital accessibility requirements are significant:

• DOJ enforcement actions— The Department of Justice can investigate complaints and initiate enforcement actions resulting in consent decrees with specific remediation timelines and oversight requirements.
• Private lawsuits— Individuals can file lawsuits against non-compliant entities. Courts can order injunctive relief (requiring specific fixes) and award attorney fees to the plaintiff.
• Loss of federal funding— Entities that receive federal financial assistance and fail to comply with Title II may be at risk of losing that funding.
• Reputational harm— DOJ settlements and consent decrees are public documents. Non-compliance signals to residents, businesses, and other stakeholders that the entity is not prioritising inclusion.

How We Help Government Entities

Our IAAP-certified team has audited government websites across multiple states and municipalities. We offer full WCAG 2.1 AA (and 2.2 AA) audits, developer-ready remediation reports, PDF document accessibility remediation, and ongoing monitoring contracts — all delivered with fast turnaround at competitive rates. Every engagement starts with a free preliminary accessibility check so you know exactly where you stand before the deadline.