If you only track one area of web compliance this year, make it this one. In the last twelve months the legal and regulatory ground under web accessibility shifted on five fronts at once: a U.S. federal deadline moved, Europe’s enforcement window opened, the consensus technical standard advanced, lawsuit filings hit a new high, and a federal regulator put a price on overlay hype. Here is the 2026 picture — with a source behind every number — and what each piece means for a small business that just wants to do this right.
The DOJ Title II deadline moved — but the clock is still ticking
In April 2024 the Department of Justice finalized a rule under Title II of the ADA setting WCAG 2.1 Level AA as the technical standard for the websites and mobile apps of state and local governments. In April 2026 the DOJ issued an interim final rule extending those compliance dates by one year: entities serving populations of 50,000 or more now have until April 26, 2027, and smaller entities and special districts until April 26, 2028 (Federal Register, April 20, 2026).
One caveat that trips people up: Title II governs public entities — cities, counties, public universities, transit agencies. If you run a private business, this rule does not set your deadline. But it does cement WCAG 2.1 AA as the federal government’s reference point, and private businesses are still routinely sued under Title III of the ADA, which courts have long read to cover commercial websites. The extension buys governments time; it changes nothing about private-sector exposure.
Europe’s Accessibility Act now has enforcement teeth
The big international development happened on June 28, 2025, when the European Accessibility Act (EAA) reached its enforcement milestone. From that date, EU member states can investigate complaints, demand remediation, and impose sanctions on covered products and services placed on the market (European Commission).
This matters to U.S. companies more than many realize. The EAA reaches any business selling into the EU — e-commerce, banking, transport, telecom, and digital services — regardless of where it is headquartered. There is a carve-out for microenterprises (fewer than 10 employees and under €2 million turnover), and the technical benchmark, EN 301 549, aligns closely with WCAG 2.1 AA (Level Access EAA guide). If you ship to European customers from a U.S. ecommerce store, this is a live obligation, not a future one.
WCAG 2.2 is the standard worth targeting
Most laws still cite WCAG 2.1, but the consensus standard has moved on. WCAG 2.2 became a W3C Recommendation on October 5, 2023, adding nine new success criteria over 2.1 — covering focus visibility, dragging alternatives, target sizes, consistent help, and reducing redundant entry, among others (W3C, What’s New in WCAG 2.2). The W3C’s working group explicitly recommends adopting 2.2 as your conformance target even where regulations still reference 2.1, because anything conforming to 2.2 also conforms to 2.1.
That is exactly why Curbcut builds to 2.2 AA: it is backward-compatible, it anticipates where policy is heading, and the new criteria fix real problems for users with low vision, motor, and cognitive disabilities. Our WCAG success criteria guide walks through what each one asks for.
Lawsuit filings hit a new high in 2025
The litigation trend is unambiguous. Seyfarth Shaw, which has tracked ADA Title III filings since 2013, counted about 3,117 website accessibility lawsuits in federal court in 2025 — roughly a 27% jump over 2024, making web cases more than a third of all Title III filings, with New York federal courts the busiest (Seyfarth ADA Title III blog). Counting state courts too, UsableNet projected the U.S. would clear roughly 4,975 digital accessibility lawsuits by year-end 2025, a 20% rise on 2024 (UsableNet 2025 mid-year report).
Two patterns are worth your attention. First, a large share of filings name repeat defendants — businesses sued more than once because the underlying code was never fixed. Second, plaintiff activity stays concentrated in a handful of venues; our lawsuits-by-state index is a good place to gauge local risk if you operate somewhere like New York or California.
The FTC put a price on overlay claims
The development that should change behavior fastest: in 2025 the Federal Trade Commission fined overlay vendor accessiBe $1 million for deceptively marketing its accessWidget as able to make “any website” WCAG compliant (FTC press release, January 2025), with the order finalized in April (FTC final order).
Meanwhile the widgets keep drawing lawsuits rather than deflecting them. UsableNet logged hundreds of 2025 filings against sites that already had an accessibility widget installed — well over a hundred in single months (UsableNet 2025 mid-year report). The reason is mechanical: an overlay scripts changes on top of broken markup but cannot fix the underlying HTML, and automated tooling alone reliably catches only a fraction of WCAG issues — which is why 94.8% of the top million home pages still had detectable WCAG failures in 2025 (WebAIM Million 2025). A bolt-on widget does not move that needle. We unpack the mechanics in do accessibility overlays work?.
What this means for your business
Strip away the acronyms and the takeaway is simple: the standard is rising, enforcement is broadening, and shortcuts now carry their own liability. The durable response is the unglamorous one — fix the actual code. Curbcut does manual remediation to WCAG 2.2 AA precisely because that is what holds up against a screen reader, a regulator, and a plaintiff’s expert alike. If you want a practical, non-panicked plan, start with how to avoid an ADA lawsuit or get a real picture of your gaps through an accessibility audit.
One last note: this article summarizes public regulatory and litigation developments for general information. It is not legal advice. For guidance on your specific obligations and risk, talk to a qualified attorney.
Want a fast, honest read on where you stand against 2026’s standards? Run a free accessibility scan.