All resources
ArticleApr 2026·6 min read·By enabl team
Accessibility overlays: why the shortcut backfires
Overlay widgets promise instant compliance for a monthly fee. Here's why hundreds of overlay-using sites still get sued — and what to do instead.
Accessibility overlays — the floating icons that promise to make your site "WCAG compliant" by injecting JavaScript — have been a multi-billion-dollar pitch to founders and marketers since 2018. The pitch is appealing: pay a subscription, paste a script, you're done.
The reality, in court records and user research, is more complicated.
What overlays actually do
- Inject a widget letting users adjust font size, contrast, spacing.
- Run automated remediations: try to guess missing alt text, infer ARIA roles, fix contrast.
- Provide a separate "accessibility profile" UI on top of your existing site.
Why they don't deliver compliance
- 01Automated remediation can't reliably detect intent. A button with a meaningless icon doesn't get a meaningful label from a script.
- 02Overlays often interfere with native screen readers, causing duplicate announcements, focus traps, or worse — making the experience less accessible.
- 03Accessible Canada Act, AODA, and ADA case law evaluate the underlying experience. "We installed a widget" is not a defense.
- 04The disability community has been near-unanimous against overlays. Several major overlay vendors have been the subject of class actions themselves.
What works instead
- Conformance audit by humans against WCAG 2.2 AA
- Code-level remediation in your real components
- Design-system patches so new work doesn't regress
- An accessibility statement with a real contact channel
The boring path is also the cheaper one over a 24-month horizon. We've never had a client regret choosing it.