The DOJ just handed public entities another year to meet the Title II web accessibility rule. The deadline moved. The work didn't.
Why it matters: If you're responsible for a website for a city, county, school district, utility district, or public agency, the legal expectation hasn't changed. Your pages, forms, and PDFs still have to meet WCAG 2.1 Level AA — the accessibility standard the DOJ rule points to.
The catch: For any organization sitting on years of accumulated content, compliance was never a plugin you install or a box you check. The extra year mostly buys time to do work that was always going to be substantial.
Web accessibility refers to the way people with disabilities access and use your website, documents, forms, and online services. That may include someone navigating with a screen reader, using a keyboard instead of a mouse, relying on captions for video content, or needing sufficient color contrast to read information on a page. The goal of the DOJ rule is to ensure public services remain accessible regardless of how someone reaches them.
What actually changed
On April 20, 2026, the DOJ issued an Interim Final Rule extending the original deadlines by one year:
- April 26, 2027 — for state and local governments serving a population of 50,000 or more.
- April 26, 2028 — for public entities under 50,000, and for all special district governments.
The technical standard — WCAG 2.1 Level AA — did not change. Neither did the scope: every page, form, PDF, and digital service you offer is expected to meet accessibility requirements.
Why Accessibility Projects Stall
Most websites don't become inaccessible because of one bad decision. A site launches with good intentions. Staff change. New departments start posting. PDFs get uploaded. Forms get added. Documents built for print get published online.
Five or ten years later, the site quietly contains hundreds or thousands of PDFs, images without alternative text, forms that are hard to navigate by keyboard, and content structures that confuse screen readers. None of it happened overnight, and by the time an organization sits down to prepare for compliance, the scope is usually larger than anyone expected.
That's why accessibility work tends to become an operational project as much as a technical one. In many organizations, nobody knows how many PDFs are even on the website until a review begins. Meeting agendas, board packets, annual reports, policy manuals, application forms, and newsletters have often been piling up for years. Before remediation can start, someone has to decide what stays, what gets archived or removed, and who will be responsible for keeping new content accessible going forward.
Where Accessibility Widgets Fit
A few years ago we wrote about accessibility tools like UserWay, and we still think they have value. A toolbar that lets visitors adjust text size, contrast, and reading aids genuinely improves the experience for a lot of people.
What a widget was never built to do is correct the underlying structure, content, documents, and code of a website. It can enhance a site that's already accessible. It can't make an inaccessible one compliant on its own — and as the requirements have gotten more specific, that distinction matters more than it used to. The right way to think about an overlay is as one piece of a larger accessibility strategy, not the strategy itself.
Accessibility Is an Ongoing Responsibility
This is the part that catches organizations off guard. A site can pass an accessibility review today and start collecting new issues tomorrow. New PDFs go up. New staff join. Publishing habits drift. Accessibility gets hard when ownership is unclear.
This is where most accessibility projects quietly fail: after the initial remediation is done, new content gets added, staff changes occur, and old publishing habits return. Because interGen already provides ongoing website stewardship for many of our clients, accessibility can become part of an established maintenance process rather than a one-time project that gradually falls out of date. Depending on where you're starting, that work can include:
- Accessibility audits using established tools alongside manual testing
- Joomla template and source-code remediation
- Form and navigation improvements
- PDF and document remediation
- Staff training and publishing guidance
- Ongoing monitoring as new content is added
Planning Ahead
The extension buys time, but if your organization has years of legacy content, this isn't something to leave until the deadline is in sight. The earlier you understand the actual scope of the work, the more realistic the plan — and the less it costs you in a last-minute scramble.
Accessibility isn't a feature you install. It's a responsibility you manage. If you'd like a clear picture of where your site stands today and what steps make the most sense from here, reach out and we'll walk through it with you.
References
- U.S. Department of Justice. Extension of Compliance Dates for Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities (Interim Final Rule, 28 CFR Part 35), 91 FR 20902. Federal Register
- U.S. Department of Justice, Civil Rights Division. State and Local Governments: First Steps Toward Complying with the ADA Title II Web and Mobile Application Accessibility Rule. ADA.gov