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 hundreds of thousands 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: Overlay subscriptions typically range from $500 to $5,000 per year, far less 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.

Independent Research Confirms Their Limitations

Multiple independent studies have evaluated overlay effectiveness:

• A 2023 study by researchers at the University of Swansea tested leading overlay products against WCAG 2.1 criteria and found that they addressed fewer than 30% of detected accessibility issues.
• The accessibility consulting firm Level Access conducted testing showing that overlays frequently introduced new WCAG violations while attempting to fix existing ones.
• Automated testing by WebAIM found that sites with overlays installed had, on average, more detectable accessibility errors than sites without them.

These are not cherry-picked results. The consistent finding across independent evaluations is that overlays address a narrow subset of accessibility issues while leaving the majority untouched.

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, disproportionately affecting users on older devices or slower connections (who are statistically more likely to be 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. It states:

"Overlay products do not and cannot make a website accessible... They create barriers, violate privacy, and provide a false sense of security."

Individual voices from the disability community reinforce this position:

• Screen reader users frequently report that overlays interfere with their existing tools and settings
• Organizations representing people with cognitive disabilities note that overlay interfaces add complexity rather than reducing it
• The National Federation of the Blind has spoken against overlays, stating that they do not provide meaningful accessibility improvements

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

Legal Precedent

The legal system has increasingly weighed in on overlays, and the results have not been favorable for overlay users:

Overlays Do Not Prevent Lawsuits

Businesses with overlays installed have been sued successfully. The presence of an overlay has not been accepted by any court as evidence of ADA compliance. In multiple cases, plaintiffs have specifically tested websites with overlays enabled and demonstrated that barriers persisted.

Expert Testimony Against Overlays

In several federal cases, accessibility experts have testified that overlay products failed to address the accessibility issues at the heart of the complaint. Courts have found this testimony persuasive.

Overlay Vendors Have Been Sued

In a notable development, accessibility overlay vendors themselves have faced legal challenges. A 2024 class action lawsuit alleged that a major overlay vendor engaged in deceptive marketing by claiming its product could make websites ADA-compliant when it could not.

The FTC Has Taken Notice

The Federal Trade Commission has signaled interest in the marketing claims of overlay vendors, particularly regarding claims of guaranteed compliance and lawsuit protection. While no formal enforcement action has been published as of early 2026, the scrutiny adds another dimension of risk for businesses relying on overlays.

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.

Continuous Monitoring

Every content update, feature release, and design change can introduce new barriers. Ongoing automated monitoring catches regressions quickly, while periodic manual testing ensures the full user experience remains accessible.

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 fix the source, not the surface. Our audit process identifies issues in your actual code, content, and design. Our remediation guidance helps your team fix the root causes.
• We combine automated and human testing. Our Ally platform provides continuous automated monitoring, while our expert auditors test with real assistive technologies to catch what automation cannot.
• We prioritize by user impact. Not all accessibility issues are equal. We help you focus on the barriers that matter most to real users, ordered by severity and user impact.
• We provide compliance documentation. Our platform generates the audit reports, progress tracking, and conformance documentation (VPATs/ACRs) that demonstrate genuine compliance to regulators, customers, and legal teams.
• We support ongoing compliance. Accessibility is a continuous practice, not a one-time purchase. Our monitoring and support ensure your site remains accessible as it evolves.

We do not add a widget to your site and call it done. We help you build accessibility into the foundation of your digital presence.

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. Courts have not accepted them as evidence of compliance. And independent research consistently shows they address only a fraction of accessibility barriers while sometimes creating 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 audit with Compliable and discover what genuine compliance looks like.