Halfway through 2026, the numbers are in, and they’re not good. UsableNet’s 2026 Midyear Report found that the first six months of this year produced the highest volume of digital accessibility lawsuits the firm has ever tracked, putting the full-year total on pace to blow past 6,000 filings. If that holds, 2026 will be the worst year on record for ADA web accessibility litigation — worse than the 27% jump the industry saw in 2025. For WordPress site owners who’ve been putting off a real accessibility fix, the midyear data makes the case that “later” keeps getting more expensive.
What the Midyear Report Actually Shows
UsableNet has tracked ADA digital accessibility litigation for years, and its monthly and midyear reports are treated as one of the more reliable pulse checks on where plaintiffs’ firms are focusing. The 2026 midyear numbers show two trends that matter for anyone running a business site:
- Filing volume in H1 2026 was the highest UsableNet has ever recorded for a six-month period, with projections putting 2026 on track to exceed 6,000 total filings once state court cases are counted alongside federal Title III suits.
- July alone added roughly 401 new lawsuits, and 77 of those defendants had already been sued once before over digital accessibility — meaning a prior settlement or fix didn’t necessarily end the exposure.
That second point is worth sitting with. A lawsuit isn’t a one-time event you settle and move past. If the underlying site issues aren’t actually resolved, or if new pages and features introduce new problems, the same business can end up back in court.
The Widget Data Is the Part That Should Worry You Most
The most striking detail in the report isn’t the overall volume — it’s what’s happening to sites that already had an accessibility widget or overlay installed. UsableNet counted lawsuits against companies running an accessibility widget in every single month of H1 2026: 165 in January alone, still 98 in June. Of July’s new filings, 113 defendants were sued despite having a third-party accessibility tool active on their site at the time.
This isn’t a new finding — it’s a confirmation of a pattern that’s held steady for years now. Plaintiffs’ attorneys know how to test past an overlay: they turn off JavaScript, use a real screen reader instead of clicking through a widget’s simplified controls, or simply document that the underlying markup still has the same missing labels and broken focus order it always did. A widget can change what a sighted visitor sees on top of the page. It generally can’t change whether a `
Why “We Already Have a Tool” Isn’t a Legal Answer
It’s easy to see why overlays remain popular: they promise a same-day fix with a single script tag, no developer time required. But the midyear data is a direct rebuttal to the pitch. If overlays reliably prevented lawsuits, the monthly widget-lawsuit count would be trending toward zero. Instead it’s been a consistent presence in every month of 2026 so far. The FTC has also taken an interest in overlay marketing claims, and the honest reading of the evidence at this point is that an overlay is, at best, a visual layer — not a substitute for fixing the HTML, ARIA, and interaction patterns underneath it.
What Actually Reduces Legal Exposure
Nothing eliminates legal risk entirely — no vendor, plugin, or consultant can honestly promise that, and you should be skeptical of anyone who does. But the pattern in litigation data consistently favors sites that have done real remediation work over sites that installed a bolt-on tool and stopped there. A more defensible approach looks like this:
- Run an actual code-level scan to find real WCAG failures — missing alt text, unlabeled form fields, insufficient color contrast, keyboard traps — rather than relying on a tool that only adjusts font size and contrast on top of the existing markup.
- Fix the issues in the underlying HTML and theme/plugin code, not just at the presentation layer.
- Re-scan on a schedule, since new posts, plugins, and page builder blocks introduce new issues constantly — a one-time fix doesn’t stay fixed.
- Keep a written accessibility statement and documentation of remediation efforts, which matters if a claim does arrive.
None of this makes a site immune from being sued — plaintiffs’ firms sometimes file against sites that are genuinely well-built, and litigation volume this high means almost any business with meaningful traffic is a plausible target. But the data is clear that businesses relying solely on an overlay are not seeing that investment translate into fewer lawsuits, month after month, in 2026.
What This Means If You Run a WordPress Site
Most small and mid-size businesses don’t have a dedicated accessibility engineer on staff, and hiring an outside audit firm for every site update isn’t realistic for most budgets. That’s the gap plugin-based tools are supposed to fill — but the midyear numbers are a reminder to be specific about what kind of tool you’re using. A scanner that flags real code issues in your theme and plugins is doing fundamentally different work than a script that repaints your page for visitors. Both can coexist, and a toolbar that gives visitors contrast and text-size controls isn’t worthless — it just isn’t a substitute for fixing what’s broken underneath.
Take Action
LEWCA is built around that distinction. It combines a WCAG scanner that finds real, code-level issues in your WordPress site with an accessibility toolbar for visitors — and the Pro plan adds AI-powered code fixes, scheduled scanning so new issues don’t slip through unnoticed, and compliance reports you can keep on file. We won’t tell you it gets you to 100% compliance, because no tool honestly can — but it’s built to fix actual problems in your code, not just mask them. See pricing plans or download LEWCA to get started.