DOJ Grants Counties More Time on ADA Web Accessibility Rule

The U.S. Department of Justice has issued a rule granting an extension on the timeline for meeting web-based accessibility requirements under the Americans with Disabilities Act, giving counties and other public entities additional breathing room before compliance obligations take effect.

That is the headline fact. What the National Association of Counties' announcement does not spell out — the new deadline itself, the rule's filing date, and which entity sizes gain the most — is exactly what local governments now need to pin down. Extensions help. They do not erase the underlying obligation.

What does the extension change?

The DOJ rule in question governs how state and local governments must make web content and mobile apps accessible to people with disabilities. An extension moves the compliance date. It does not narrow the substantive requirements themselves.

For counties, that distinction matters. The technical work — auditing sites, remediating documents, training content staff — takes months regardless of when the deadline lands. A later date buys scheduling room, not a lighter workload.

The National Association of Counties flagged the extension for its members, signaling that local governments had pressed for more time. That pressure is easy to understand. County websites carry some of the highest-stakes public content anywhere: emergency alerts, tax payments, court records, permit applications. When those interfaces fail assistive technology, the exclusion is not theoretical.

Why counties were watching this closely

Public entities have faced ADA obligations for decades, but web-specific federal rules arrived only recently, after years of advocacy and litigation filled the gap left by absent regulation. Counties without dedicated digital teams have struggled to interpret what compliance looks like in practice.

An extension addresses one complaint: timing. It leaves others standing — funding, staffing, and the technical question of how to remediate legacy PDFs and aging content management systems.

There is a familiar pattern here worth naming. Deadlines get extended; scope rarely does. Counties that treat the extra time as a reason to delay planning will face the same audit backlog later, compressed into fewer months.

What should local governments do now?

The practical move is unchanged by any deadline shift:

• Inventory every public-facing page, document and app.
• Run automated accessibility scans, then manual testing with screen readers and keyboard-only navigation.
• Prioritize high-traffic services: payments, forms, emergency information.
• Document remediation progress, since good-faith records carry weight in enforcement conversations.

None of that work expires when a compliance date moves.

The open questions

Counties reading the announcement should verify specifics against the rule text itself: the exact new compliance dates, whether different entity sizes face different timelines, and whether the extension covers mobile apps or web content only. The summary notice does not say.

What is clear is the direction. Federal regulators extended the runway but kept the requirement on the books, and future rulemaking or litigation could still test whether the new timeline holds — counties that build accessibility capacity now will absorb whatever comes next with the least disruption.

By Priya Raman