On April 20, 2026, the Department of Justice published an interim final rule extending the compliance dates for its Title II web accessibility rule by a full year, four days before the first deadline was due to bite. If your organisation is a state or local government, you just got time you did not ask for.
What changed, precisely
The 2024 rule required state and local governments to bring web content and mobile apps in line with WCAG 2.1 Level AA. That part has not changed. Only the dates did:
- Public entities with a population of 50,000 or more: moved from April 24, 2026 to April 26, 2027.
- Public entities under 50,000, and any special district government: moved from April 26, 2027 to April 26, 2028.
The interim final rule took effect the day it was published, with written comments due by June 22, 2026. So this was not a proposal that might happen. It happened, and the consultation came afterwards.
Worth being clear about the scope, because a lot of people still read "web accessibility" as "the website". The rule covers web content and mobile apps, and documents are web content. PDFs, Word files, spreadsheets, slide decks. The council minutes, the budget appendix, the permit application, the public notice about the road closure. All of it.
The reaction was not warm
Disability advocates did not treat this as a sensible administrative adjustment. Maria Town, President and CEO of the American Association of People with Disabilities, called the extension "a profound disappointment and a serious setback for the disability community", and added that "state and local governments have known since at least the Obama administration that accessible websites were not optional". A coalition of disability rights organisations went further and stated unequivocal opposition to the rule.
The argument is hard to wave away. The complaint is not that a year is too short. It is that a decade of notice was already enough, and that extending the deadline pays out to whoever did the least.
Why documents are the piece that slips
Ask anyone who has run one of these programmes where the schedule broke, and it will not be the homepage. Homepages get rebuilt anyway. It is the twelve thousand PDFs sitting behind them.
Three reasons, in rough order of pain.
Volume. A mid-sized county can be publishing several hundred documents a month without anyone treating that as a publishing operation. Nobody signed up to be a publisher. It happened one agenda packet at a time.
Scans. A meaningful share of public documents are photographs of paper. A scanned page has no text at all as far as a screen reader is concerned, so before you can think about headings or reading order, you need OCR. That is a separate project with its own accuracy problems.
Forms. A PDF form that looks fillable and is actually flat is a trap for everyone, and doubly so for keyboard and screen reader users. If a form matters, the honest fix is usually not an accessible PDF at all. It is an HTML form.
The exceptions are narrower than people want them to be
The rule carries limited exceptions, including for certain preexisting electronic documents that were already available before the compliance date. That sounds generous until you notice what it does not cover: anything you publish from here on. A document you upload next Tuesday is not archived content, no matter how boring it is.
Treat the exception as a way to prioritise a backlog, not as a reason to leave it alone. If a five-year-old PDF is still the only place a resident can find the recycling schedule, its age is not really the point.
What the extra year is actually good for
The temptation is to file this away and rediscover it in early 2027. Better use of the time, in order:
- Stop producing new inaccessible documents. This is the single highest-value change and it is a process fix, not a remediation project. Tag structure at authoring time in Word or InDesign costs minutes. Retrofitting it later costs hours per document. Our PDF accessibility guide covers what a screen reader actually needs.
- Inventory what you have, and sort by traffic rather than by folder. Analytics will usually show that a few dozen documents account for most of the downloads.
- Convert the top of that list to HTML where the content suits it. An accessible web page beats an accessible PDF for most public-facing information, and it is cheaper to maintain.
- Remediate the rest against a real standard, which for documents means PDF/UA alongside WCAG, not a vendor's automated score out of 100.
One caveat before you relax completely. Writing for Jackson Lewis after the announcement, attorneys pointed out that a separate Department of Health and Human Services rule under Section 504 carried its own May 2026 date and was not covered by the DOJ extension. Different agency, different rule, different clock. If you receive federal health funding, do not assume this delay applies to you.
