Accessibility overlay widgets: why they do not work

Accessibility overlay widgets are JavaScript tools that load on top of a website and claim to automatically fix accessibility issues. The major vendors include AccessiBe, UserWay, EqualWeb and AudioEye. They are marketed as a fast path to ADA and WCAG compliance: install one script tag and your accessibility problems are solved.

The accessibility and legal communities have documented extensively why this is not true. Overlays do not achieve WCAG 2.1 AA compliance. They do not reliably prevent ADA lawsuits. In some cases, they make the experience worse for disabled users. This post covers the technical reasons, the legal record and the positions of disability rights organizations.

The goal here is accuracy, not advocacy. If you are evaluating overlays as a compliance solution, you should understand what they can and cannot do. For the technical standard overlays claim to meet, see our WCAG 2.1 AA ecommerce checklist.

What overlays actually do

Overlays work by injecting a JavaScript layer that tries to detect and patch accessibility issues after the page has loaded. They use a combination of automated heuristics and, in some cases, a user-facing toolbar that lets visitors enable settings like larger text, high contrast or reduced motion.

The automated layer attempts to add missing ARIA attributes, generate alt text for images using machine vision, fix color contrast by overlaying CSS, and restructure some interactive elements. The user toolbar lets individuals customize their experience.

The two functions are distinct. The user toolbar is a legitimate accommodation tool, similar to browser accessibility settings. The automated remediation layer is where the compliance claims fall apart.

Technical limitations: what overlays cannot fix

Overlays operate on the rendered DOM. They can read and modify what is in the browser. They cannot modify server-side rendering, third-party iframes or the underlying code that generates the page. This creates hard limits on what they can remediate.

Missing alt text. Overlays use machine vision APIs to generate alt text for images that have no alt attribute. Machine-generated alt text is unreliable. It describes what it sees in the image, not the purpose the image serves on the page. A decorative image used as a divider may be labeled "abstract geometric pattern." An image of a product that is also the only way to understand what the product looks like may receive a description that misses the commercially relevant detail. WCAG 1.1.1 requires text alternatives that serve the equivalent purpose. Automated image description does not consistently meet that standard.

Heading hierarchy. WCAG 1.3.1 requires that information and relationships conveyed through visual presentation be programmatically determinable. A page with a broken heading hierarchy (headings used for visual size rather than document structure) needs its HTML restructured. An overlay cannot change the heading levels without breaking the visual design. It can add ARIA heading roles, but only with guesswork about the intended structure that no automated tool can reliably get right.

Form labels on third-party widgets. Third-party widgets, including payment forms loaded in iframes, embedded chat tools, review plugins and address autocomplete components, run in their own execution context. Overlay scripts cannot access the DOM inside a cross-origin iframe. This is a browser security boundary, not a limitation overlays can work around. If your Stripe payment fields are inaccessible, an overlay cannot fix them. If your Zendesk chat widget has unlabeled inputs, an overlay cannot add labels. These failures remain.

Keyboard navigation and focus management. Correct keyboard navigation requires that focus moves in a logical order, that focus is managed correctly when dynamic content loads, and that custom components implement the correct ARIA keyboard interaction patterns. Overlays cannot reliably infer the intended focus order of a complex page. They cannot know where focus should move when a modal opens or a new checkout step loads. These are design decisions that require code-level remediation.

Complex interactive components. A data table with sortable columns, a product configurator, a multi-step form with conditional logic: these require deliberate ARIA implementation from the development team. An overlay adding generic ARIA attributes to these components often makes them more confusing for screen reader users, not less, because the attributes do not match the actual behavior.

The legal record

The marketing premise of overlay vendors is that their product provides legal protection. The actual legal record does not support this.

In Nunez v. AccessiBe, filed in the Southern District of New York in 2021, a blind plaintiff alleged that AccessiBe's own website was not accessible despite using the AccessiBe widget. The case drew attention to the irony of the situation, a vendor selling accessibility tools whose own site failed accessibility tests.

More broadly, ADA web lawsuits have continued to be filed against businesses using overlay products. Plaintiff attorneys have explicitly stated in legal filings that the presence of an overlay widget does not constitute compliance with the ADA. Courts have not accepted overlay installation as a defense to inaccessibility claims. The overlay does not change the underlying HTML. If a screen reader user cannot complete a task, the barrier exists regardless of whether an overlay script is loaded on the page.

AudioEye, which went public in 2019, faced a class action securities lawsuit in 2021 alleging that the company made misleading statements about the effectiveness of its product and the legal protection it provides. The suit alleged that AudioEye knew its claims of WCAG compliance were overstated.

Several legal filings from 2022 and 2023 have included language explicitly addressing overlays, with plaintiffs' counsel noting that automated tools are insufficient to achieve WCAG compliance and that testing by real screen reader users revealed barriers that the overlay did not remediate.

The National Federation of the Blind position

The National Federation of the Blind (NFB), the largest and oldest organization of blind Americans, issued a statement in 2021 on accessibility overlays. The statement is direct: the NFB condemns overlay products that claim to provide compliance without genuine remediation.

The NFB's position is grounded in practical experience. Blind users interact with overlays regularly. The user-facing toolbar often interferes with screen readers rather than helping them. When a blind user navigates to a site with an overlay, the overlay's toolbar itself may not be keyboard accessible, creating a new barrier on top of the existing ones.

The NFB has specifically called out the business model of these products: selling a compliance claim to businesses that are not equipped to evaluate whether the claim is true. The organization's position is that genuine accessibility requires genuine remediation, manual testing by disabled users and ongoing maintenance.

The American Council of the Blind has taken a similar position, as has the Deaf-Blind community through its advocacy organizations.

OverlayFactSheet.com

In 2021, a group of accessibility professionals published OverlayFactSheet.com, which documented the technical limitations of overlay products with evidence. The fact sheet has since been signed by over 700 accessibility practitioners, developers, researchers and disabled users.

The fact sheet identifies three categories of failure: overlays do not fix all issues, overlays introduce new issues and overlays can actively interfere with assistive technology. On the third point, the fact sheet documents cases where overlay scripts conflict with screen reader keyboard shortcuts, intercept key events that the screen reader needs and prevent the screen reader from reading page content correctly.

The signatories include prominent accessibility researchers, web standards contributors and professionals who conduct accessibility audits for governments and large enterprises. The consensus among practitioners who test with real assistive technology is consistent: overlays do not achieve WCAG compliance.

Why the gap exists

Overlay vendors are not necessarily making fraudulent claims out of bad faith. The technical challenge they are addressing is real: most websites have accessibility problems, most development teams do not have accessibility expertise, and fixing accessibility correctly requires time and code changes.

The problem is that the overlay approach, automated remediation of a running page, cannot solve problems that exist in the source code. It is the equivalent of putting subtitles on a video after it is already playing: you can add some information on top, but you cannot change the underlying content.

WCAG 2.1 AA has 50 success criteria, as outlined in the full ecommerce checklist. Automated tools, including the best static analysis tools, reliably detect violations of approximately 20-25 of them. The remaining criteria require human judgment: does this image description convey the right information? Does focus management make sense to a real screen reader user? Is this error message genuinely helpful? Overlays cannot apply human judgment.

What works instead

Genuine accessibility remediation follows a different path. It is not faster or cheaper in the short term. It is more effective and it provides actual legal protection.

The process starts with an audit. Automated scanning identifies the violations that tools can find. Manual testing with a screen reader (NVDA, JAWS or VoiceOver), keyboard-only navigation and review by a qualified accessibility practitioner identifies the rest. A good audit produces a prioritized list of violations by severity and impact.

Remediation happens in the code. Labels are added to inputs. Heading hierarchies are corrected. Keyboard navigation is implemented for custom components. Alt text is written by people who understand what the images are supposed to communicate. ARIA attributes are added where they belong and only where they belong (incorrect ARIA is worse than no ARIA). For a breakdown of what this costs, see our analysis of ADA compliance costs for ecommerce.

Testing follows remediation. Changes are verified against the same criteria that identified the violations. Screen reader users test the critical flows: checkout, account creation, search, product pages.

Monitoring maintains compliance. Every theme update, new app installation, A/B test and checkout modification can introduce regressions. Continuous automated scanning catches new violations before they accumulate. Manual audits run periodically to check for what automation misses.

This process is slower and more expensive upfront. It produces a site that is actually usable by the 15-20% of consumers who have some form of disability. It produces evidence of compliance that can be presented in court. It reduces lawsuit risk because the barriers are actually removed.

The bottom line

Overlay widgets are not a compliance solution. They may partially address some visual issues. They do not achieve WCAG 2.1 AA. They do not reliably prevent ADA lawsuits. They are not accepted as a compliance defense by courts. Disability rights organizations actively oppose them.

If you have an overlay installed, it is not providing the protection the vendor sold you. The only thing that does is fixing the underlying code.

Frequently asked questions

Do accessibility overlays achieve WCAG compliance?

No. Accessibility overlays cannot fix issues that exist in source code, including broken heading hierarchies, missing form labels in third-party iframes, keyboard navigation failures and complex interactive components. WCAG 2.1 AA has 50 success criteria and automated overlays reliably address fewer than half.

Do accessibility overlays prevent ADA lawsuits?

No. Courts have not accepted overlay installation as a defense against ADA inaccessibility claims. ADA lawsuits have continued to be filed against businesses using overlay products, and plaintiff attorneys explicitly note that overlay presence does not constitute compliance.

What does the National Federation of the Blind say about overlays?

The NFB issued a statement in 2021 condemning overlay products that claim compliance without genuine remediation. The organization found that overlay toolbars often interfere with screen readers rather than helping them, creating new barriers on top of existing ones.

What works instead of an accessibility overlay?

Genuine accessibility requires an audit (automated scanning plus manual testing with screen readers), code-level remediation of violations, verification testing and continuous monitoring. This process is slower but produces a site that is actually usable and provides real legal protection.