38.5% of Sued Websites Already Had an Overlay Widget Installed
A procurement officer asked us last month why we don't just sell a widget. Cheaper, faster to install, one line of JavaScript. Here's the honest answer, backed by two 2026 lawsuits and a litigation report that did the math nobody wanted to do.
An accessibility overlay is a snippet of JavaScript that drops onto an existing site and promises to patch accessibility problems at runtime: resizing text, adjusting contrast, narrating content. No developer time. No rebuild. The pitch is seductive precisely because it sounds like it shouldn't work, and for the last three years, the data has backed that instinct up.
1The Number That Should Worry Every Procurement Officer
AudioEye's 2026 litigation report found that 38.5% of businesses sued for inaccessibility in 2025 already had some accessibility solution installed. Usually an overlay. Read that twice. These weren't sites that ignored accessibility. They'd bought something, installed it, and told their board the problem was handled.
It wasn't handled. The underlying markup never changed. The widget sat on top of broken HTML, hiding the problem from a sighted person glancing at the page while leaving it fully intact for the screen reader user trying to navigate it.
2Two Companies, Two Very Different 2026s
accessiBe: $1.2 million, plus an FTC order with teeth
A class action against accessiBe settled for $1.2 million, with claims paying out through 2026. Separately, the FTC finalized its own $1 million settlement over deceptive compliance claims. The order bars accessiBe from claiming its widget makes a site WCAG-compliant without evidence, and it stays in force for 20 years. Twenty. Not two.
UserWay: the key claims survive
A small online florist sued UserWay over similar claims. A year in, a magistrate judge recommended the core of the case move forward rather than get dismissed. A dermatology practice brought nearly identical claims against accessiBe before that. Different plaintiffs, different vendors, same pattern.
3Why the Fix Doesn't Actually Fix Anything
An overlay runs in the browser, after the page has already loaded, guessing at structure it was never given. It can't write alt text that reflects what a chart actually shows. It can't know a table's header row from a glance at the DOM. It can't fix a form that was built with placeholder text instead of real labels, because the label never existed in the markup to begin with.
Compare that to fixing the HTML directly. A real label tag. A real heading hierarchy. Alt text a person wrote and reviewed. None of that disappears if the JavaScript fails to load, which, by the way, overlay scripts do, regularly, on slow connections or when a browser extension blocks third-party scripts. A resident on a government network with aggressive content filtering might never see the widget at all. The underlying page is still what they get.
4Where This Hits Government Specifically
Private-sector lawsuits run through state courts mostly, under Title III. Government sites answer to Title II, a different statute, but the same WCAG 2.1 AA standard and the same DOJ that just finished telling a private company its settlement website wasn't accessible either (more on that one separately). A government procurement file that says "we installed an accessibility widget" reads, to an auditor, exactly like the sentence that preceded 38.5% of last year's lawsuits.
5Read the Contract, Not Just the Pitch
The sales conversation and the contract language rarely match. A demo shows a floating icon that resizes text and reads a page aloud, framed as compliance in a box. The actual terms of service, the ones a procurement officer should be reading line by line, usually include a disclaimer that the vendor doesn't guarantee WCAG conformance and that the customer remains responsible for accessibility obligations under applicable law.
That clause exists precisely because vendors know what the FTC order against accessiBe just confirmed in public: an unsupported compliance claim is a liability, not a selling point. A government agency that signs a contract with that disclaimer in it, while telling its own council or board that accessibility is handled, is holding paper that says the opposite of what it just told its oversight body.
6Why the Scan Can Still Come Back Green
Here's a detail that trips up a lot of well-intentioned IT teams. Some overlays inject ARIA attributes and alt-text placeholders into the live DOM at runtime, after the underlying page loads. An automated scanner that checks the rendered page, rather than the original markup, can register those injected attributes as present and report a cleaner result than the site actually earns.
That's a false negative baked into the measurement, not the fix. A screen reader user interacting with the real document structure, or a manual auditor reading source code instead of rendered output, finds the same missing labels and broken headings that were always there. A green automated score next to an overlay installed on top of unfixed markup is worth checking twice before anyone reports it up the chain as evidence of compliance.
7What to Check If You Already Have One
- Disable JavaScript and reload the page. If it's unusable, that's what a meaningful share of your actual visitors experience.
- Pull up the page source and look for actual alt attributes on images, not a widget script tag.
- Ask the vendor for a written, signed conformance claim. If they won't put it in writing, that tells you something.
Final Takeaway
The lawsuit data isn't subtle. Installing a widget and calling it done doesn't reduce legal exposure, it just delays the complaint. Fixing the markup is slower to set up and faster to defend. For government sites heading into the 2027 and 2028 Title II deadlines, slower-but-defensible is the only version worth building.
See what a structural fix actually looks like
Our WordPress and Drupal modules fix alt text, contrast, and form labels in the real markup, not a floating widget. See the difference on a 20-minute call.
Schedule a Free Demo