Website Accessibility Overlays vs. Real Compliance

You've probably seen the ads. "Make your website accessible with one line of code." Companies like AccessiBe, UserWay and AudioEye sell overlay widgets that promise to fix accessibility problems automatically. The pitch is appealing: drop a JavaScript snippet on your site and you're WCAG compliant.

It doesn't work that way. And choosing an overlay over real fixes can actually make things worse.

What accessibility overlays are

An overlay is a JavaScript widget that loads on top of your existing website. It typically adds a small icon in the corner of the page. When visitors click it, they get options like increasing text size, changing contrast, highlighting links or enabling a screen reader mode.

Some overlays also claim to use AI to fix underlying code problems automatically. They say they can detect missing alt text, fix heading structures and add ARIA labels without you touching your code.

The products sound different but work similarly. AccessiBe, UserWay, AudioEye, EqualWeb and others all follow this basic approach.

Why overlays don't fix accessibility

The problems with overlays fall into a few categories.

They can't fix structural HTML issues

If your website has a broken heading hierarchy, missing form labels, inaccessible navigation or keyboard traps, an overlay can't fix these. These are problems in your HTML structure. An overlay sits on top of your site like a coat of paint on a crumbling wall.

A screen reader needs proper HTML semantics to work. If a button is coded as a <div> instead of a <button>, no overlay can make it behave correctly for keyboard users. If your form fields don't have associated <label> elements, an overlay can guess what the labels should be, but it often guesses wrong.

They break screen readers

This is the ironic part. Overlays designed to help screen reader users often interfere with how screen readers work.

Screen readers like JAWS, NVDA and VoiceOver have their own settings for text size, contrast and navigation. When an overlay adds its own layer of modifications, it conflicts with these settings. Users who already have their screen reader configured the way they need it suddenly find that the overlay is overriding their preferences.

The National Federation of the Blind issued a statement about AccessiBe specifically, describing their experience as users being "held hostage" by the overlay. Multiple accessibility professionals have documented cases where overlays made sites less usable, not more.

They create new problems

Overlays inject JavaScript that can:

• Slow down page loading
• Conflict with other scripts on your site
• Change the visual layout in unexpected ways
• Add ARIA attributes incorrectly, which confuses assistive technology more than having no ARIA at all
• Break on mobile devices or in certain browsers

Incorrect ARIA is worse than no ARIA. If an overlay labels a navigation menu as a "button" or marks a decorative image as meaningful content, screen readers relay that wrong information to the user.

They don't cover all WCAG criteria

WCAG 2.1 AA has 50 success criteria. Overlays can theoretically address a handful of them, mostly related to text size and color contrast. They cannot address criteria related to keyboard navigation, focus management, error handling, time-based media, content structure or cognitive accessibility.

An overlay might cover 10% to 20% of WCAG requirements. The remaining 80% to 90% require changes to your actual HTML, CSS and JavaScript.

The Overlay Fact Sheet

In 2021, a group of accessibility professionals published the Overlay Fact Sheet at overlayfactsheet.com. It has been signed by over 700 accessibility practitioners, researchers and advocates.

The fact sheet states clearly: "overlays do not and cannot provide sufficient accessibility." It documents the technical limitations, the false marketing claims and the harm these products cause to disabled users.

Among the signatories are people who have spent decades working in accessibility, including members of the W3C working groups that write the WCAG standards. This isn't a fringe opinion. It's the professional consensus.

Real lawsuits against overlay users

Here is the part that should make business owners pay attention. Companies that installed overlays have been sued for accessibility violations. The overlay did not protect them.

UsableNet's 2023 report documented that companies using accessibility overlays were defendants in over 800 accessibility lawsuits in the US. Having an overlay installed did not prevent the lawsuit and was not accepted as a defense.

Murphy v. Eyebobs LLC is one example. The company had AccessiBe installed. They were still sued under the ADA, and the overlay was not considered sufficient compliance.

While most of these cases are from the US, the European Accessibility Act makes this relevant for EU businesses too. The EAA became enforceable in June 2025, and it requires websites to meet EN 301 549, which aligns with WCAG 2.1 AA. An overlay won't satisfy those requirements for the same reasons it doesn't satisfy ADA requirements.

If you want to understand the EAA requirements, read our guide on whether the EAA applies to your business.

What actually works

Real accessibility requires real changes to your website. That sounds harder than installing a widget, and it is. But it's the only approach that actually works.

Fix your HTML structure

Start with the basics:

• Use proper heading levels. One <h1> per page, then <h2>, <h3> in order. Don't skip levels.
• Use semantic HTML elements. <nav> for navigation, <button> for buttons, <main> for main content.
• Add <label> elements to every form field, linked with the for attribute.
• Include alt text on informational images. Use empty alt="" for decorative images.

<!-- Bad: div pretending to be a button -->
<div class="btn" onclick="submit()">Send</div>

<!-- Good: actual button element -->
<button type="submit">Send</button>

This single change gives you keyboard support, screen reader announcements and focus styling for free. No overlay needed.

Test with keyboard only

Unplug your mouse and try to use your website with just the keyboard. Tab through the page. Can you reach every interactive element? Can you tell where you are? Can you activate buttons and links? Can you close modal dialogs?

If you get stuck anywhere, that's a real accessibility barrier that no overlay can fix.

Test with a screen reader

NVDA is a free screen reader for Windows. VoiceOver is built into every Mac and iPhone. Turn one on and listen to how your website sounds. You'll quickly discover missing labels, confusing link text and structural problems.

Run an automated scan

Automated tools catch about 30% to 40% of accessibility issues. That's not everything, but it's a solid starting point. Tools like axe DevTools, WAVE and Lighthouse can identify missing alt text, color contrast failures, missing form labels and heading order problems.

Our free website scanner includes accessibility checks based on axe-core and flags the most common WCAG 2.1 AA violations.

Fix the top issues first

You don't need to fix everything at once. Focus on the highest-impact issues:

1. Keyboard navigation. Can people tab through your site?
2. Form labels. Are all form fields properly labeled?
3. Image alt text. Do informational images have descriptions?
4. Color contrast. Is text readable against its background? WCAG requires a 4.5:1 ratio for normal text.
5. Heading structure. Are headings used correctly and in order?

These five areas cover the most common accessibility barriers. Fix them and you've addressed the majority of issues real users encounter.

Write an accessibility statement

An accessibility statement is a page on your site that describes your commitment to accessibility, the standard you're working toward, known limitations and how users can report problems. Under the EAA, this is a requirement for many businesses.

The honest take on overlays

Overlay companies aren't evil. Some of the people working there genuinely want to improve accessibility. But the technology doesn't deliver what the marketing promises.

The problem is that accessibility is a design and development discipline, not a bolt-on feature. It needs to be part of how your site is built, not a layer added after the fact. An overlay that promises otherwise is selling a shortcut that doesn't exist.

If you've already installed an overlay, don't panic. But also don't assume you're compliant. Remove the overlay, run an actual accessibility audit, and start fixing the real issues. It takes more effort, but it's the only path to a website that actually works for everyone.

Common Questions

Are overlays completely useless?

Some overlay features, like high-contrast mode or text resizing, can be helpful for some users. But these features already exist in operating systems and browsers. And they don't make your site legally compliant. The compliance claims are the problem, not every individual feature.

How much does real accessibility work cost?

For a typical small business website with 5 to 15 pages, an accessibility audit and fixes might cost 1,000 to 3,000 euros. For a simple site, you can fix many issues yourself using the steps above. Compare that to overlay subscriptions of 500 euros per year that don't actually solve the problem.

Will removing an overlay make my site less accessible?

In most cases, no. The overlay features that are genuinely useful, like text resizing, are already available through browser settings and operating system accessibility features. Removing the overlay also removes the conflicts it causes with screen readers.

Does the European Accessibility Act mention overlays?

The EAA doesn't mention overlays by name. It requires conformance with EN 301 549, which maps to WCAG 2.1 AA. The standard is about results: does your site meet the criteria or not? An overlay that doesn't achieve conformance is irrelevant to the legal requirement.

Can AI fix accessibility automatically in the future?

AI might get better at detecting and suggesting fixes. But accessibility involves understanding context, intent and user experience in ways that require human judgment. A tool might correctly detect a missing alt text, but writing a good alt text requires understanding what the image communicates. Fully automated accessibility remains a long way off.

---

Check your website now. Scan your site for accessibility issues, missing compliance requirements and more. Free, takes two minutes. Scan your website