Nearly a Third of Businesses Sued Over Website Accessibility Already Had a Widget Installed

Here’s a stat worth sitting with: of the 432 new ADA website accessibility lawsuits filed in August 2026, roughly 31% of the businesses being sued had already installed an accessibility widget on their site before the lawsuit landed. About a quarter of the businesses sued had been sued over this before, too.

We’ve written before about the rise in these lawsuits and why they’re becoming a real cost of doing business online, not just a rare edge case. This new number gets at something more specific: a lot of businesses think they’ve already solved the problem, and they haven’t.

What’s actually going on with these widgets

Accessibility widgets — the little floating icon in the corner of a site that promises to “make your website ADA compliant” with one line of code — are appealing for an obvious reason. They’re cheap, fast to install, and marketed as a complete fix. No developer, no redesign, no waiting.

The trouble is that most of these tools work by scanning and adjusting a site from the outside, on top of code that wasn’t built with accessibility in mind to begin with. They can add some surface-level features — resizing text, adjusting contrast — but they generally can’t fix the underlying structure of a page: things like whether headings are actually organized logically, whether a form can be completed with a keyboard alone, or whether an image has meaningful alt text instead of none at all. A screen reader user often runs into the exact same barriers whether the widget is turned on or not.

That’s the disconnect this month’s data is pointing at. Installing a widget can feel like checking a box, but it doesn’t change what’s actually happening under the hood. And apparently, it isn’t stopping lawsuits either.

Reform is coming, eventually, but it’s not a fix either

There’s a bill in Congress right now — the Protecting Small Business from Predatory Website Lawsuits Act — that would require a plaintiff to notify a business and give it a chance to fix an accessibility issue before suing. It’s a “fix first, litigate later” approach, and it would genuinely help slow down the kind of drive-by lawsuits that have pushed filings from under 200 a year in 2016 to over 4,000 last year. It’s still sitting in committee, with no timeline for a vote.

Even if it passes, it wouldn’t change what actually makes a website accessible. A notice-and-cure period just changes how much warning you’d get before being asked to fix the same underlying problem a widget was never going to fix in the first place.

Why we build it in instead of bolting it on

This is really the same conversation we have about every part of a website. A widget is a patch applied after the fact. Real accessibility comes from decisions made while a site is actually being built: proper heading structure, forms and navigation that work without a mouse, images with real alt text, color choices that hold up to contrast standards. It’s slower to set up than pasting in a script, but it’s the difference between a site that’s actually usable and one that just looks like it tried.

While we’re on the subject of things we keep an eye on

Small, related note for anyone on WordPress: version 7.1.1 lands this Thursday, September 17. It’s a maintenance release — bug fixes only, not a security patch — cleaning up issues that showed up after 7.1’s launch. Nothing to worry about on your end. We just wanted to mention it, because keeping an eye on core updates like this (and making sure they don’t quietly break something on a client’s site) is part of what “we’ve got this handled” actually looks like day to day, not just at launch.

---

Suggested slug: /blog/accessibility-widget-ada-lawsuit-stat Suggested meta description: New data shows a third of businesses hit with ADA website lawsuits in August had already installed an accessibility widget. Here’s why that happens, and what actually holds up. Internal link: tie “written before about the rise in these lawsuits” back to the earlier accessibility post once it’s live on the site.