April Is the ADA Title II Deadline: Final-Quarter Triage for Public Entities

The rule is two years old. The deadline is ten weeks out.

This April, the Department of Justice’s web accessibility rule under ADA Title II starts applying to larger public entities. That means state and local governments. It also means public universities, transit systems, and the districts and agencies attached to them. The standard is WCAG 2.1 Level AA. Smaller entities get another year, until 2027.

If your institution has been running a real accessibility practice, this deadline is mostly paperwork. If it hasn’t, February is the month that separates a manageable spring from a bad one. This briefing is for both groups, with most of the space given to the second.

The ten-week plan, in order

Ninety days is not enough time to fix everything. It is enough time to fix the right things in the right order.

Start with templates and shared components. Navigation, forms, and focus indicators live in the code every page shares. So do heading structure and color contrast. Fixing them once fixes them everywhere. This is where most WCAG failures cluster, and it is by far the most coverage you can buy in a month.

Then triage documents by usage, not by fear. Public sites carry years of old PDFs, and you cannot fix them all by April. Fix the ones people actually download: the current forms, the transactional documents, the things visitors need. The 2019 agenda packet nobody has opened since 2019 is not the priority.

Send the vendor letters now. The third-party tools in your user paths, like payment portals and scheduling systems, are part of your compliance story. Ask each vendor for their conformance documentation with the April date attached, and keep what they send.

What the rule actually settles

A few scope questions have caused more anxiety than they should, because the rule text answers them.

• Archived content gets an exception. Old material kept for reference, unmodified and properly labeled as archived, does not need remediation unless someone requests it. Your entire history is not due in April.

• Your content is yours to fix. Content you post or commission must conform. Truly independent third-party content is treated differently. Embedded vendor tools land on your side of the line, which is why the letters matter.

• Social media and course content have their own provisions. These have specific timelines and conditions worth an hour with counsel rather than a summary here.

• The standard is 2.1 AA. If your last audit used a 2.0-era checklist, it measured against the wrong law. Check the version before you trust the results.

What the audits keep finding

A quick word on where public-sector sites actually fail, because the pattern is consistent and it will focus your ten weeks.

The most common failures repeat everywhere. Keyboard traps in menus and modals, missing focus indicators, form fields without labels, and color contrast that fails on exactly the templates used most. All of them live at the template level, and all of them are fixable in a sprint.

The document problem is usually worse than teams expect and more concentrated than they fear. In many public-sector inventories, a small share of PDFs accounts for most downloads. Usage data can turn an overwhelming document backlog into a manageable priority list. Fix the documents people actually use first.

One warning while budgets are moving: this deadline will bring the overlay vendors back out. The one-line-of-code compliance products do not fix the underlying issues, and lawsuits increasingly name sites that run them. Spend the money on remediation instead. It costs less than the subscription over any honest time horizon.

Build the paper trail as you build the fixes

Here is the part that should lower the temperature for institutions that will not be perfect by April, which honestly describes most of the ones starting now.

Enforcement in this area has always rewarded demonstrated progress over paper perfection. The complaint that arrives finds one of two institutions. One has a dated audit and a ranked plan, plus a fix log and a working feedback channel. The other has none of that. Those two conversations go very differently.

So keep the paper trail as you go. Date the audit. Log fixes as they ship. Publish an accessibility statement with a contact that actually gets answered. Save the vendor correspondence. None of this costs meaningful time on top of the work itself, and it is the difference between meeting a complaint with a file and meeting it with a scramble.

Ten weeks is enough to start well

Step back and the bigger picture is clear. Europe’s accessibility act has been enforced since last June. Title II now has a date at home. Accessibility requirements are converging on WCAG across every market this readership serves.

Institutions that treat accessibility as an ongoing practice absorb each new rule as documentation. Institutions that treat it as a one-time project meet each one as a fresh crisis, and pay for the same work repeatedly. We have been making that case since 2010, and this deadline is a good reason to finally choose the cheaper approach.

Ten weeks is enough if you sequence it. Templates first, then documents by usage, then the letters. Keep the documentation as you go, and start this week.