Why Accessibility Widgets Keep Losing in Court
You've seen them: the little accessibility icon in the corner of a website. Click it and you get a toolbar — bigger text, higher contrast, screen-reader mode. Companies like accessiBe and UserWay built nine-figure businesses selling these overlays as instant ADA compliance.
Then, in 2025, the FTC fined accessiBe $1 million for deceptive claims about what its product actually does.
What overlays promise vs. what they deliver
The pitch is seductive: paste one line of JavaScript into your site and you're compliant overnight. No code changes, no developer needed.
The problem is architectural. Overlays don't fix your website — they patch it in the visitor's browser, after the page loads. The underlying code still has missing labels, broken structure, and unnamed controls. A screen reader hitting the raw page (which is what actually matters for real users, and what courts look at) still finds the same issues.
Worse, overlays can actively interfere with the assistive technology disabled users already rely on. There are documented cases of overlay toolbars conflicting with screen readers — making the experience worse, not better.
What the courts and regulators actually said
The FTC's action against accessiBe centered on one thing: the company claimed its product could make websites compliant with accessibility standards, and the FTC found those claims deceptive. A million-dollar fine is the regulator spelling it out: no overlay makes a site compliant.
Plaintiff firms know this too. Sites running overlays still get sued — the overlay doesn't change the underlying code the complaint is based on.
What actually works
There's no shortcut, but there's also no mystery:
- Fix the code, not the browser. Missing alt text, unlabeled buttons, unassociated form fields — these are fixed in your HTML, where they stay fixed for every visitor and every assistive device.
- Automate what's safely automatable. The mechanical fixes (language attributes, decorative-image alt text, derived control names, skip links) can be applied automatically and reversibly. That's what EqualFix does — in your page output, not as a browser patch.
- Be honest about the rest. Contrast, structure, and complex widgets need human review. Any vendor who won't say that out loud is waving a red flag.
The takeaway
If a product promises compliance in one click, ask what it changes in your actual code. If the answer is "nothing, it runs in the visitor's browser," you have your answer about what it's worth.
EqualFix fixes accessibility issues in your WordPress site's actual output — not as an overlay. See what it fixes vs. what it flags.