ADA Title II Web Accessibility Deadlines: Are You Ready?

Updated April 22, 2026. This post was originally published in May 2025, when the compliance deadlines were April 24, 2026 for larger entities and April 26, 2027 for smaller ones. On April 17, 2026 the Department of Justice issued an interim final rule extending both dates by one year; it was published in the Federal Register on April 20, 2026. The deadlines below reflect the extension. Nothing else about the rule changed — WCAG 2.1 Level AA remains the standard and the scope is unchanged.

If you run a state or local government website, operate a public school district portal, or build software for government agencies, web accessibility compliance is no longer optional — it is a federal legal requirement with hard deadlines attached.

The Department of Justice finalized a rule in 2024 establishing explicit WCAG 2.1 Level AA requirements under Title II of the Americans with Disabilities Act (ADA). Those deadlines were subsequently extended by a Federal Register notice published April 20, 2026. Here is what the current compliance timeline looks like and what it means for your organization.

What Is ADA Title II?

Title II of the ADA prohibits discrimination by state and local governments on the basis of disability. It applies to all programs, activities, and services offered by state and local government entities — including, increasingly, their digital presence.

For most of the ADA's history, Title II contained no specific technical standard for web or mobile accessibility. Government entities were expected to provide effective communication and equal access, but the mechanics were left to interpretation. The DOJ's 2024 rulemaking changed that by specifying WCAG 2.1 Level AA as the enforceable standard for web content and mobile apps.

Covered entities include:

• State government departments and agencies
• County and municipal governments
• Public school districts and public universities
• Special districts (water authorities, transit agencies, port authorities)
• Any state or local government entity regardless of size

Unlike the EAA, which exempts small enterprises, Title II covers all state and local government entities — there is no small-entity carveout.

The Extended Compliance Deadlines

The original 2024 rule set a two-tier deadline based on population served. The April 2026 Federal Register extension preserved that two-tier structure but shifted the dates:

April 26, 2027 — Entities serving populations of 50,000 or more must have their web content and mobile apps in compliance with WCAG 2.1 Level AA by this date. This covers most city governments, large county agencies, state departments, and larger public university systems.

April 26, 2028 — Entities serving populations under 50,000 have an additional year. This covers smaller towns, rural counties, small special districts, and community college systems below the population threshold.

The population threshold is based on the entity's total served population, not the traffic to a particular website. A county government serving 75,000 residents falls under the 2027 deadline for all of its digital properties.

Important: The extensions do not delay the obligation to make progress. The DOJ has been clear that entities should begin remediation immediately and use the compliance window to address existing barriers systematically, not to postpone starting.

What Standard Applies: WCAG 2.1 Level AA

WCAG 2.1 Level AA is a W3C (World Wide Web Consortium) technical standard that defines four principles of accessible web content:

• Perceivable: Content must be presentable to users in ways they can perceive — images need text alternatives, videos need captions, and text must be readable by screen readers.
• Operable: All functionality must be available via keyboard (not just mouse), with enough time to complete tasks and no content that could cause seizures.
• Understandable: Pages must be readable and predictable, with input assistance for forms and error identification.
• Robust: Content must be reliably parsed by assistive technologies including screen readers, switch access devices, and voice control software.

WCAG 2.1 AA includes 50 success criteria across these principles. The most commonly failed criteria on government sites are: missing image alt text, insufficient color contrast, unlabeled form inputs, missing skip navigation links, and inaccessible PDF documents (PDFs must meet PDF/UA standards or be provided with accessible HTML equivalents).

Who Enforces It?

The DOJ's Civil Rights Division enforces Title II compliance. Enforcement can be triggered by:

Complaints filed by individuals with disabilities to the DOJ's Civil Rights Complaint Portal. The DOJ receives thousands of accessibility-related complaints per year and has active investigations open against multiple state and local entities.

DOJ-initiated investigations, particularly targeting high-profile government services and entities that have received prior accessibility complaints without resolution.

Private litigation under Title II. Unlike some federal civil rights statutes, individuals can bring private suits directly in federal court without exhausting an administrative process. Government websites are a frequent target of accessibility litigation.

For vendors who build software for government clients: a government entity's Title II obligations do not disappear when they outsource their web presence. Procurement increasingly includes accessibility requirements, and several states have passed additional accessibility procurement laws that apply to vendors bidding on government contracts.

Practical Steps to Get Ready

Know your deadline tier. Identify whether your entity or your government clients fall under the 2027 or 2028 track based on population served. Do not assume you are in the smaller tier without checking — the population figure is the total served population, not just website users.

Conduct a baseline audit. You cannot remediate what you have not measured. A comprehensive accessibility audit combines automated scanning (fast, high coverage of certain violation types) with manual keyboard and screen reader testing (required to catch interaction-layer issues that automation misses). Start with the automated layer to scope the effort.

Address high-priority pages first. Government entities typically have hundreds or thousands of pages. Prioritize pages that represent core government services: benefits applications, permit systems, public meeting agendas and minutes, emergency information, and any form submission flow. These are the pages most likely to trigger complaints and the most critical for residents with disabilities.

Integrate accessibility into the development pipeline. If your CMS, custom code, or third-party widgets are generating new accessibility violations with every release, you are running on a treadmill. Catching violations at the pull request or CI stage means the deployment pipeline itself prevents regressions.

Prepare an accessibility conformance report. A VPAT (Voluntary Product Accessibility Template) or equivalent accessibility statement helps document your conformance posture. For government entities, a public accessibility statement is both a best practice and, in some jurisdictions, a legal requirement.

The deadlines are set. Whether your organization is a municipality heading toward 2027 or a rural county with until 2028, the path forward is the same: audit, remediate, automate, and maintain. Accessibility compliance is not a one-time project — it is an ongoing commitment that requires the same attention as security or performance.