Accessibility overlays — the one-line JavaScript widgets that promise instant WCAG compliance — remain one of the most oversold products on the web. The disability community, courts, and the FTC have all pushed back. Here's what the record actually shows.
Overlays don't fix the underlying code
An overlay is a script that runs in the browser after your page loads. It can add ARIA attributes, adjust contrast, and toggle a screen-reader menu, but it cannot rewrite a broken form, restructure a table, or add meaningful alt text where none exists. The source markup still fails WCAG.
WebAIM's analysis of the top one million home pages found sites using overlays had roughly the same average number of detectable errors as sites without them.
The lawsuits kept coming
Plaintiffs' firms have specifically targeted overlay users. In multiple filings, complaints named both the business and the overlay vendor, arguing that the widget itself created new barriers — capturing focus, injecting inaccessible menus, or interfering with the user's own screen reader. Being sued while paying a vendor for "compliance" is a bad look in front of a judge.
The disability community's position
The National Federation of the Blind has formally condemned overlay products. Screen-reader users routinely report that overlays make sites harder to use, not easier, and many browse with them disabled or blocked entirely.
What actually works
Real remediation is code-level: semantic HTML, proper labels, keyboard operability, sufficient contrast, and testing with assistive technology. It's slower than pasting a script tag, but it holds up in court and — more importantly — in front of real users.
Want a real report instead of a band-aid? Request your free audit.