Are accessibility overlays a good solution?

No. Accessibility overlays fail to fix the majority of real accessibility issues and are actively opposed by disability advocacy organizations. Over 400 accessibility professionals signed an open letter against them. They create legal liability, not protection.

What accessibility overlays claim to do

Overlay widgets — products like AccessiBe, UserWay, AudioEye, and others — are JavaScript snippets that load a toolbar allowing users to adjust visual settings (text size, contrast, cursor size) and claim to automatically remediate accessibility issues in the page code.

The pitch is appealing: install one line of code, get accessibility compliance. Prices range from £500-5,000/year. Vendors often imply — and sometimes explicitly claim — that their overlay provides ADA or WCAG compliance.

None of them do.

Why overlays don’t work

Automated remediation misses the majority of issues. Independent testing by accessibility specialists consistently shows that overlays address surface-level issues (adding some ARIA labels, adjusting some contrast values) but miss the structural problems that matter most to disabled users: broken keyboard navigation flows, inaccessible custom components (date pickers, modals, carousels), missing form associations, and complex interaction patterns that screen readers can’t interpret.

Axe accessibility engine testing typically shows overlays passing 30-40% of automated checks while failing 60-70% of manual checks that reflect real user experience.

Overlays conflict with assistive technologies. Screen readers like JAWS, NVDA, and VoiceOver apply their own interpretation to page code. When an overlay injects modified ARIA attributes and additional DOM elements, it creates conflicts that actively break the screen reader experience. The overlay makes the site worse for the users it claims to serve.

The underlying code remains broken. An overlay sits on top of your code without changing it. If a form field has no associated label, the overlay might add an ARIA label — but the next time you update the form in your CMS, the ARIA label is gone or wrong. The fix is cosmetic and fragile.

The legal reality

Multiple lawsuits have been filed against companies using overlays where the overlay was cited as evidence of compliance. Courts have consistently held that an overlay does not constitute accessibility compliance. In some cases, the overlay’s presence was used to demonstrate that the company knew about the problem and applied a cosmetic fix rather than a real one.

The overlay vendors typically respond to lawsuits involving their customers by stating that customers must also implement underlying code fixes — which undermines the entire premise of the product.

What disabled users say

The clearest evidence against overlays comes from the users they claim to help. The #AccessiBe controversy in 2021 saw disability advocates, screen reader users, and accessibility professionals publicly document how overlay widgets degraded their experience. Many users add overlay domains to blocklists or use browser extensions to suppress them.

The overlay industry’s response — that a vocal minority is opposed to their products — has been refuted by research showing that screen reader users specifically report worse experiences on overlay-equipped sites compared to sites without overlays.

What to do instead

Real accessibility improvement requires real code changes. The process is:

1. Audit: Use automated tools (axe, WAVE) plus manual testing with keyboard and screen reader
2. Prioritize: Fix the critical path — navigation, product pages, checkout — before addressing edge cases
3. Implement: Developer time to fix structural HTML, ARIA usage, keyboard interactions, and form associations
4. Test: Verify with assistive technology, not just automated tools
5. Maintain: Include accessibility in your QA process for all future development

The cost of proper accessibility remediation for a typical e-commerce site is £3,000-15,000 depending on the size of the codebase and the severity of existing issues. This is a one-time cost (with ongoing maintenance) versus annual overlay subscriptions that provide no actual compliance.

A UX audit includes accessibility evaluation and gives you a prioritized remediation plan with specific code-level recommendations.