ADA Title II Deadline Extended to 2027. Don't Spend the Year Waiting.
The DOJ pushed the ADA Title II web accessibility deadline to 2027 for larger public entities and 2028 for smaller ones. Here's what to do with the extra year, and why doing nothing is the wrong move.
Today was supposed to be the day. April 24, 2026. The hard deadline for state and local governments with populations over 50,000 to bring their websites and mobile apps into WCAG 2.1 AA compliance under the new ADA Title II rule.
Then four days ago, on April 20, the Department of Justice released an interim final rule that pushed the date out a year. Larger entities now have until April 26, 2027. Smaller entities and special districts have until April 26, 2028. The ADA Title II deadline did not go away. It just moved.
If you run a city, a county, a public university, a special district, or a court system, you got a reprieve. You did not get a pass.
The underlying law did not change
The interim final rule extended the technical compliance dates. It did not touch ADA Title II’s underlying obligation to provide effective communication and avoid discrimination on the basis of disability. That obligation has always covered digital services. Plaintiffs have already won cases against state and local entities under that framework, with no fixed technical standard, going back over a decade.
So the practical answer to “do we still have to do this work” is yes. The question is whether you do it now while you have time, or you do it during a lawsuit while you do not.
I have watched both versions of this play out. The first one is a budget line. The second one is a budget emergency.
Most public entities are nowhere near ready
We have run accessibility audits across government and nonprofit sites for years. The baseline is rough.
A typical mid-size municipal site has somewhere between 5,000 and 30,000 indexed pages, at least a thousand PDFs, three or four embedded third-party tools (payment portals, permit systems, agenda management), and a content management system that nobody on staff is fully responsible for. Automated scans flag a few hundred WCAG failures per site, and that is before any human goes looking for the issues that automated tools cannot detect, which is most of them.
The fix is real work. Not a banner you can drop into the footer. Not an overlay widget. Real remediation of alt text, focus management, color contrast, keyboard traps, form labels, PDF tagging, and a content workflow that prevents the next batch of inaccessible material from going up next month.
If you tell a vendor “we need to be WCAG 2.1 AA compliant by April 2027” today, they are going to come back with a phased plan that runs nine to twelve months. If you tell them in October, they are going to come back with a plan that runs eighteen months and costs more.
What the year is actually for
Pretend the deadline is still April 2026 and the extension is your buffer. That framing is more useful than the reverse.
Here is what we tell clients to do with the time, in order.
Inventory everything. Get a list of every domain, subdomain, application, document repository, and third-party tool that lives under your jurisdiction. The 2024 rule applies to anything “provided or made available” through your entity, including vendor systems. If your permit portal is operated by a vendor, it is in scope. The agenda system hosted by a different vendor is in scope. So is the Squarespace site some department spun up three years ago and forgot to tell IT about.
We have found ghost properties on every audit we have ever done. There is always at least one site nobody knew was still public.
Hold vendors accountable. Once you have the inventory, send each vendor a letter asking for a current ACR (Accessibility Conformance Report) or VPAT, and a written remediation plan if they are not compliant. Some vendors will respond fast and cleanly. Others will go quiet. The ones that go quiet are the ones you need to start replacing now, not later.
Triage your own pages. Run automated scans across owned content. Group failures by impact, not by count. A single keyboard trap on the donation page is a bigger problem than a thousand instances of poor heading order on archived press releases. Fix the high-impact failures on the high-traffic pages first.
Clean up documents. Most government sites are PDF graveyards. Decide what gets reformatted as accessible HTML, what gets remediated as accessible PDF, and what gets pulled offline because nobody actually needs the 2014 zoning amendment in a public-facing folder. The work of accessibility is also the work of cleaning up content sprawl, and that part has its own benefits.
Train the people who publish. New inaccessible content is being uploaded to your site this week. Probably today. Until your communications staff and department editors know how to write alt text, structure headings, and avoid scanned PDFs, you are remediating into a leaking bucket.
That sequence works whether your real deadline is 2027, 2028, or whatever year a complaint forces it on you.
A note on overlay widgets
Vendors are going to get more aggressive over the next year, because they smell budget. Some of that pitch will be useful. Most of it will be the same accessibility overlay product that has been the subject of multiple class-action lawsuits and a public statement from over 800 accessibility advocates telling organizations not to use them.
If a vendor tells you their plugin will make your site WCAG 2.1 AA compliant in one click, you are talking to a vendor who is going to make your problem worse. They are also unlikely to indemnify you when somebody sues anyway.
The compliance work is structural. The shortcut is that there is no shortcut.
What we are doing for our clients
At Rudder we run WCAG 2.1 AA audits as part of our standard engagement, because for the kinds of organizations we work with, accessibility was always going to be table stakes. Some of our clients were racing toward the original 2026 date. Some now have a year of breathing room and are using it well. A few are using it badly.
The ones using it well are not waiting for legal notice. They are pretending the original deadline still applies, getting the inventory done, having uncomfortable conversations with vendors, and turning their content publishing process into something that does not generate new violations every Monday.
The ones using it badly are nodding politely, filing the issue under “things to deal with later,” and assuming the deadline will move again. It might. It also might not.
A year passes faster than you think.