Accessibility Overlays: What They Are, Why They Fail, and What To Do Instead
Accessibility overlay widgets promise one-click WCAG compliance, but the reality is far more complicated. This guide explains what overlays are, why they fail, the legal risks they carry, and what you should do instead.
What Are Accessibility Overlays?
Accessibility overlays are third-party JavaScript widgets that get injected into a website with the promise of automatically detecting and fixing accessibility issues. They typically appear as a small toolbar icon (often a wheelchair symbol or person icon) in the corner of a webpage, offering features like text resizing, contrast adjustments, and cursor enlargement.
Common overlay vendors include accessiBe, UserWay, AudioEye, EqualWeb, and Recite Me. These products are typically sold as SaaS subscriptions and marketed as a quick, low-cost solution to meet ADA, WCAG, and other accessibility requirements.
Overlay vendors claim their AI-powered technology can automatically scan, detect, and remediate accessibility barriers without requiring changes to the underlying source code. In reality, these claims do not hold up under scrutiny. Overlays attempt to patch the front end at runtime using JavaScript, but they cannot address the structural, semantic, and content-level issues that make a website inaccessible.
Why Overlays Cannot Fix Accessibility
There are fundamental technical and practical reasons why overlay widgets cannot deliver on their promises. Here are the four most critical limitations.
Limited Detection Capability
Automated tools can only catch approximately 30-40% of WCAG issues. The majority of accessibility barriers require human judgment to identify, including problems with reading order, meaningful alternative text, and logical content structure.
No Content Understanding
Overlays cannot understand the context or meaning of your content. They cannot write accurate alt text for images, determine if link text is descriptive, or ensure that form labels make sense in context. These tasks require human comprehension.
Introduces New Barriers
Overlays frequently introduce new accessibility problems including focus traps, screen reader conflicts, keyboard navigation issues, and performance degradation. The widget itself can become an obstacle for the very users it claims to help.
One-Size-Fits-All Fails
Disabled users have diverse needs. A blind screen reader user, a person with low vision, someone with motor disabilities, and a person with cognitive differences all interact with the web differently. A single widget cannot address this spectrum of needs.
Legal Risks of Using Overlays
Using an accessibility overlay does not protect your organization from legal liability. In fact, the presence of an overlay may increase your legal risk. Courts have repeatedly ruled that overlays do not constitute ADA compliance.
In landmark cases such as Robles v. Domino's Pizza, courts established that websites must be accessible under the ADA. Subsequent cases, including suits involving overlay-equipped websites, have confirmed that the mere presence of a widget is not a valid defense. In Murphy v. Eyebobs, the court found accessibility barriers persisted despite the defendant's use of an overlay product.
According to data tracked by accessibility law firms, hundreds of ADA digital accessibility lawsuits have been filed against websites actively using overlay products. In many of these cases, the overlay itself created additional barriers that strengthened the plaintiff's claims.
Important: Overlay vendor contracts often disclaim liability for accessibility lawsuits. If you are sued, the overlay vendor is unlikely to cover your legal costs or settlement. Your organization bears full legal responsibility.
What To Do Instead
Genuine accessibility requires integrating inclusive design and development practices into your workflow. Here are five effective alternatives to overlay widgets.
- 1
Conduct Proper Accessibility Audits
Hire qualified accessibility professionals to perform a comprehensive audit combining automated scanning with manual expert testing. A thorough audit identifies the full range of barriers, not just the subset that tools can detect.
- 2
Train Your Development Team on WCAG 2.2
Invest in training your designers, developers, and content creators on WCAG 2.2 guidelines. Teams that understand accessibility build it in from the start, which is far cheaper and more effective than trying to bolt it on after the fact.
- 3
Integrate Automated Testing into CI/CD
Use tools like axe-core, Pa11y, or Lighthouse in your continuous integration pipeline to catch regressions early. Automated tests work best as a safety net alongside manual testing, not as a replacement for it.
- 4
Test with Real Assistive Technology Users
Include people with disabilities in your usability testing. Screen reader users, keyboard-only users, and people with cognitive disabilities provide insights that no automated tool or overlay can replicate.
- 5
Build Accessibility into Your Design System
Create reusable, accessible components in your design system. When buttons, forms, modals, and navigation components are accessible by default, every page built with them inherits those qualities automatically.
Check If Your Site Uses an Overlay
Use our free Overlay Detector tool to scan any website for overlay widgets. See which vendor is installed and discover real WCAG violations the overlay fails to fix.
Scan Your Site NowFrequently Asked Questions
Are all accessibility overlays bad?▾
Most accessibility professionals agree that overlay widgets that claim to automatically fix accessibility issues are ineffective and can cause harm. They cannot replace proper remediation. Some vendors offer useful supplementary tools such as monitoring dashboards, but the auto-fix widget approach has been widely criticized by disability advocacy organizations, including the National Federation of the Blind.
Can I get sued for using an overlay?▾
Yes. Websites using accessibility overlays have been named in hundreds of ADA lawsuits. Courts have consistently ruled that the presence of an overlay does not constitute compliance with the ADA or WCAG standards. In some cases, the overlay itself introduced additional barriers that strengthened the plaintiff's case.
How do I remove an overlay from my site?▾
Removing an overlay typically involves deleting the vendor's JavaScript snippet from your site's HTML or tag manager configuration. Check your theme files, CMS plugins, or Google Tag Manager for the overlay script. After removal, conduct a thorough accessibility audit to identify and fix the underlying issues the overlay was masking.
What is the Overlay Fact Sheet?▾
The Overlay Fact Sheet (overlayfactsheet.com) is a joint statement signed by hundreds of accessibility practitioners, disability advocates, and organizations. It documents the technical limitations of overlays, the harm they cause to disabled users, and why they should not be used as a substitute for genuine accessibility remediation.
Do overlays help with Section 508 compliance?▾
No. Section 508 requires federal agencies and their contractors to meet specific technical standards based on WCAG 2.0 Level AA. Overlays cannot satisfy these requirements because they do not modify the underlying source code or fix structural accessibility issues. Federal agencies have been specifically advised against relying on overlay solutions.
How much does real accessibility remediation cost?▾
Costs vary widely depending on site complexity. A basic audit for a small site might cost $3,000 to $10,000, while enterprise-level remediation can range from $25,000 to $100,000 or more. However, building accessibility into your development process from the start is far more cost-effective than retroactive fixes. Training your team in accessible development practices is one of the best long-term investments.
Essential Accessibility Resources
Comprehensive tools, checklists, and guides to help you create inclusive digital experiences