If you run a private business, the most important federal accessibility development in years is a rule that, on paper, has nothing to do with you. On April 24, 2024, the Department of Justice published a final rule under Title II of the ADA setting a single technical standard — WCAG 2.1 Level AA — for the websites and mobile apps of state and local governments (ada.gov fact sheet). It does not bind private companies. And yet it quietly resolved a question businesses have argued about for a decade: what does “accessible” actually mean in U.S. law?
What the rule actually says
The rule covers state and local governments — including their agencies and departments, special purpose districts, Amtrak, and commuter authorities — and applies whether they build content themselves or hand it to a vendor (Federal Register, 2024-07758). Those entities must bring their web content and mobile apps into conformance with WCAG 2.1 Level AA, the W3C’s published guidelines. As the DOJ’s own guidance puts it, “although WCAG includes the word ‘guidelines,’ complying with WCAG 2.1 Level AA is required under the rule” (ada.gov first steps).
Deadlines are staggered by population, and they moved this spring. The original dates were April 24, 2026 for entities serving 50,000 or more people and April 26, 2027 for smaller entities. In an Interim Final Rule effective April 20, 2026, the DOJ pushed both back by a year: large entities now have until April 26, 2027, and entities under 50,000 plus all special district governments have until April 26, 2028 (Federal Register, 2026-07663). Notably, the Department cited a reason businesses should sit up for: it had “overestimated the capabilities” of entities to remediate, and warned that generative AI cannot reliably automate accessibility fixes at scale.
The rule is not absolute. It carves out five narrow exceptions — archived content, pre-existing conventional documents like old PDFs, third-party content the government didn’t post, password-protected individualized documents, and pre-existing social media posts (small entity compliance guide). There’s also a limited safe harbor for minor nonconformance that doesn’t actually impair access. But the guidance is blunt that you “cannot use this part of the rule to avoid trying to meet WCAG 2.1, Level AA.”
Why this binds governments, not businesses
The ADA splits into titles. Title II governs public entities; Title III governs “places of public accommodation,” which is where private businesses live. The 2024 rule amends only the Title II regulations. The DOJ has not issued — and has no active rulemaking for — an equivalent Title III web rule, and it withdrew its earlier Title III web efforts years ago.
So if you sell shoes, run a clinic, or operate a law firm, no statute gives you an April 2027 deadline. That sounds like good news. It mostly isn’t, and here’s why.
What businesses should actually take from it
WCAG 2.1 AA is now the closest thing to an official U.S. federal standard. For years, the defense in a Title III website case could argue there was no legally defined target. That argument is weaker today. The federal government has formally declared, in regulation, that 2.1 AA is the technical standard for ADA web accessibility. Courts hearing Title III claims already lean on WCAG as the de facto benchmark, and a sister-title federal rule pointing at the same version reinforces it. If you want to understand the criteria themselves, our WCAG explainer and the POUR principles walk through what conformance involves in plain language.
The litigation that already targets you isn’t slowing down. Title III web lawsuits have run in the thousands every year. UsableNet’s 2025 year-end report counted more than 5,000 digital accessibility lawsuits filed in that year alone, with e-commerce making up roughly 70% of them (UsableNet 2025 report). Seyfarth Shaw, which tracks federal filings specifically, recorded thousands of website cases in federal court the prior year (Seyfarth ADA Title III blog). These cases name WCAG failures — missing alt text, poor color contrast, unlabeled forms — as the substance of the claim. The standard the Title II rule made official is the same standard plaintiffs cite against private sites. (This is general information, not legal advice — talk to a qualified ADA attorney about your specific exposure.)
The DOJ just told you, on the record, that automated fixes don’t work. When the Department extended its own deadlines, it pointed to the limits of generative AI for remediation. That same logic torpedoes the accessibility-overlay pitch — the widget that promises one-line compliance. UsableNet’s data shows lawsuits continuing against sites that already use these tools, and our breakdown of why overlays don’t work explains the mechanics. The government’s own conclusion is that real conformance takes manual, human work.
The DOJ’s recommended method is a blueprint you can borrow. Its first-steps guidance tells covered entities to inventory their content, prioritize high-traffic and transactional pages, and — critically — combine automated scanning with manual testing, because “you won’t be able to use automated testing tools alone.” That is exactly how a private business should approach an accessibility audit: start with the pages where customers register, search, pay, and check out, then remediate against 2.1 AA. Our ADA compliance checklist turns that into concrete steps.
The practical takeaway
The Title II rule didn’t create a new obligation for private businesses. It did something arguably more consequential: it ended the ambiguity about what accessible means. The federal benchmark is WCAG 2.1 AA, the government has said automated shortcuts aren’t sufficient, and the lawsuit volume aimed at private sites isn’t waiting for a Title III rule that may never come.
The businesses that fare best treat the government deadlines as a signal, not a loophole — they bring their sites to the same standard now, through real remediation rather than a bolt-on widget. If you want to know where you stand against the standard the DOJ just made official, run a free accessibility scan and we’ll show you.