Do Accessibility Overlays Work? The Problems, at the Code Level
The FTC has acted against one overlay vendor’s claims, and the National Federation of the Blind, the International Association of Accessibility Professionals, the European Disability Forum and the practitioners who signed the Overlay Fact Sheet all say overlay widgets do not make websites accessible. Here is the evidence, and what happens in the code. Not sure what an overlay is? Start with the definition.
Compliapoint works on WordPress (including WooCommerce) and Shopify sites.
The Numbers Tell the Story
Every major data point — from government enforcement to user surveys — points in the same direction.
The Evidence Against Overlays
This is not opinion. These are documented enforcement actions, official resolutions, professional statements, and user testimony from the people most affected.
FTC Orders accessiBe to Pay $1 Million
On January 3, 2025 the FTC announced that accessiBe would pay it $1 million to settle allegations that it misrepresented the ability of its AI-powered tool to make any website compliant with WCAG. The complaint also alleged that accessiBe “deceptively formatted third-party articles and reviews to appear as if they were independent opinions by impartial authors.” The FTC approved the final order in April 2025.
Final order issued April 2025 — Announced January 2025NFB Resolution Opposing Overlay Products
The National Federation of the Blind — the oldest and largest organization of blind people in the United States — adopted Resolution 2021-04 on July 10, 2021, calling on overlay providers to “stop making misleading, unproven, and unethical claims”. In January 2025 it filed comments fully supporting the FTC’s proposed order against accessiBe.
Resolution passed 2021 — NFB comments on FTC order 2025The Accessibility Community's Unified Opposition
Accessibility professionals, researchers, and advocates have signed the Overlay Fact Sheet — a community-driven document that states overlays “are not an effective means of ensuring accessibility.” By October 2026 it carried more than 1,000 signatures, among them people working at Google, Microsoft, Shopify, eBay, Target, CVS Health and Dell Technologies, and at MIT, Carnegie Mellon and Gallaudet University.
Published March 2021 — more than 1,000 signatories by October 2026IAAP Official Position Against Overlays
The International Association of Accessibility Professionals — the global credentialing body for the accessibility field — published an overlay position and recommendations in early 2022. It is the same body whose certifications some overlay vendors cite for their own staff.
Position published early 2022EDF & IAAP Joint Statement on Overlays
The European Disability Forum and the IAAP issued a joint statement opposing accessibility overlay widgets. It says plainly that overlays “do not make the website accessible or compliant with European accessibility legislation.”
Joint statement published May 2023Two-Thirds of Accessibility Practitioners Rate Overlays Ineffective
In WebAIM’s January 2021 survey of web accessibility practitioners, 67% rated overlays, plugins and widgets that automate accessibility changes as not at all or not very effective. Among respondents with disabilities, the figure was 72%. (WebAIM Survey of Web Accessibility Practitioners #3.)
January 2021, 758 respondentsWhy Overlays Fail — The Technical Reality
Understanding why overlays cannot work requires understanding how assistive technology interacts with your website's code.
What Overlays Cannot Fix
- Broken HTML heading structure that screen readers depend on for navigation
- Missing or incorrect form label associations in the source code
- Keyboard navigation and focus management failures in JavaScript components
- Meaningful alt text for complex images — AI cannot interpret context accurately
- Inaccessible PDFs, downloadable documents, and embedded media
- Dynamic content in React, Angular, or Vue components that change after overlay loads
- Color contrast issues that require CSS changes overlays cannot reliably apply
- Reading order and document structure problems in the source
- ARIA attributes that conflict with the overlay's injected ARIA roles
- Touch target sizes and mobile accessibility issues
What Source-Code Remediation Fixes
- Heading hierarchy corrected directly in HTML templates
- Form labels properly associated using for/id attributes in the source
- Keyboard navigation and focus management repaired in event handlers
- Alt text written by humans who understand the content context
- PDFs tagged for screen reader navigation with proper reading order
- Component accessibility built into the theme templates and scripts that render it
- Color contrast fixed in CSS with proper ratio calculations
- Document reading order corrected in the DOM structure
- ARIA attributes applied correctly without runtime conflicts
- Every fix sits in your own code, which is what every assistive technology reads
Guesses, Timing and Tricks: How Overlays Fail in Practice
Why a script running in the visitor’s browser cannot do the job, even when it works exactly as its vendor designed it.
Its Repairs Are Guesses
A screen reader works from the browser’s accessibility tree, which Chrome’s developer documentation calls “a derivative of the DOM tree”. When an overlay script edits the page, that tree changes with it, so the edits do reach the screen reader. The trouble is what the edits are. A script can see that a form field has no label; it cannot know whether the field wants a phone number or a coupon code, so it guesses, and a confident wrong label misleads more than a missing one.
Modern Frameworks Change State Independently
Websites built with modern JavaScript frameworks — React, Angular, Vue, Next.js — update portions of the page dynamically without a full page reload. Each time a component re-renders, the overlay has to find it and patch it again. Anything it misses, or reaches only after someone has already started using it, is read in its original broken state, which is where the timing problem really lies: not at page load, but on every change after it.
One Overlay Was Caught Gaming a Checker
In June 2023 WebAIM found that UserWay’s overlay recognized its WAVE checker and rewrote the page for it, making all text black on white and giving every image alt="image", so WAVE reported zero errors. Visitors got nothing of the kind. Accessibility consultant Adrian Roselli documented it, and UserWay removed that code on June 9, 2023, after the finding became public.
Timeline of Overlay Controversy
The evidence against overlays has been building for years. Here are the key moments.
Disability Rights Attorney Publishes Warning
Lainey Feingold, a prominent disability rights attorney, published “Honor the ADA: Avoid Web Accessibility Quick-Fix Overlays”, urging businesses to avoid overlay products and citing UsableNet’s count of around 100 companies sued after installing one.
Overlay Fact Sheet Published
Accessibility expert Karl Groves and the accessibility community launched the Overlay Fact Sheet. By October 2026 it had more than 1,000 signatories.
National Federation of the Blind Resolution
The NFB adopted Resolution 2021-04, demanding that overlay providers stop making “misleading, unproven, and unethical claims” about what their technology does.
EDF & IAAP Joint Statement
The European Disability Forum and the International Association of Accessibility Professionals jointly oppose overlay products in an official published statement.
WebAIM Finds UserWay Gaming the WAVE Checker
WebAIM reports that UserWay’s overlay rewrote pages only for its WAVE tool, producing zero-error results visitors never saw. UserWay removes the code within the week.
Bloomsybox Files Class Action Against UserWay
Online flower delivery service Bloomsybox sued UserWay in federal court in Delaware, alleging it was sued for accessibility violations about five months after subscribing to the overlay, despite what it says UserWay promised about compliance.
1,023 Sued Companies Had a Widget Installed
UsableNet counted 1,023 companies sued in 2024 while an accessibility widget was live on their site, in a year of more than 4,000 digital accessibility lawsuits.
FTC Proposes Order Requiring accessiBe to Pay $1 Million
On January 3 the FTC announces a proposed order under which accessiBe pays $1 million to settle allegations that it misrepresented the ability of its AI-powered tool to make any website compliant with WCAG.
FTC Final Order Approved
The Commission approves the final order against accessiBe, which bars it from claiming its automated product can make any website WCAG compliant without evidence to support it.
Illinois Advises Against Overlays on State Websites
The Illinois Department of Innovation and Technology’s accessibility office advises against including overlays on State websites.
Choosing between named products such as accessiBe, UserWay and AudioEye is a decision rather than a mechanism, so that comparison lives on Accessibility Overlays vs Source Remediation.
What Actually Works: A Person Checking the Code
Every failure above ends in the same place. Something has to be judged by someone who understands what the page is for, and then fixed where it was written.
Fix the source code
Every accessibility violation exists in your HTML, CSS, JavaScript, or content. Fixing it at the source puts the repair in the code every assistive technology reads, and it stays there when you stop paying anyone. Updates still need watching, which is what monitoring below is for. This is what Compliapoint does — an audit, with a person reviewing what automation cannot judge, followed by direct source-code remediation. No JavaScript injection. No overlay script. No dependency on a third-party subscription to maintain compliance.
Get a human audit, not just an automated scan
In Deque’s 2021 study of more than 2,000 audits, automated testing accounted for 57 percent of the issues found, by volume. Everything else, from whether focus lands where a keyboard user expects to whether a label names what the field is for, took a person to find, and that is exactly the work an overlay is built to skip. Every Compliapoint engagement combines automated scanning with guided review by a person, not just an algorithm scanning for missing attributes.
What the person actually checks
Every interactive element reached with a keyboard alone, in an order that makes sense. Each page listened to with NVDA, JAWS and VoiceOver, to hear whether names, states and errors are announced and whether they mean anything. Text enlarged and the window narrowed until content reflows. Alt text read against the picture it describes. None of these is a pattern a script can match; each is a judgment about your content.
Document everything for legal defense
If you receive an ADA demand letter, your defense depends on documentation: what was audited, what was found, what was fixed, and when. A subscription to an overlay product does not produce this documentation. Compliapoint delivers a complete audit report, remediation documentation, a dated accessibility test record, and VPAT when needed — all permanent deliverables that you own regardless of any future business relationship.
Don't forget PDFs and documents
PDFs are easy to overlook, and an untagged PDF fails WCAG success criterion 1.3.1 Info and Relationships, at Level A, the minimum level of conformance. Overlay widgets cannot modify downloadable documents — they only affect HTML in the browser. Every PDF on your site needs proper tagging for screen reader navigation, correct reading order, and structured headings. PDF remediation is priced per page on our pricing page: $6.38 a page, quoted on your page count.
Monitor for new violations — but don't depend on monitoring to stay compliant
Content updates, plugin changes, new pages, and design refreshes can introduce new accessibility violations. Optional monitoring catches these changes before they become legal exposure. The key word is optional. Your source-code fixes remain in place whether or not you choose ongoing monitoring. With overlay products, stopping the subscription removes every modification — monitoring and "fixes" alike.
Common Questions About Overlays
Do accessibility overlays work?
Not as a route to WCAG conformance. An overlay changes the page in the visitor’s browser after it loads: its repairs are guesses about content it cannot understand, it has to re-patch the page every time something changes, and it cannot touch PDFs, captions or your source code. The FTC’s 2025 order against accessiBe, NFB Resolution 2021-04 and the IAAP’s overlay position all point the same way.
My developer recommended an overlay. Should I trust that advice?
Most web developers are not accessibility specialists. Overlays are marketed heavily to developers as an easy solution they can install in minutes. The appeal is understandable — the alternative is learning WCAG 2.2, auditing every page manually, and making detailed code changes. But the ease of installation does not correlate with effectiveness. Accessibility specialists — the people who do this full-time — have signed a document opposing overlays. The developer's recommendation is likely well-intentioned but not informed by the current professional consensus.
Can overlays fix any accessibility issues at all?
Overlays can make minor cosmetic adjustments: font size, cursor size, contrast overrides, link highlighting. These features duplicate functionality already available in every operating system's built-in accessibility settings — settings that users with disabilities have already configured for their needs. The more serious violations — broken form labels, missing alt text, keyboard traps, heading structure, reading order — cannot be reliably fixed by injecting JavaScript after page load.
What if I already have an overlay installed and I receive a demand letter?
Contact us immediately through our assessment form or contact page. We can evaluate your site's actual source-code compliance beneath the overlay and scope a remediation plan. The process is straightforward: we audit your source code, remediate the violations, deliver the dated records of what was tested and changed, and you remove the overlay script. Your site becomes natively accessible.
Are there any situations where an overlay makes sense?
As a temporary measure while source-code remediation is actively underway — and only as a temporary measure — an overlay can provide some marginal improvement. However, it should never be treated as a permanent solution, and it should never be represented as achieving compliance. The moment your source-code remediation is complete, the overlay should be removed. Compliapoint's standard delivery is 7–10 business days, which makes a long-term "temporary" overlay unnecessary.
How do plaintiffs' attorneys find out I'm using an overlay?
Overlay scripts are trivially detectable. Technology lookup services such as BuiltWith publish lists of sites running a given overlay, so assume anyone looking for yours can find it. The overlay's JavaScript file is visible in your page source code. The floating widget icon is visible on-screen. There is no way to hide the use of an overlay from someone who knows what to look for — and plaintiffs’ firms know what to look for.
The next question: what do you do instead?
If an overlay cannot do the job, the decision is what replaces it. Accessibility Overlays vs Source Remediation compares what each changes, what each costs over time, and how to swap out an overlay you already run.
Ready to Fix the Actual Problem?
Our Site Accessibility Assessment takes about five minutes. We review your answers and respond with a clear written proposal — no obligation, no automatic charges, no pressure.
Some eligible small businesses may qualify for the federal Disabled Access Credit for qualifying accessibility expenditures. Ask your tax professional whether your project qualifies.