The FTC, the National Federation of the Blind, the International Association of Accessibility Professionals, 800+ experts, state governments, and the courts all agree: overlay widgets do not make websites accessible. Here is the evidence.
Every major data point — from government enforcement to user surveys — points in the same direction.
This is not opinion. These are documented enforcement actions, official resolutions, professional statements, and user testimony from the people most affected.
The FTC found that accessiBe made false and misleading claims about its AI-powered overlay's ability to make websites compliant with WCAG standards. The FTC specifically determined these compliance claims were "not supported by competent and reliable evidence." The fine included charges related to deceptive advertising and fabricated customer reviews.
Final order issued April 2025 — Announced January 2025The National Federation of the Blind — the oldest and largest organization of blind people in the United States — issued a formal resolution stating that overlay providers "make misleading, unproven, and unethical claims" and that overlays "may actually make navigation more difficult" for people who rely on assistive technology. The NFB also submitted official comments supporting the FTC's enforcement action against accessiBe.
Resolution passed 2021 — NFB comments on FTC order 2025Over 800 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." Signatories include contributors and editors for WCAG, ARIA, and HTML specifications, as well as internal accessibility experts at Google, Microsoft, Apple, Shopify, BBC, eBay, Target, CVS Health, Dell, Lyft, and dozens of other organizations. Academic signatories represent MIT, Carnegie Mellon, Syracuse, and Gallaudet University.
Published 2021 — Active and growingThe International Association of Accessibility Professionals — the global credentialing body for the accessibility field — has published an official position and set of recommendations advising against reliance on overlay products for compliance. This is the organization that certifies the very experts overlay companies claim to employ.
Position published and maintainedThe European Disability Forum and the IAAP issued a joint statement explicitly opposing accessibility overlay widgets. With the European Accessibility Act requiring WCAG compliance for businesses operating in the EU as of June 2025, overlays have been confirmed as non-compliant with European standards as well.
Joint statement published May 2023In a WebAIM survey of people with disabilities, 72% of respondents said that accessibility overlays were "not at all" or "not very" effective at making websites usable. These are the actual end users — the people these products claim to help — reporting that the products fail to deliver on their core promise.
WebAIM Screen Reader User SurveyThe Illinois Department of Innovation & Technology's Office of Information Accessibility officially advises against including overlays on state websites, noting that "while accessibility overlays may eventually become effective and reputable tools," the current evidence does not support their use. Illinois cites the Overlay Fact Sheet, the FTC enforcement action, and the IAAP's official position in its guidance.
Published April 2025In multiple federal court rulings, defendants who argued that their overlay installation demonstrated good-faith ADA compliance were still found liable. Courts have required overlay removal and actual source-code remediation as conditions of settlement. The presence of an overlay has not been accepted as a legal defense in any published ruling.
Multiple federal cases — ongoingUnderstanding why overlays cannot work requires understanding how assistive technology interacts with your website's code.
This is the most fundamental technical reason overlays fail — and no amount of AI can fix it.
When someone using a screen reader visits your website, the assistive technology parses your HTML source code as the page loads. It builds a virtual document structure — called the accessibility tree — from that raw HTML. This happens immediately. An overlay widget is JavaScript that runs after the page has already loaded. By the time the overlay script executes and attempts to inject modifications into the DOM, the screen reader has already built its representation of your page from the original, broken source code. The overlay is trying to repair a house after the inspector has already filed the report.
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 would need to re-apply its modifications. In practice, overlays cannot keep up with these state changes, meaning portions of your site cycle in and out of their "fixed" state. Content that was accessible one moment becomes inaccessible the next as components update.
Accessibility consultant Adrian Roselli documented that UserWay's overlay was actively manipulating results from the WAVE accessibility testing tool. When tested, the overlay was adding black backgrounds behind text to hide contrast errors from automated scanners — without actually fixing the underlying contrast problems. The overlay wasn't making the site accessible; it was making the test results look better while leaving the actual barriers in place.
The evidence against overlays has been building for years. Here are the key moments.
Lainey Feingold, a prominent disability rights attorney, published a detailed analysis urging businesses to avoid accessibility overlay products, documenting cases where overlay users were sued.
Accessibility expert Karl Groves and the accessibility community launched the Overlay Fact Sheet. Within months, hundreds of professionals signed it — now over 800 signatories strong.
The NFB passed a formal resolution stating that overlay providers make "misleading, unproven, and unethical claims" and that their products may make navigation more difficult for blind users.
The European Disability Forum and the International Association of Accessibility Professionals jointly oppose overlay products in an official published statement.
Online flower delivery service Bloomsybox sued UserWay after being sued for accessibility violations just six months after installing the overlay — despite UserWay's promises of compliance and lawsuit protection.
Data from accessibility lawsuit tracking shows that one in four ADA website lawsuits in 2024 involved sites running overlay products, with plaintiffs' attorneys specifically targeting overlay users.
The Federal Trade Commission orders accessiBe to pay $1 million for deceptive business practices, finding their compliance claims were "not supported by competent and reliable evidence."
The FTC's final order against accessiBe is issued. Illinois becomes one of the first states to officially advise against overlay use on government websites, citing the FTC action, the Overlay Fact Sheet, and the IAAP position.
See how the most popular overlay products stack up against source-code remediation — with real data on each.
$1M FTC fine. Deceptive compliance claims. See the full breakdown of why accessiBe's overlay approach fails.
Read Full Comparison →1M+ installations. Class action lawsuit. Caught faking test results. See why scale doesn't mean compliance.
Read Full Comparison →Publicly traded. "Hybrid" marketing. Automation covers ~50% of issues. See what "hybrid" really means.
Read Full Comparison →The accessibility community has always been clear about what achieves compliance. There are no shortcuts.
Every accessibility violation exists in your HTML, CSS, JavaScript, or content. Fixing it at the source means the repair is permanent, works with every assistive technology, and survives updates to your site. This is what Compliapoint does — a full manual audit followed by direct source-code remediation. No JavaScript injection. No overlay script. No dependency on a third-party subscription to maintain compliance.
Automated scanning tools can detect 30–40% of WCAG violations at most. The remaining 60–70% — keyboard navigation, meaningful alt text, form logic, reading order, cognitive accessibility — require human evaluation. Every Compliapoint engagement includes a full manual audit by people who understand assistive technology, not just an algorithm scanning for missing attributes.
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 compliance certificate, and VPAT when needed — all permanent deliverables that you own regardless of any future business relationship.
PDFs are the most overlooked accessibility violation and a frequent target in demand letters. 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. Compliapoint includes PDF remediation as part of the engagement scope.
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.
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. Over 800 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.
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.
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. Many of our clients come to us after discovering their overlay did not prevent a demand letter. The process is straightforward: we audit your source code, remediate the violations, deliver your legal defense documentation, and you remove the overlay script. Your site becomes natively accessible.
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.
Overlay scripts are trivially detectable. Tools like BuiltWith can identify every website using a specific overlay product. Plaintiffs' law firms use these tools to generate target lists. 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 ADA plaintiffs' attorneys know exactly what to look for.
Our Site Accessibility Assessment takes about 3 minutes. We review your answers and respond with a clear written proposal — no obligation, no automatic charges, no pressure.
Eligible small businesses can recover up to $5,000 of accessibility costs annually via IRS Form 8826.