The ADA Title II Deadline Moved. What That Actually Changes.

On April 20, 2026 the Department of Justice issued an interim final rule pushing both Title II web accessibility compliance dates back by one year. A lot of vendor pages and explainers still show the old dates, so it’s worth being precise about what moved and what didn’t.

The new dates

• April 26, 2027 — public entities serving a population of 50,000 or more.
• April 26, 2028 — public entities serving under 50,000, and special district governments regardless of the population they serve.

That second line catches people out. “Special district government” is a census classification, not a size: regional planning councils, transit and port authorities, drain and conservation districts, library districts. A regional agency covering a dozen counties and well over 50,000 residents can still sit in the 2028 group, because it is a special district rather than a general-purpose government. If you’re unsure which bucket your entity is in, that is a question for your attorney, and it is worth asking early — it changes your timeline by a full year in either direction.

What did not change

The technical standard is still WCAG 2.1 Level AA. The scope is still broad: the main site, departmental sites, online forms and services, and password-protected content.

More importantly, the underlying obligation never depended on the 2024 rule. Title II has required equal access to programs and services since 1990. The web rule set a specific technical yardstick and a date; it did not create the duty. An entity with an inaccessible site today can still face a complaint today. The extension moved a compliance deadline, not the exposure.

Why an extra year is less than it sounds

For most agencies the website itself is the easy part. A competent rebuild gets templates, navigation, forms, and contrast to AA without much drama. The part that consumes the calendar is the document back-catalogue.

A mid-sized agency routinely has several hundred PDFs: board minutes, agendas, budgets, master plans, permit forms, zoning maps. Most were produced by scanning, or by exporting from Word with no tagging, no reading order, and no alternative text. Remediating one properly takes anywhere from twenty minutes to several hours depending on tables and scanned images. Multiply that out before deciding how much runway you have.

This is why the honest first step is an inventory rather than a redesign. You need to know how many documents exist, which ones people actually open, which can be replaced outright with an accessible HTML page, and which are candidates for the archive.

The archived-content exception, stated precisely

This is the most misunderstood part of the rule, and the misunderstanding is expensive in both directions — some agencies plan to remediate documents they never needed to touch, others assume an “archive” folder is a blanket exemption.

It is not a blanket exemption. Content qualifies only when all four conditions hold:

• It was created before the entity’s applicable compliance date, or it reproduces paper or other media created before that date.
• It is kept in a clearly designated archive area of the site.
• It has not been altered since being archived.
• It is organized and searchable.

The condition that does the most work in practice is the third one. If a document is still part of how the agency operates — a permit form residents submit, a fee schedule staff cite, a zoning ordinance that gets amended — it is in active use, and moving it into an archive folder does not make it archived content. The exception is for the historical record, not for the filing cabinet you still open.

Used correctly it is genuinely powerful. The decade of board minutes nobody has opened since they were posted can live in a properly designated, organized, searchable archive, and the remediation budget goes to the forms and pages people actually use.

What to do with the extra year

If you were already behind, the extension is breathing room rather than a reprieve. A realistic sequence:

• Inventory first. Every page and every document, with traffic data where you have it. You cannot scope the work without knowing the size of the pile.
• Triage into four buckets: remediate, replace with HTML, archive, retire. Most documents land in the middle two.
• Fix the transactional paths early. Forms, payments, permit applications, and contact pages are where an accessibility failure actually denies someone a service — and where a complaint is most likely.
• Design the archive deliberately, so it satisfies all four conditions rather than looking like a dumping ground.
• Budget for the approval cycle. If the work needs board approval, the procurement calendar is part of your timeline, not separate from it.

One thing worth protecting

Whatever else you do, don’t let a redesign quietly drop the old site’s documents. Agencies have retention obligations, and in a surprising number of cases the website is the only place a given set of minutes still exists. When the outgoing host gets switched off, the files go with it. Get a complete export before anyone cancels anything, and map the old URLs to the new ones so the links on state sites, grant portals, and other agencies’ pages keep working.

If you want help scoping it

We work on exactly this — accessibility remediation, document triage, archive sections built around the exception, and migrations off legacy platforms. See our government services, or get in touch for an inventory and an honest estimate of the size of the job.

Related: Government & public sector, ColdFusion modernization, When Your Old Web Guy Disappears, Rebuild or Fix?