DOJ guidance · March 15, 2026

The DOJ Web Accessibility Rule: What It Changed and Who It Reaches

In April 2024 the U.S. Department of Justice finalized its rule under Title II of the ADA setting web and mobile accessibility requirements for state and local government entities. The headline: WCAG 2.1 Level AA is the binding standard, with compliance deadlines staggered by jurisdiction size (large entities earlier, small later). Here is the plain-English read and why it matters beyond the entities it technically binds.

Who the rule binds

Title II covers state and local government programs, services, and activities — including state university systems, county health departments, city transportation agencies, public libraries, public K–12 schools, and municipal-run venues. The rule applies to their websites, mobile apps, and — critically — the web content they make available through third-party platforms and vendors.

Large entities (50,000+ residents, or state/territory) had to comply by April 24, 2026. Smaller entities had an extra year. Special districts have their own timeline based on the population they serve.

What the rule does not change

• It does not create a new right of private action. Title II enforcement continues to run through DOJ administrative complaints or private suits already available under pre-rule law.
• It does not bind private businesses directly. Title III public accommodations — private restaurants, stores, hotels, hospitals, offices — are not subject to the rule.
• It does not remove anything. All pre-existing Title II obligations still apply.

Why private businesses should read it anyway

Three reasons:

1. It fixes WCAG 2.1 AA as the federal accessibility benchmark. Before the rule, DOJ guidance pointed to WCAG informally. Private-plaintiff lawyers suing under Title III had to argue WCAG as the applicable standard case by case. Now the federal government has codified it. Title III plaintiffs will cite the rule as evidence that WCAG 2.1 AA is the floor.
2. State-level adoption usually follows. Several state attorney-general offices have already signaled they will treat WCAG 2.1 AA as the enforceable standard under their state-level disability-rights laws — which do reach private businesses, often with damages available (California Unruh, New York State and City HRLs, etc.).
3. Vendor contracts shift. Businesses that sell into government — SaaS platforms, learning-management systems, web-hosting providers — are getting accessibility riders in every RFP. The compliance bar they hold their vendors to cascades through their commercial customers too.

What to do if you run a state or local entity

1. Inventory your digital surface: website, mobile apps, PDFs, video content, third-party platforms (patient portals, registration systems, LMS, payment pages).
2. Run an audit against WCAG 2.1 Level AA. Most of these rules are the 12 criteria we cover in our plain-English WCAG guide.
3. Document a remediation plan with dates.
4. Review vendor contracts for accessibility representations. Require vendors to warrant WCAG 2.1 AA.
5. Publish an accessibility statement with a contact method for complaints.

What to do if you run a private business

1. Treat WCAG 2.1 AA as your working target — DOJ has now said it in writing.
2. Start with the same 12 highest-value criteria.
3. Fix before the demand letter, not after.
4. Document your process so you can show good-faith effort if you are ever challenged.