The pitch, and the physics
The overlay pitch is genuinely attractive: paste one script tag, pay a monthly fee, and an AI makes your website compliant — no developers, no rebuild. For a practice owner with no technical staff, that sounds like exactly the right product.
The problem is where accessibility actually lives. A screen reader reads your HTML: the alt attributes on your images, the labels bound to your form fields, the semantic structure of your headings, the keyboard behavior of your menus. WCAG measures those same things. An overlay runs after all of that is already broken and tries to guess at repairs in the visitor’s browser — guessing what your before/after photos depict, guessing what an unlabeled input is for. When the guesses are wrong, and they routinely are, the result is a site that is differently broken, sometimes worse: many blind users report overlays interfering with the screen-reader configurations they already have.
What the record shows
| Evidence | What happened |
|---|---|
| FTC v. accessiBe (Jan 2025) | FTC ordered the largest overlay vendor to pay $1M and barred claims that its widget makes sites fully WCAG-compliant automatically — the compliance promise itself was found deceptive |
| Lawsuit tracker data, year after year | Hundreds of companies with overlays already installed are named in web accessibility suits annually — the widget did not remove them from target lists |
| Complaints citing the overlay itself | Some filings now list the widget as an additional access barrier, not a mitigation |
| The assistive-technology community | Hundreds of accessibility practitioners and screen-reader users have publicly signed statements urging businesses not to rely on overlays |
The tell: scanners still see everything
Here is the test that settles it. Run any standard accessibility engine — axe-core, Lighthouse, WAVE — against a site with an overlay installed. The violations are still there: the scanner reads the same DOM a screen reader does, and the underlying failures the overlay claims to handle show up in the report. Plaintiff-side firms use exactly this class of tooling to build target lists, which is why an overlay subscription and a demand letter are not mutually exclusive — they are frequently line items in the same practice’s ledger.
What to do instead
Fix the code. It is less convenient than a script tag and it is the only thing that changes what scanners, regulators, and actual patients with disabilities encounter. The path is short to describe: audit to inventory the violations, remediate them at the template and page level, keep the dated records, and re-scan as the site evolves. For most dental sites the violations cluster in a dozen recurring patterns — this is weeks of focused work, not a rebuild. And unlike a widget subscription, remediation is an asset you own: cancel an overlay and its promises vanish with it; fixed code stays fixed.