The ADA Title II Deadline Moved. The Work Didn’t.
On April 20, the Department of Justice extended the ADA Title II web accessibility deadlines by a year. State and local government entities serving 50,000 or more people now have until April 26, 2027. Smaller jurisdictions and special districts have until April 26, 2028. The technical standard, WCAG 2.1 Level AA, did not change. Neither did the scope, the exceptions, or the underlying obligation under Title II.
If you run digital services for a city, school district, library system, public university, or housing authority that was racing the original April 24, 2026 date, the temptation right now is obvious. Take a breath. Move the project to next year’s budget. Reassign the staff time to whatever got deferred to make room for the audit.
We would push back on that. Here is why.
What the extension actually changed, and what it didn’t
The DOJ said it plainly in the rule itself. Even with the new dates, covered entities still have an ongoing obligation under Title II to make their web content accessible to people with disabilities. The deadline moved. The duty didn’t.
The DOJ also signaled where it sees the next twelve months going. From the Federal Register: “the Department fully anticipates implementing the regulation at the new deadline.” That is not the language of an agency preparing to walk away from the rule. It is an agency that gave covered entities more time and expects them to use it.
Three reasons “shelve it until 2027” misreads what happened
Title II liability didn’t move. The 2024 final rule put a technical standard on top of an obligation that has existed since 1990. A lawsuit filed today against an inaccessible state or local government website does not have to wait until April 2027 to find a sympathetic court.
HHS Section 504 didn’t extend. The HHS Section 504 rule from May 2024, which imposes parallel web and mobile accessibility requirements on recipients of HHS funding, still has its original May 11, 2026 first compliance deadline. HHS has not matched the DOJ’s move. Healthcare providers, public university medical centers, county hospitals, and any nonprofit receiving HHS funding face that earlier date regardless of what DOJ did. For dual-covered entities, the earliest deadline controls.
Private litigation is not slowing down. UsableNet’s tracking shows more than 5,000 digital accessibility lawsuits filed in 2025, roughly a 20 percent increase over 2024. Forty-six percent of federal cases in the first half of 2025 involved repeat defendants, organizations sued for a second, third, or even fourth time. None of those cases waited for a federal compliance deadline. They were filed under existing law.
For Minnesota organizations specifically, the picture is sharper. The state recorded 114 federal website accessibility lawsuits in 2024, ranking third nationally behind New York and Florida. The Minnesota Human Rights Act adds its own teeth: under Minnesota Statutes 363A.42 and 363A.43, agencies face penalties of $500 per violation for inaccessible records and continuing education materials, plus reasonable attorney fees and costs. And Minnesota state government adopted WCAG 2.1 Level AA in July 2024, meaning the state has already been holding itself to the same standard the federal rule requires.
If you are a Minnesota public entity hoping the federal extension buys quiet, it doesn’t. The state law and the lawsuit pipeline both predate it.
What twelve extra months actually buy you
The right way to comply with WCAG 2.1 AA is to design and build accessibility in from the start. It’s how we’ve built WordPress sites for cities, housing authorities, libraries, and mission-driven organizations for nearly three decades. Industry data puts that incremental cost at roughly 10 to 20 percent of development time. The wrong way is to wait, audit late, and try to remediate a finished site under deadline pressure. Small public sites can require $5,000 to $15,000 for full remediation, while larger platforms can exceed $100,000, with structural fixes that ripple through the entire codebase.
That gap is the actual value of the extension. Twelve months gives you room to:
- Run a proper audit using both automated scanning and manual testing with assistive technology, not an overlay tool’s promise
- Inventory third-party content and amend vendor contracts so accessibility moves into procurement instead of staying a post-launch problem
- Train the staff who create content so the remediation backlog stops growing while you fix it
- Stand up continuous monitoring so the work you finish in 2026 does not quietly decay before 2027
The organizations that use the next year this way will be in a fundamentally different position next April than the ones running the same fire drill twelve months later, with the same vendors, at higher prices.
Three moves worth making this quarter
If you are an ADA coordinator, IT director, or executive director sitting with this rule, the three highest-impact things to do between now and the end of Q2 are simple:
- Get a baseline audit on your highest-traffic pages and your most exposed templates: forms, PDFs, payment portals, residency and benefits applications.
- Pull every vendor contract that touches your site or app and check whether accessibility language is in it. If it isn’t, add it at the next renewal.
- Decide who owns ongoing monitoring, and how. The audit you finish in June won’t reflect the site you have in March 2027 unless someone is watching the gap.
That third piece is where most accessibility programs come apart. We built Insi for it: continuous WCAG 2.1 AA monitoring across a full site, surfacing new issues as content changes so the work doesn’t unravel between audit cycles. For the clients we work with, Insi runs from the initial audit through design and development checkpoints and into long-term operations, not as a post-launch add-on. If you’d rather keep that in-house, the same principle applies. Pick a tool, set a cadence, assign an owner.
The deadline moved. The work didn’t. The organizations treating the next twelve months as a runway will be ready in April 2027. The ones treating it as a reprieve will be reading a different version of this post next year.
Frequently Asked Questions
If you’d like a partner for this work, ArcStone has been helping cities, housing authorities, libraries, and mission-driven organizations build accessible WordPress sites since 1997. Our Blueprint discovery gives you a real read on where your site stands and what a defensible path to WCAG 2.1 AA looks like for your situation. Insi handles ongoing monitoring once you launch. Reach out at arcstone.com/contact or 612-455-7200.