The Accessibility Overlay Debate: What Actually Works?

# The Accessibility Overlay Debate: What Actually Works?

Few topics in the web accessibility community generate as much heated debate as accessibility overlays. These JavaScript-based tools promise to make websites accessible with a single line of code, and they have been adopted by a large number of websites worldwide. Yet accessibility professionals, disability advocates, and an increasing number of legal experts argue that overlays not only fail to deliver on their promises but can actually make the experience worse for the people they claim to help.

This article examines the overlay debate from all sides: what overlays are, why they became popular, the criticisms and evidence against them, what the disability community has to say, the legal landscape, and what genuinely works for achieving web accessibility.

What Are Accessibility Overlays?

Accessibility overlays (sometimes called accessibility widgets or toolbar plugins) are third-party JavaScript tools that are added to a website to modify its appearance and behavior for users who activate them. They typically appear as a small icon (often featuring a wheelchair or accessibility symbol) in the corner of a webpage.

When a user clicks the overlay icon, a panel opens offering options such as:

• Increasing or decreasing text size
• Changing color contrast or switching to a dark mode
• Highlighting links or headings
• Adjusting font spacing or style
• Pausing animations
• Enabling a screen reader mode

Some overlay vendors have gone further, claiming that their products use artificial intelligence to automatically detect and fix accessibility issues in the page's code in real time, without the website owner needing to make any changes to their actual HTML, CSS, or JavaScript.

Why Overlays Became Popular

The appeal of overlays is easy to understand:

Speed: Installation takes minutes. Add a single script tag, and the overlay appears on every page.

Cost: An overlay subscription usually costs far less up front than a comprehensive accessibility audit and remediation project.

Marketing claims: Overlay vendors have invested heavily in marketing that promises ADA compliance, lawsuit protection, and WCAG conformance through their product alone.

Fear of litigation: As accessibility lawsuits increased, businesses scrambled for quick solutions. Overlays positioned themselves as the fastest path to compliance.

Complexity avoidance: Genuine accessibility work requires understanding WCAG, modifying code, testing with assistive technologies, and maintaining compliance over time. Overlays promise to eliminate that complexity.

For a business owner facing the threat of a lawsuit and lacking in-house accessibility expertise, the overlay pitch is compelling. Unfortunately, the reality does not match the marketing.

The Criticisms: Why Overlays Do Not Work

They Do Not Fix the Underlying Code

This is the fundamental problem. Assistive technologies like screen readers interact with a website's HTML structure, ARIA attributes, and semantic markup. An overlay that changes visual presentation does not change what a screen reader "sees."

For example, if an image is missing alt text, the overlay cannot determine what the image depicts and add a meaningful description. If a form field lacks a proper label, the overlay cannot infer the label's content. If a custom widget lacks keyboard support, the overlay cannot make it keyboard-accessible without rewriting the widget's code.

The overlay operates on top of the existing page. The existing page, with all its accessibility issues, remains the foundation.

Many Barriers Need Human Judgment

Much of accessibility depends on meaning, not markup. Whether alt text actually describes an image, whether a heading structure reflects the content, whether an error message tells a user how to fix a mistake: these require a person who understands the content. A script running in the visitor's browser cannot make those judgments reliably, which is why overlays can only ever address a narrow subset of issues. The same limit applies to automated scanners, including ours, which is why automated results should always be paired with manual testing.

They Can Make Things Worse

Paradoxically, overlays sometimes create new barriers:

• Keyboard traps: Some overlays introduce focus management issues that trap keyboard users within the overlay panel.
• Screen reader conflicts: Overlay scripts can conflict with screen reader software, causing unexpected behavior, repeated content, or broken navigation.
• Performance impact: The additional JavaScript payload can slow page load times, affecting users on older devices or slower connections, including many people with disabilities.
• Unwanted modifications: Some overlays automatically alter the page for users of assistive technologies without their consent, overriding their own carefully configured settings and preferences.

They Create a Separate, Inferior Experience

Even when overlay features work as intended, they create a segregated experience. Users with disabilities must find and activate the overlay, learn its interface, and configure their preferences on every site that uses one. Meanwhile, users without disabilities experience the site as designed.

This "separate but equal" approach contradicts the core philosophy of web accessibility, which holds that the same content and functionality should be available to everyone through the same interface.

What the Disability Community Says

The disability community has been vocal and consistent in its opposition to overlays. The most notable collective statement is the Overlay Fact Sheet (overlayfactsheet.com), which has been signed by hundreds of accessibility professionals, disability advocates, and organizations. Its central point is that overlays do not make a website accessible and should not be relied on for compliance. Read the full statement and signatory list at the source.

Individual voices from the disability community reinforce this position:

• Screen reader users often report that overlays interfere with their existing tools and settings
• Advocates point out that an extra interface to find and configure adds complexity rather than reducing it
• The National Federation of the Blind has publicly criticized overlay marketing

The message from the people these products claim to serve is clear: overlays are not welcome and do not help.

Legal Precedent

The legal picture has not been favorable for businesses relying on overlays:

Overlays Do Not Prevent Lawsuits

Businesses with overlays installed have been sued, and plaintiffs have tested sites with the overlay enabled to show that barriers persisted. An overlay is not accepted evidence of ADA compliance.

Regulators Have Taken Notice

In January 2025, the U.S. Federal Trade Commission announced an order requiring overlay vendor accessiBe to pay $1 million over claims that its AI product could make any website compliant with WCAG. The order also bars the company from making such claims without evidence. The message for buyers is simple: be skeptical of any product that promises compliance on its own.

The Canadian View

The AODA and the Accessible Canada Act regulate the accessibility of your website itself. In Ontario, the requirement is that the site conforms to WCAG 2.0 Level AA. A layer added on top of an inaccessible page does not change the code that assistive technologies actually read, so it does not change whether the site conforms.

What Actually Works: Code-Level Accessibility

Genuine web accessibility requires addressing the root causes of barriers in your website's code, content, and design. There are no shortcuts, but the work is straightforward when approached systematically:

Semantic HTML

Use proper HTML elements for their intended purpose. Headings (h1 through h6) should reflect content hierarchy. Lists should use list elements. Buttons should be buttons, not styled divs. Navigation should use nav landmarks. Semantic HTML solves a remarkable number of accessibility issues with no additional effort.

Proper Form Labeling

Every form input needs a programmatically associated label. This means using the <label> element with a for attribute that matches the input's id, or wrapping the input within the label element. Placeholder text is not a substitute for a label.

Text Alternatives

All meaningful images need descriptive alt text. Decorative images need empty alt attributes. Videos need captions. Audio content needs transcripts. Complex images (charts, diagrams) need detailed descriptions.

Keyboard Accessibility

Every interactive element must be reachable and operable with a keyboard alone. Focus order should follow a logical sequence. Focus indicators must be visible. Custom interactive widgets need appropriate keyboard event handlers.

Color and Contrast

Text must have sufficient contrast against its background (4.5:1 for normal text, 3:1 for large text). Color must not be the only means of conveying information.

Testing with Assistive Technologies

Regular testing with screen readers (NVDA, JAWS, VoiceOver), keyboard-only navigation, and other assistive technologies reveals issues that no automated tool or overlay can detect.

Regular Re-testing

Every content update, feature release, and design change can introduce new barriers. Re-running automated scans after changes catches many regressions quickly, while periodic manual testing checks the full user experience.

For guidance on evaluating different tools, see our guide on choosing the right accessibility solution.

How Compliable's Approach Differs

Compliable exists because we believe accessibility should be real, not performative. Our approach is built on the principles that the accessibility community has advocated for:

• We point to the source, not the surface. Our free scan renders your page in a real headless Chrome browser on desktop and mobile and tests it with the open-source axe-core engine, so findings point to the actual elements in your page that need fixing.
• We combine automated and human testing. Automated scanning detects only part of all barriers. Our expert audits add manual testing to cover what automation cannot.
• We prioritize by severity. Not all accessibility issues are equal. Findings are scored so your team can focus on the barriers that matter most first.
• We map findings to the rules you follow. Reports are mapped to WCAG, the AODA, the Accessible Canada Act, the ADA and Section 508, giving you a dated record of your progress.
• We are honest about limits. No tool can guarantee compliance, and we never claim to fix your site automatically. Your developers fix the code, with our findings as the guide.

We do not sell a widget. We help you find and fix barriers in the site itself.

Making the Right Choice

If you are currently using an overlay or considering one, here is practical guidance:

1. Do not rely on an overlay as your compliance strategy. It will not protect you from lawsuits, and it will not make your site genuinely accessible.
2. An overlay can coexist with real remediation work, but it should not be the primary effort. If you choose to keep an overlay for its user preference features (text sizing, contrast controls), treat it as a minor convenience, not a compliance solution.
3. Invest in understanding your actual accessibility gaps. A proper audit will reveal the real issues. Many of them are simpler and cheaper to fix than you might expect.
4. Budget for ongoing compliance. A one-time overlay subscription does not address the ongoing nature of accessibility. Build accessibility into your development and content processes.

Conclusion

The accessibility overlay debate is not really a debate among those who understand accessibility. The evidence is clear: overlays do not fix the underlying issues that make websites inaccessible. The disability community has spoken clearly against them. Businesses using them are still being sued, and regulators have acted against misleading compliance claims. At best they address a fraction of accessibility barriers, and they sometimes create new ones.

Genuine accessibility requires genuine work: fixing code, testing with assistive technologies, and maintaining compliance over time. It is more effort than installing a script, but it is the only approach that actually serves users with disabilities, meets legal requirements, and protects your business.

Ready to move beyond overlays and toward real accessibility? Start your free scan with Compliable and see the detectable issues in your site's actual code.