Accessibility Overlay

An accessibility overlay is a third-party JavaScript plugin or widget that is added to a website with the promise of automatically detecting and repairing accessibility barriers. Overlay products typically add a visible toolbar icon (often a wheelchair symbol or person icon) to the corner of a website. When clicked, this icon opens a panel offering options like "increase text size," "change contrast," "pause animations," or "screen reader mode." Major overlay vendors include accessiBe, UserWay, AudioEye, EqualWeb, and MaxAccess. These companies market their products as quick, affordable solutions for ADA compliance and WCAG conformance. Plans typically cost $500 to $5,000 per year, which is significantly less than genuine accessibility remediation. This pricing is core to their pitch: they promise to solve a complex technical and legal problem for a fraction of the cost of real solutions. **The reality is that overlays do not work.** This is not a matter of opinion — it is the consensus of the disability community, accessibility professionals, independent researchers, federal regulators, and the courts. Overlays fail technically, fail legally, and actively harm the people they claim to help. Understanding why is important for anyone responsible for a website's accessibility.

Overlays matter because they are actively harming web accessibility by giving businesses a false sense of compliance. When a business installs an overlay and believes the problem is solved, it stops investing in genuine accessibility. The underlying code remains broken. People with disabilities continue to encounter barriers. And the business faces legal risk it thinks it has mitigated. The scale of this problem is significant. Overlay companies have installed their products on millions of websites, including those of Fortune 500 companies, government agencies, educational institutions, and small businesses. Every one of these websites is getting a false promise in exchange for an annual subscription fee. The disability community has been unambiguous in its opposition. The National Federation of the Blind (NFB), the largest organization of blind Americans, issued a statement calling on businesses to stop using accessiBe's overlay. Over 700 accessibility professionals — including engineers, designers, attorneys, and researchers — have signed the Overlay Fact Sheet (overlayfactsheet.com), a public document explaining why overlays are harmful. The American Council of the Blind and multiple other disability organizations have joined in opposing overlay technology. From a legal standpoint, overlays have failed to protect businesses from lawsuits. UsableNet's annual report on digital accessibility lawsuits has documented that a significant percentage of companies sued for web accessibility violations had an overlay installed at the time. Courts have consistently rejected the argument that installing an overlay constitutes ADA compliance or good-faith effort toward accessibility.

**Automated detection limitations.** Overlays rely on automated scanning to identify accessibility issues. But automated tools can only detect approximately 30-40% of WCAG failures, according to research by the Government Digital Service (UK) and independent accessibility organizations. Issues like illogical reading order, poor heading structure, inadequate link context, incorrect ARIA usage, and complex interaction patterns require human judgment to identify. Overlays cannot find what automated scanning cannot find. **AI-generated alt text.** Some overlays claim to use artificial intelligence to generate image descriptions. While AI image recognition has improved, it still produces generic, inaccurate, or misleading descriptions for many images. An AI might describe a product photo as "a person holding an object" instead of "Model wearing the Cascade jacket in forest green, size medium." For informational, educational, or e-commerce contexts, this level of inaccuracy is not acceptable. A screen reader user relying on these descriptions gets an unreliable experience. **DOM manipulation problems.** Overlays work by injecting JavaScript that modifies the page's DOM (Document Object Model) after it loads. This approach creates several problems: it can conflict with existing JavaScript on the page, it can break functionality in screen readers (which may read the page before or during the overlay's modifications), it adds page weight and loading time, and it creates a race condition where the accessibility "fixes" may not be applied in time for assistive technology to benefit. **The "screen reader mode" myth.** Some overlays offer a "screen reader mode" that restructures the page for screen reader users. This approach is fundamentally flawed because screen reader users already have the tools they need — what they need is for the underlying HTML to be correct. A separate "mode" creates a segregated, often broken experience rather than an inclusive one. It is the digital equivalent of a "separate but equal" accommodation. **Interference with assistive technology.** Screen reader users have reported that overlays actively interfere with their assistive technology. The overlay's DOM manipulations, forced focus changes, and injected elements confuse screen readers and disrupt established navigation patterns. Many screen reader users have browser extensions or scripts that specifically block overlay widgets because they make websites harder, not easier, to use. **Failure to fix structural issues.** The most critical accessibility barriers are structural: missing semantic HTML, broken heading hierarchies, inaccessible form structures, focus management failures in single-page applications, and custom components without proper keyboard support. These issues exist in the source code and require code changes to fix. An overlay cannot restructure a `<div>`-based navigation into a `<nav>` with proper `<ul>` and `<li>` elements. It cannot add keyboard event handlers to custom components. It cannot fix the tab order of a page with CSS-repositioned elements.

**Court rejecting an overlay defense.** In multiple federal cases, defendants have argued that installing an accessibility overlay demonstrates compliance or good-faith effort. Courts have rejected this argument, finding that the websites remained inaccessible despite the overlay's presence. Expert witnesses for plaintiffs have demonstrated specific, persistent WCAG failures that the overlay did not and could not fix. **NFB opposition to accessiBe.** In 2021, the National Federation of the Blind publicly denounced accessiBe, stating that the overlay "does not provide true accessibility" and calling on businesses to stop using it. This followed reports from blind users that accessiBe's overlay made websites harder to use with screen readers, not easier. **FTC investigation.** The Federal Trade Commission investigated accessiBe over its marketing claims that its product ensures ADA and WCAG compliance. The FTC found that these claims were not substantiated by evidence. This regulatory action put the entire overlay industry on notice that overclaiming about accessibility capabilities constitutes deceptive marketing. **The Overlay Fact Sheet.** Launched by accessibility professionals, overlayfactsheet.com catalogs the technical, legal, and ethical problems with overlays. The document has been signed by over 700 practitioners and is cited in legal proceedings, industry guidance, and educational materials. Its central thesis is that no overlay product can substitute for genuine accessibility work. **Real-world user experience.** A blind screen reader user visits an e-commerce site that uses an overlay. The overlay's toolbar widget captures focus when the page loads, forcing the user to interact with it before reaching the actual content. The "screen reader optimized" mode strips away visual formatting but also removes navigational landmarks. Product images have AI-generated alt text that reads "image of item" instead of describing the product. The checkout form lacks proper label associations that the overlay did not detect or fix. The user abandons the purchase.

**Believing the marketing.** Overlay companies spend heavily on marketing, SEO, and sales. Their websites feature testimonials, compliance claims, and ADA badges. These claims are not supported by evidence, have been challenged by the FTC, and have been rejected by courts. Evaluate overlay claims the same way you would evaluate any vendor's marketing — with skepticism and by consulting independent sources. **Treating accessibility as a procurement problem.** Accessibility is not something you buy from a vendor — it is a practice you build into your development process. Installing an overlay is like buying a fire extinguisher and calling it fire prevention. The underlying hazards remain. **Not consulting people with disabilities.** Before making decisions about accessibility tools, talk to actual users with disabilities. Every major disability advocacy organization opposes overlays. Screen reader users consistently report that overlays make their experience worse. Their voices should be the most important factor in your decision. **Assuming an overlay reduces legal risk.** Overlays do not reduce legal risk. They may increase it. Plaintiff's attorneys have stated that overlay badges signal that a website likely has unresolved accessibility issues. Installing an overlay can also be seen as knowledge of accessibility obligations without genuine effort to meet them — which undermines any argument of ignorance. **Buying time with an overlay while planning real remediation.** Some businesses install an overlay as a temporary measure while planning genuine fixes. This is understandable but problematic: the overlay may introduce new issues, creates a false sense of progress, and does not protect against legal claims during the interim period. A better temporary measure is publishing an accessibility statement acknowledging known issues and committing to a remediation timeline. **Confusing widget features with compliance.** The text-size and contrast adjustment features offered by overlay toolbars are redundant with browser and operating system settings that users already have. These features do not address the core WCAG failures — missing alt text, inaccessible forms, keyboard traps, broken ARIA — that create real barriers.