Why Accessibility Overlays Don't Make You ADA Compliant

Accessibility overlay widgets — products like accessiBe, UserWay, AudioEye, and similar tools that promise one-line-of-code ADA compliance — have become one of the most controversial topics in web accessibility. The evidence against their effectiveness is now overwhelming.

In 2024, the FTC fined accessiBe $1 million for deceptive marketing practices, specifically for claiming their AI-powered overlay could make websites ADA compliant. The FTC found these claims were false and misleading, as the overlay failed to detect or fix many common accessibility barriers.

Court rulings have consistently rejected overlays as adequate compliance measures. In Murphy v. Eyebobs (2023), the court specifically noted that the defendant's use of an overlay widget did not constitute a good-faith effort toward compliance. Sites using overlays have been successfully sued just as frequently as sites without them.

The technical limitations are fundamental. Overlays operate at the presentation layer — they can modify how content appears but cannot fix structural issues like missing semantic HTML, improper heading hierarchy, or inaccessible custom JavaScript widgets. An overlay cannot make a custom React dropdown accessible if the underlying component doesn't support keyboard navigation.

The disability community has spoken clearly. The Overlay Fact Sheet (overlayfactsheet.com), signed by over 700 accessibility professionals and advocates, explicitly states that overlays do not provide adequate accessibility remediation and can introduce new barriers.

Over 1,000 websites with overlay widgets installed were sued for ADA violations in 2024 alone. The overlay did not prevent litigation and was not accepted as evidence of compliance.

Real accessibility requires structural changes: semantic HTML, proper ARIA usage, keyboard event handlers, screen reader testing, and genuine human evaluation. There are no shortcuts.