Why overlay widgets don't end ADA website lawsuits
If your business was just sued over its website, someone will offer you a one-line fix within the week: an accessibility overlay — a JavaScript widget that promises instant compliance for a subscription fee. It is worth understanding, before you renew or buy one, why businesses running overlays get sued anyway, and why settlement agreements don't accept them.
What an overlay actually is
An overlay is a script that sits on top of your site and offers a panel of adjustments — font size, contrast modes, a built-in reader — and attempts automated repairs of the underlying code at page load: guessing image descriptions, guessing form labels, injecting ARIA attributes.
The problem is the word "guessing." Screen-reader users already have fonts, contrast, and reading handled by their own software; what they need is for your site's actual code to be correct — real text alternatives, real labels, real heading structure, real keyboard access. An overlay cannot reliably supply what the code never contained, and its injected guesses often conflict with the assistive software users actually run. The largest annual survey of screen-reader users, run by WebAIM, has repeatedly found that a majority of respondents rate these widgets as unhelpful or actively in the way.
What the litigation record shows
Hundreds of businesses with an overlay installed have been sued anyway — overlay-equipped sites are named in new ADA filings every month, and some complaints now cite the overlay itself as evidence the defendant knew about accessibility and chose a cosmetic fix. Plaintiff's experts test the underlying code with the same tools blind users rely on, not the widget's panel. If the code fails, the overlay is irrelevant to their report.
The practical test is simple: turn the widget off and run the site with a screen reader. That is exactly what the plaintiff's expert will do.
What settlements actually require
ADA website cases overwhelmingly end in settlement, and the agreements follow a pattern: bring the site into conformance with WCAG 2.1 AA (the Web Content Accessibility Guidelines) by a deadline, maintain it, and often retest on a schedule. WCAG conformance is a property of your site's code and content. No settlement I'm aware of has accepted "we subscribed to a widget" as satisfying that obligation — and defendants who try to argue it tend to pay for remediation twice: once for the overlay, then again for the real work.
What real remediation looks like
Code-level work in your actual theme or templates: text alternatives written for your real images; labels tied to your real form fields; heading structure that matches the page; focus order and visible focus states; keyboard operability for menus, carousels, and cart drawers; accessible names on buttons and iframes; color contrast fixed in the stylesheet. Then a retest, and documentation mapping each fix to the WCAG criterion it satisfies — the artifact your attorney can actually use.
That's the work I do, at a fixed price, in about a week for most storefronts. The scope is public: what the remediation includes. If you were just sued and want to understand your own case first, start here: how to read your docket in ten minutes.