Why Accessibility Overlays Don’t Make You Compliant

If you’ve searched for “website accessibility quick fix,” you’ve probably found an overlay product. AccessiBe, UserWay, AudioEye, and similar tools promise to make your site accessible by adding a toolbar widget. They show up in countless ads: “Make your site accessible in minutes.” “Automatic AI-powered compliance.” “Instant WCAG 2.2 Level AA.”

None of these claims are true. And worse, overlays often make accessibility worse — not better.

Here’s the reality, the research behind it, and what actually works.

Myth 1: “An Overlay Makes Your Site Accessible”

Reality: An overlay doesn’t fix your code. It attempts to patch issues at the browser level, after the page has loaded. This approach has fundamental limitations.

An overlay can’t fix underlying code problems. If your images have no alt text, an overlay might generate alt text automatically (often poorly). But the underlying HTML is still broken. If a custom JavaScript menu only responds to mouse clicks, an overlay can’t add keyboard support — that requires fixing the code itself. If form fields have no labels, an overlay can’t create labels that screen readers will recognise.

Research confirms this. The WebAIM Million study (annual analysis of the top 1 million websites) found that overlays are common on high-traffic sites, yet those sites still fail most accessibility checks. Overlays give the appearance of accessibility without fixing the underlying problems.

Worse, overlays can actively break accessibility. Screen reader users often turn overlays off because they interfere with their assistive technology. A blind user with a screen reader might encounter an overlay that adds extra navigation, confuses focus order, or inserts noise into the reading experience.

What to do instead: Fix the underlying code. Add alt text to images, label form fields properly, ensure keyboard navigation works, fix colour contrast. These are real solutions that work for everyone, not just users with overlays installed.

Myth 2: “Overlays Provide Legal Protection”

Reality: Overlays do not provide legal protection against accessibility lawsuits. In fact, relying on an overlay might strengthen a claimant’s case that you haven’t made genuine reasonable adjustments.

Under the UK Equality Act 2010, you have a legal duty to make reasonable adjustments for disabled people. An overlay is not a reasonable adjustment — it’s a workaround that doesn’t actually fix the underlying barriers.

If a disabled person experiences a barrier on your website and brings a claim, citing “we have an overlay” is not a credible defence. It signals that you were aware of accessibility requirements but chose a superficial solution rather than actually fixing the problem.

Several US court cases have rejected overlay-based defences. Courts have recognised that overlays don’t provide equivalent access and don’t constitute genuine compliance with accessibility obligations.

The European Accessibility Act also requires WCAG 2.2 Level AA compliance — not overlay compliance. An overlay is unlikely to help you meet that standard.

What to do instead: Make genuine code changes that fix accessibility barriers. This is your actual legal obligation.

Myth 3: “Overlays Are Better Than Nothing”

Reality: Overlays can be worse than nothing. For many disabled users, overlays make the site harder to use.

The National Federation of the Blind issued a formal statement opposing accessibility overlays. Their core finding: overlays often introduce new barriers, interfere with real assistive technology, and create confusion rather than access.

Specific problems:

• Screen reader interference: Overlays add extra navigation and content that screen readers announce, cluttering the experience and making it harder for blind users to navigate the site
• Focus management issues: Overlays can trap keyboard focus or move focus unexpectedly, making keyboard navigation worse
• Custom widget problems: Overlays can’t fix broken custom JavaScript widgets — they just add another layer of broken code
• Mobile issues: Overlays are often ineffective on mobile devices, where accessibility is increasingly important
• Cognitive load: Users with cognitive disabilities may be confused by the overlay interface itself

A disabled user encountering an overlay might think “this site is trying to be accessible but doing it poorly” rather than “this site is accessible.” The frustration factor is real.

What to do instead: Build accessibility into your site from the start. Fix the code. Test with real assistive technologies. Real accessibility is better than a superficial overlay.

Myth 4: “Overlays Are Cheap and Easy”

Reality: Overlays are cheap upfront but expensive in the long run. And they create a false sense of security that prevents real fixes.

Yes, you can add an overlay widget for £30–300/month. But:

• You still haven’t fixed your site. After you cancel the overlay, your site is still inaccessible. You’ve paid for months or years of fake compliance.
• Real accessibility is often cheaper. The most common failures (alt text, colour contrast, form labels, heading structure) are quick to fix and cost very little. Real accessibility is often more cost-effective than overlays.
• Overlays don’t improve your core product. An accessible site is a better site — faster on mobile, better SEO, better usability for all users. An overlay doesn’t provide these benefits.
• You’ve signalled you’re not taking accessibility seriously. Using an overlay instead of fixing code tells disabled users (and courts) that you see accessibility as a compliance checkbox, not a product obligation.

What to do instead: Invest in real accessibility. It’s often cheaper and always more effective.

Myth 5: “We Use an Overlay So We’re Compliant With WCAG”

Reality: WCAG compliance is based on whether your site actually meets WCAG criteria, not whether you’ve added an overlay. An inaccessible site with an overlay is still inaccessible.

WCAG 2.2 Level AA success criteria are testable against your actual code and user experience. Automated testing tools like axe-core, Lighthouse, and WAVE don’t care if you have an overlay — they test whether your underlying code is accessible. An overlay that hides those failures from its own tests is just masking the problem, not solving it.

And manual testing (the part that catches 50–70% of issues) will reveal that your site is still inaccessible, overlay or not.

What to do instead: Run automated tests and manual testing. Fix the actual failures. Test with real assistive technologies. That’s how you achieve real WCAG compliance.

What Actually Works

If you want to make your site accessible, do this:

1. Run an automated accessibility scan. Use axe-core, Lighthouse, WAVE, or similar. This catches 30–50% of issues and gives you a concrete starting list.

2. Fix the high-impact issues first. Colour contrast, alt text, form labels, and heading structure account for most automated failures.

3. Conduct manual testing. Use a screen reader. Test keyboard navigation. Test with real users with disabilities. This reveals the issues automation can’t catch.

4. Fix custom widgets and navigation patterns. Custom JavaScript, complex menus, and interactive elements often need specific code changes to be keyboard-accessible and screen-reader-compatible.

5. Test across different assistive technologies. Different screen readers, browsers, and devices have different behaviours. Test with at least NVDA (free, Windows) and JAWS (paid, industry standard).

6. Maintain accessibility. When you update your site, maintain accessibility standards. New features should be built accessibly from the start.

This approach takes more upfront effort than an overlay, but it solves the actual problem. And the result is a better site for everyone.

The Disability Advocate Perspective

It’s worth understanding why disability advocates strongly oppose overlays. For disabled users, overlays are often insulting. They signal: “We know we have a problem, we just don’t want to fix it properly. We’re buying a widget instead.”

An accessible site — one where the underlying code works properly with assistive technology — is fast, usable, and respectful. An overlay-augmented inaccessible site is slow, often non-functional, and feels like an afterthought.

If you’re genuinely committed to accessibility, it shows. If you’re not, disabled users know it.

The Bottom Line

Accessibility overlays don’t provide legal protection, don’t make your site compliant, and often make the experience worse for disabled users.

What works is fixing the underlying code. Adding alt text, fixing colour contrast, labelling form fields, ensuring keyboard navigation, and testing with real assistive technologies. This is what the Equality Act requires. It’s what WCAG 2.2 Level AA means. And it’s what disabled users actually need.

If you need help identifying what to fix and prioritising remediation, Bartram Web screens your website and delivers a concrete action plan. Our screening tells you what’s broken so you can fix it — no overlays, no shortcuts, no false promises.

For more on what actually matters for accessibility, see Common Accessibility Failures and WCAG 2.2 explained.