Skip to main content

Do Accessibility Overlays Work? The Evidence

Benjamin Morton

Do accessibility overlays work? Not as a way to make a website accessible or compliant. The Overlay Fact Sheet, signed by more than 1,000 accessibility practitioners, states that "No overlay product on the market can cause a website to become fully compliant with any existing accessibility standard and therefore cannot eliminate legal risk" (Overlay Fact Sheet). The European Commission says overlays, "or any other tools which do not ensure the website itself meets the detailed criteria of the standard, are not an appropriate solution" (European Commission). An overlay is a script that changes the page in the visitor's browser after it loads; the site's own code stays as it was.

Problems With Accessibility Overlays

  1. They cannot make a site conform to WCAG. The Overlay Fact Sheet accepts that an overlay "may improve compliance with a handful of provisions in major accessibility standards", but says "full compliance cannot be achieved with an overlay" (Overlay Fact Sheet).
  2. Automated repair is unreliable and can get in the way of assistive technology. The same fact sheet lists automated text alternatives, form labels and keyboard access as "not reliable", and says repairs "can either slow down page load times or cause unexpected page changes for assistive technology users" (Overlay Fact Sheet).
  3. Detecting assistive technology raises privacy concerns. Overlays that switch on screen reader modes automatically do so "by detecting when an assistive technology is running on the device. This exposes the fact that the person using the device at the time has a disability" (Overlay Fact Sheet).
  4. Sites using them still get sued. 456 ADA website lawsuits in the first half of 2025, 22.64% of the 2,014 filed, targeted websites with an accessibility widget installed (EcomBack, 2025).
  5. Disabled practitioners rate them poorly. In WebAIM's January 2021 survey of accessibility practitioners, 72% of respondents with disabilities rated overlays and similar tools "not at all or not very effective", and only 2.4% rated them very effective (WebAIM, 2021).
  6. No automated tool can confirm compliance on its own. The FTC's complaint against accessiBe states that, according to experts including the W3C, "no automated testing tool alone can determine if a website meets accessibility standards. Rather, manual human testing is required" (FTC complaint, 2025).

TL;DR: Overlays do not make websites WCAG-conformant and do not stop lawsuits. 22.64% of ADA website lawsuits in H1 2025 targeted sites with a widget installed (EcomBack, 2025). In April 2025 the FTC approved a final order requiring accessiBe to pay $1 million. Fix the source code instead.

Developer reviewing accessibility code on a laptop screen, representing the technical depth needed beyond quick-fix overlays

Do Accessibility Overlays Prevent Lawsuits?

No. 456 ADA website lawsuits filed in H1 2025, 22.64% of the total, targeted websites that already had an accessibility widget installed (EcomBack, 2025). For all of 2025, UsableNet counted more than 5,000 digital accessibility lawsuits and found "no meaningful reduction in lawsuits against widget users" in its monthly filing data (UsableNet, 2026). E-commerce accounted for nearly 70% of ADA web lawsuits.

Some complaints go further than noting the overlay was installed. In 2024, 25% of lawsuits (1,023) cited widgets as barriers rather than solutions, according to Accessibility.works, which draws on UsableNet's 2024 year-end report (Accessibility.works, 2025).

Filing is also getting easier. Seyfarth Shaw counted 40% more federal pro se ADA Title III lawsuits in 2025 than in 2024, based on average monthly numbers, and links the rise to AI tools (Seyfarth Shaw, 2025). EcomBack also reports that demand letters, many of which never reach a court record, are increasing.

What Can Overlays Actually Fix?

Overlay widgets typically offer font size, contrast, spacing and cursor controls. The Overlay Fact Sheet points out that the people these features are meant to serve will already have them on their own computers, either built in or as separate software (Overlay Fact Sheet). The harder problems sit in the markup, and an overlay runs as JavaScript on top of it after the page renders (TestParty).

Here's what overlays cannot reliably fix:

  • Missing alt text. An overlay can try to generate alt text with AI, but AI can't reliably describe images in the right context. A photo of a team might need "Marketing team at Q3 kickoff", not "group of people standing indoors."
  • Broken ARIA implementations. If your custom dropdown uses role="menu" incorrectly, an overlay can't safely restructure the DOM to fix it.
  • Keyboard traps. When focus gets stuck inside a modal with no escape route, the fix is the missing event handling in your source code.
  • Form labels. Programmatically associating a <label> with an <input> requires editing HTML. Overlays inject ARIA attributes that sometimes work and sometimes clash.
  • Semantic structure. Heading hierarchy, landmark regions and list markup are baked into your HTML. A script layer cannot dependably restructure a page that uses <div> for everything.

The core problem is architectural. Overlays operate in the presentation layer. Accessibility lives in the markup. A <div onclick="..."> needs to become a real <button> with proper keyboard handling, role and focus management, and that change belongs in the source.

The Overlay Fact Sheet's signatories include contributors and editors of the WCAG, ARIA and HTML specifications, consultants from more than a dozen countries, and in-house accessibility specialists at companies such as Google, Microsoft, Apple, BBC and Shopify (Overlay Fact Sheet). If you want tools that work at the code level, our best accessibility scanning API guide compares the options.

Close-up of a computer screen showing HTML source code with accessibility markup highlighted

Overlay Vendors: The Public Record

This section lists regulator actions, court filings and rulings, and the vendors' own published statements for three of the best-known overlay vendors. It reports what each record says and nothing more. Allegations in a complaint are claims, not findings, and a ruling on a motion to dismiss assumes the complaint's facts are true for that purpose only.

accessiBe

FTC complaint and proposed order, January 3, 2025. The FTC announced a complaint and proposed consent order against accessiBe Inc. and accessiBe Ltd., sellers of the accessWidget plug-in (FTC, 2025). The complaint alleged that:

  • accessiBe represented that accessWidget's AI and other technology makes any website WCAG compliant and keeps it compliant as the site changes, and that these representations were "false or misleading or were not substantiated" (FTC complaint). The complaint quotes accessiBe marketing that promised compliance within 48 hours.
  • accessiBe presented reviews, articles and blog posts on third-party sites as independent opinions when they were not, and failed to disclose that it paid for them or helped draft, edit or approve them.

The proposed order required a $1 million payment, barred accessiBe from claiming its automated products can make any website WCAG compliant or ensure continued compliance unless it has evidence to support the claim, barred misrepresentations about the independence of reviews and endorsers, and required disclosure of material connections to endorsers. The Commission vote to accept it was 5-0.

FTC final order, April 22, 2025. After a public comment period, the Commission voted 3-0 to approve the final order, which requires the $1 million payment and keeps the restrictions on WCAG compliance claims (FTC, 2025). Case documents are on the FTC case page.

accessiBe's response. accessiBe published a statement saying the FTC review "focused on the past period between 2019-2022", that it "reached a no-admission settlement", and that "We strongly disagree with the FTC's allegations." It said it believes the allegations "are largely based on outdated information and flawed testing methodologies", and that "The FTC's complaint does not challenge our ability to ensure that our customers' websites are compliant with the Americans with Disabilities Act (ADA)" (accessiBe statement, archived November 2025). The original page at accessibe.com/ftc-statement returned a 404 error when we checked on October 16, 2026.

Customer class action, filed June 26, 2024. Sherwin K. Parikh MD, P.C. v. accessiBe, Inc. (S.D.N.Y., No. 1:24-cv-04848) is a putative class action now brought by three businesses that deployed accessWidget. They allege that accessiBe claimed the widget would make any website conform to WCAG 2.1 AA, and so comply with the ADA, within 48 hours. On March 31, 2026, Judge P. Kevin Castel granted accessiBe's motion to dismiss "as to all claims other than the breach of contract claim insofar as it alleges that accessiBe misrepresented its Widget's ability to ensure WCAG and ADA compliance" (opinion and order, 2026). An answer to the amended complaint was filed on June 25, 2026, and the case remains open (docket).

AudioEye

Patent litigation with accessiBe, 2020 to 2022. AudioEye sued accessiBe for patent infringement in the Western District of Texas on September 4, 2020 (docket), and accessiBe sued AudioEye for patent infringement in the District of Delaware on June 16, 2022 (docket). AudioEye's November 10, 2022 earnings release, filed with the SEC, states that "In October 2022, AudioEye and AccessiBe agreed to a global settlement of all pending legal disputes", which includes mutual covenants not to sue (SEC filing, 2022). The Delaware case was closed on a stipulation of dismissal on October 26, 2022.

AudioEye v. Roselli, 2023 to 2024. AudioEye sued accessibility consultant Adrian Roselli in the Supreme Court of the State of New York, Erie County (Index No. 803054/2023), over statements he had published about the company. Roselli moved to dismiss under New York's anti-SLAPP law (memorandum of law, July 5, 2023). On January 3, 2024, the parties filed a stipulation stating that they "have settled and compromised the claims" and that the action is dismissed with prejudice (stipulation, 2024). The filing does not state the settlement terms. Both documents are court filings published by Roselli.

AudioEye's position. In a 2026 post, AudioEye writes that "Accessibility overlays alone do not reliably prevent ADA lawsuits" and that "An overlay is designed to be the entire solution on its own." It describes its own product as pairing automated technology with expert audits by certified experts and people with disabilities who use assistive technology (AudioEye, 2026).

UserWay

Ownership. UserWay's site names Level Access as "the parent company of UserWay" (UserWay). Level Access announced that it had completed the acquisition on March 20, 2024 (Level Access press release, via JMI Equity, 2024).

Customer class action, filed July 19, 2024. In Bloomsybox.com LLC v. UserWay, Inc. (D. Del., No. 1:24-cv-00844), an online flower retailer brought a putative class action. The complaint says it bought a $129 per month UserWay subscription in July 2023 and was served with an ADA website lawsuit on December 11, 2023. It pleads breach of contract and the implied covenant of good faith, the Delaware Consumer Fraud Act, the Magnuson-Moss Warranty Act, and negligent misrepresentation (complaint, 2024). UserWay moved to dismiss. On March 2, 2026, Judge Richard G. Andrews adopted the magistrate judge's February 13, 2026 recommendation: the contract and Magnuson-Moss counts and the request for injunctive relief were dismissed without prejudice, and the Delaware Consumer Fraud Act and negligent misrepresentation counts go forward (order, 2026).

UserWay's position. UserWay offers a Litigation Support Program with its annual widget subscription for customers facing a lawsuit or demand letter. The page states that "Level Access, the parent company of UserWay, and UserWay itself are not law firms and do not provide legal representation" (UserWay).

Citation capsule: In January 2025 the FTC alleged that accessiBe's claims that accessWidget makes any website WCAG compliant were false, misleading or unsubstantiated, and in April 2025 it approved a final order requiring a $1 million payment. accessiBe describes the settlement as no-admission and says it disagrees with the allegations. Customer class actions against accessiBe (S.D.N.Y.) and UserWay (D. Del.) each had part of their claims survive motions to dismiss in March 2026.

What Are the Alternatives to Accessibility Overlays?

Fix issues in the code, and catch them early. Deque's figures put a defect fixed in development at about $350 less than one found in QA, and one fixed in QA at about $450 less than fixing it in production (Deque, 2024).

Option 1: Automated testing in your CI/CD pipeline

Automated scanners like axe-core run during development and flag WCAG violations before code ships. They catch the programmatically detectable share of issues, about 30-40% according to TestParty (TestParty): missing alt text, broken form labels, color contrast failures, missing language attributes.

The cost ranges from free (open-source tools like axe-core and Pa11y) to $5,000-$50,000/year for enterprise platforms with dashboards, historical tracking and API access. That's more than a $49/month overlay, but the tool finds real issues in the source code, where fixes happen. We've compared the leading options in axe vs Lighthouse vs WAVE vs Pa11y.

Option 2: Manual expert audit

A standard manual accessibility audit typically runs $5,000 to $15,000, with comprehensive enterprise audits reaching $20,000 to $50,000 or more (TestParty). An auditor tests with real assistive technology (screen readers, switch devices, voice control) and catches what automation misses.

Option 3: The hybrid approach

The most effective strategy combines both. Automated scanning catches regressions continuously. Manual audits verify the full experience periodically. Developer training stops new issues being introduced.

Approach

Upfront Cost

Annual Cost

What It Catches

Overlay widget

$0

$490-$950/yr

Surface-level UI adjustments only

Automated testing (OSS)

$0

$0 (staff time)

30-40% of WCAG violations

Automated testing (Enterprise)

$0-$5,000

$5,000-$50,000/yr

30-40% with dashboards and reporting

Manual audit

$5,000-$50,000

$500-$2,000/yr

Full WCAG coverage including UX

Hybrid (automated + audit)

$5,000-$55,000

$5,500-$52,000/yr

Maximum coverage, continuous + periodic

The overlay is the only line in the table that leaves your code unchanged.

What the WebAIM Million tells us about progress

The WebAIM Million study found that 95.9% of the top one million homepages had detectable WCAG failures in 2026, with an average of 56.1 errors per page (WebAIM, 2026). That's worse than 2025, when the figures were 94.8% and 51 (WebAIM, 2025). Pages are getting heavier too: the 2026 report found average page elements rising to 1,437 per homepage, a 14.3% increase in one year, and pages with ARIA averaged more errors (59.1) than pages without it (42) (WebAIM, 2026).

On overlays specifically, the 2024 WebAIM Million found that home pages where common overlays were detected averaged fewer errors than the 56.8 average: AudioEye 36.9, UserWay 42.9 and accessiBe 50.5. WebAIM notes that overlays that manipulate WAVE results were disabled before testing (WebAIM, 2024). Detectable errors are only the automatically testable part of WCAG, so a lower count is not the same as conformance.

A person using a smartphone with accessibility settings enabled, showing enlarged text and high contrast display

Frequently Asked Questions

Do accessibility overlays work?

Not as a route to accessibility or compliance. The Overlay Fact Sheet says no overlay can make a site fully compliant with any existing accessibility standard (Overlay Fact Sheet), and the European Commission says overlays that do not make the website itself meet the standard "are not an appropriate solution" (European Commission).

Are accessibility overlays illegal?

No. Selling or installing one isn't illegal. The FTC's order against accessiBe concerned its marketing claims, not the product's existence: it bars claims that its automated products can make any website WCAG compliant unless the company has evidence to support them (FTC, 2025). Relying on an overlay as your only accessibility work won't protect you from ADA lawsuits.

Do overlays help screen reader users?

Disabled practitioners rate them poorly. In WebAIM's 2021 practitioner survey, 72% of respondents with disabilities rated overlays not at all or not very effective, and only 2.4% rated them very effective (WebAIM, 2021). The Overlay Fact Sheet also warns that automated repairs can cause unexpected page changes for assistive technology users (Overlay Fact Sheet).

How much does it cost to make a website accessible without an overlay?

Costs range from $0 for open-source automated tools like axe-core to $50,000+ for a full manual audit of a complex site (TestParty). A practical starting point: run axe-core in your CI/CD pipeline for free, fix what it catches, then budget $5,000-$15,000 for a manual audit of the issues automation can't detect.

Will the European Accessibility Act affect US companies?

Yes, if you serve EU customers. The EAA became enforceable on June 28, 2025 across all 27 member states, with penalties set by each member state rather than a single EU-wide cap (EAA developer guide). It applies to covered digital products and services sold in the EU regardless of where the company is headquartered. The European Commission's position is that overlays are not an appropriate way to meet the standard (European Commission).

Can AI fix accessibility issues automatically?

Not reliably. AI can identify some violations and suggest fixes, but it can't dependably judge context: whether an image needs descriptive alt text or is decorative, whether a heading structure makes sense, or whether a custom widget is keyboard-operable. The FTC's accessiBe case turned on the gap between AI compliance claims and what the product delivered on real websites.

The Bottom Line

Overlays don't make websites accessible, and they don't stop lawsuits: 22.64% of ADA website lawsuits in H1 2025 targeted sites with a widget installed. The FTC required accessiBe to pay $1 million and to stop claiming its AI makes any website WCAG compliant without evidence, and the European Commission calls overlays "not an appropriate solution."

What works is fixing your source code. Automated testing catches the detectable share of WCAG issues during development, manual audits cover the rest, and both cost less the earlier they happen. If you're using an overlay now, replace it with a real testing strategy: start with automated scanning in your CI/CD pipeline, then invest in a professional audit. Our accessibility testing tools comparison breaks down where to start.