ADA Title II Deadlines for Public Entities: What April 2027 and 2028 Actually Require

If your organization is a state or local government entity — a city, county, school district, transit authority, water district, library system, or metropolitan planning organization — the DOJ's Title II web accessibility rule now has firm compliance dates. They are closer than most teams assume, and the work behind them takes longer than a single sprint.

Here is what April 2027 and April 2028 actually require, who falls into which deadline, and what a realistic path to compliance looks like.

The rule in one paragraph

In April 2024, the U.S. Department of Justice published a final rule under Title II of the Americans with Disabilities Act setting a specific technical standard for the websites and mobile apps of state and local governments: WCAG 2.1 Level AA. Before this rule, Title II required "accessibility" without naming a measurable standard, which left agencies guessing. The rule removes the guesswork — and attaches deadlines.

The two deadlines

Which date applies to you depends on the population your entity serves:

• April 26, 2027 — public entities serving a population of 50,000 or more, and all state government entities. This is the larger-jurisdiction deadline.
• April 26, 2028 — public entities serving fewer than 50,000 people, and special district governments regardless of population (water, library, transit, housing, fire, and similar single-purpose districts).

A few clarifications that trip people up:

• Population served, not staff size or budget. A small planning agency that serves a large regional population is measured by that region.
• Metropolitan planning organizations (MPOs) are generally tied to the urbanized area they serve, which for most MPOs puts them in the 2027 group.
• Special districts land in the 2028 group as a category — but if a district also serves as, or is operated by, a larger general-purpose government, look carefully at how it is organized before assuming the later date.

If you are unsure which bucket you fall into, treat 2027 as your planning date. It is the safer assumption and the work is the same either way.

What "WCAG 2.1 AA" actually means for your site

The standard is a checklist of testable success criteria, but in practice compliance comes down to a handful of things being true across every page and every document:

1. Every image that conveys meaning has a text alternative, and decorative images are marked so screen readers skip them.
2. Text has sufficient color contrast against its background — a surprisingly common failure on buttons, links, and overlaid banners.
3. Every form field has a programmatic label, so someone using a screen reader knows what to type.
4. The site works with a keyboard alone — no mouse — including menus, sliders, and pop-ups, with a visible focus indicator.
5. Links and buttons have real, descriptive names — not empty, and not "click here."
6. Video has captions and audio has transcripts.
7. PDFs and other posted documents meet the same standard. This is the one that catches most governments off guard.

That last point deserves emphasis: the rule covers web content, and your posted PDFs, meeting agendas, budgets, permit forms, and board packets are web content. For most public entities, the document backlog is larger than the website itself.

What the rule does *not* require

The rule includes limited exceptions — for example, certain archived content, some third-party content the entity does not control, and individualized password-protected documents. These exceptions are narrower than they sound, and leaning on them is risky: the safest and most defensible position is conformance, not exemption. Treat exceptions as edge cases to document, not as a strategy.

Why this takes longer than you think

The gap between "we should fix our website" and "our website and our document library conform to WCAG 2.1 AA" is usually measured in months, for three reasons:

• Scope discovery. Most agencies do not have an accurate count of their own pages and documents. The first real task is finding out how big the problem is.
• Volume. Remediating hundreds or thousands of PDFs is a production effort, not a one-time fix.
• Drift. A site that conforms today drifts out of conformance as staff post new content. Without monitoring, you re-earn the problem every quarter.

Working backward from April 2027, an agency that wants a comfortable margin should be scoping the work in 2026 — not starting it in early 2027.

A realistic path

1. Scan everything. Get an accurate inventory of pages and documents and a prioritized list of what fails and why.
2. Fix by impact. Start with the pages people actually use — the homepage, service pages, forms, and the documents residents download most.
3. Work the document backlog as a parallel track, because it is usually the long pole.
4. Monitor continuously, so new content is caught before it becomes a violation.
5. Keep a record. Documented, ongoing remediation is what demonstrates good-faith compliance if you are ever questioned.

Start by knowing where you stand

You cannot plan a remediation you have not measured. The first step is an honest, complete picture of your current gap — every page and every document — so you know how much runway you actually have before your deadline.

Sources: U.S. Department of Justice, Final Rule on Accessibility of Web Information and Services of State and Local Government Entities (28 CFR Part 35), April 2024; Web Content Accessibility Guidelines (WCAG) 2.1. This article is informational and is not legal advice. Confirm which deadline applies to your specific entity before relying on it.