Do Accessibility Overlays Work? Why a Widget Won't Make Your Website WCAG Compliant (2026)

No - accessibility overlays do not make a website WCAG compliant, and the evidence is no longer a matter of opinion. The US Federal Trade Commission fined the largest overlay vendor $1 million for claiming its product could make any site compliant; websites that already had a widget installed were sued at a steady 95 to 155 a month through 2025; and 72% of accessibility practitioners with disabilities rate overlays "not at all" or "not very" effective. An overlay can change how a page looks. It cannot fix how a page is built, and WCAG conformance is a property of how a page is built.

This matters in India right now: SEBI's digital accessibility circulars give regulated entities until 31 October 2026 to complete an accessibility audit and fix what it finds, and an audit by certified accessibility professionals tests the site itself - not the widget sitting on top of it.

Key Takeaways

• Overlays are JavaScript added on top of your site. They can adjust contrast, text size and cursors, and attempt automated repairs at page load. They cannot reliably fix keyboard access, form labels, focus order, error handling or image alt text - the categories where most WCAG failures live.
• They do not reduce legal risk. UsableNet found no meaningful drop in 2025 lawsuits against widget users, peaking above 150 in a single month.
• The regulator has ruled on the marketing. The FTC's 2025 order bars accessiBe from claiming its products can make any site WCAG compliant without evidence, and required a $1M payment.
• Users with disabilities rate them lowest. In WebAIM's 2021 practitioner survey, 67% of all respondents and 72% of respondents with disabilities called overlays ineffective.
• The Overlay Fact Sheet says it plainly: no overlay product can make a website fully compliant with any existing accessibility standard.
• For India: the RPwD Act, IS 17802 and SEBI's circulars all require conformance to a standard. An overlay does not produce conformance, so it does not produce compliance.

What Is an Accessibility Overlay?

An accessibility overlay is a script - usually one line of JavaScript - that loads a third-party tool on top of your existing website. Most products combine two things: a widget, the floating icon that opens a panel of contrast, font-size, cursor and "reading mode" toggles; and an automated repair layer that scans the page after it loads and tries to inject fixes such as guessed alt text or ARIA attributes.

Neither piece touches your source code. Your templates, components and forms stay exactly as they were; the overlay tries to paper over problems in the browser every time the page renders. That is the whole design, and it is why the limits below follow from the architecture rather than from any one vendor's quality. A better overlay is still an overlay.

Why Can't an Overlay Make a Site WCAG Compliant?

WCAG conformance is all-or-nothing at the page level: a page conforms at Level AA only if it satisfies every Level A and AA success criterion. To bring a page into conformance, a tool would have to fix everything - and the Overlay Fact Sheet, whose signatories include contributors to the WCAG, ARIA and HTML specifications and to the JAWS and NVDA screen readers, lists what automated repair does not do reliably:

• Text alternatives for images (an AI guess is not alt text that conveys purpose).
• Form field labels, error handling and focus control.
• Keyboard access.
• Content in PDFs, SVG, canvas and media.

Now set that list against what actually fails. The WebAIM Million 2026 scan of the top one million home pages found 95.9% had detectable WCAG 2 failures, and 96% of all errors fell into six categories: low-contrast text (83.9% of pages), missing alt text (53.1%), missing form labels (51%), empty links (46.3%), empty buttons (30.6%) and missing document language (13.5%). An overlay can adjust contrast cosmetically for users who open its panel, and might guess at alt text. The other four are structural, and the widget cannot touch them.

There is a second, subtler problem. The widget's features - larger text, higher contrast, a bigger cursor - duplicate what screen readers, magnifiers and operating-system settings already provide. A user who needs 200% text needs it on every site, so they already have it set up. At best the widget is redundant; at worst it fights the user's own assistive technology.

Do Overlays Stop Accessibility Lawsuits?

No. If overlays reduced legal exposure, sites that use them would be sued less. UsableNet's review of 2025 US filings found the opposite: lawsuits against companies using accessibility widgets ran at roughly 95 to 155 a month all year, "peaking above 150 cases in a single month", with "no meaningful reduction". An increasing number of complaints explicitly referenced the widget while alleging unresolved code-level barriers, and some claimed the widget itself interfered with screen readers.

The wider numbers from the same report show where the risk concentrates. More than 5,000 digital accessibility lawsuits were filed in 2025 across federal and state courts. E-commerce accounted for nearly 70% of them, because a checkout that cannot be completed by keyboard is the clearest possible harm. And 1,427 suits targeted companies that had already faced an accessibility claim; in federal court alone, 46% of cases involved repeat defendants - which is what happens when a first settlement is followed by a surface-level fix instead of remediation.

These are US figures, and India's enforcement mechanism is different. But the failure is the same everywhere: a person using a screen reader still cannot check out, and no widget changes that.

What Did the FTC Rule About accessiBe?

On 3 January 2025 the US Federal Trade Commission announced an order against accessiBe, the largest overlay vendor, over claims that its accessWidget could make any website WCAG compliant. The FTC's complaint called those claims "false, misleading, or unsubstantiated", and separately alleged the company had formatted third-party articles and reviews to look like independent opinions. The Commission voted 5-0 to issue the proposed order, then approved the final order 3-0 on 22 April 2025. It bars accessiBe from claiming its products "can make any website WCAG-compliant or can ensure continued compliance with WCAG over time" without evidence, and required a $1 million payment.

The wording matters to buyers everywhere. What the regulator named was not a bug; it was the claim of automatic compliance. If a vendor selling into India makes the same claim, the FTC order is the reference point for why it is not credible.

What Do Users With Disabilities Say?

WebAIM's third Survey of Web Accessibility Practitioners (758 respondents, 29% with a disability, published January 2021 - still the most recent in the series) asked directly about overlays, plugins and widgets. 67% of all respondents rated them "not at all" or "not very" effective. Among respondents with disabilities the figure was 72%, and only 2.4% of that group rated them "very effective."

The Overlay Fact Sheet collects first-hand accounts from screen-reader users describing sites becoming less usable after an overlay was added: focus jumping unexpectedly, pages flooded with spurious headings, and users blocking overlay domains outright just to complete a purchase.

There is also a privacy angle Indian businesses should weigh under the Digital Personal Data Protection Act. The Overlay Fact Sheet notes that overlays which switch on a "screen reader mode" automatically do so by detecting assistive technology on the visitor's device - in effect, inferring a disability without asking.

What Does This Mean for Indian Websites?

India's legal framework does not mention overlays, but it does require conformance to a standard - and that is the point.

• The Rights of Persons with Disabilities Act, 2016 requires accessibility of information and communication technology (sections 40, 42 and 46), and the RPwD (Amendment) Rules of 10 May 2023 made the IS 17802 standard mandatory for ICT products and services. Under section 89, a contravention is punishable with a fine of up to ₹10,000 for a first offence and ₹50,000 to ₹5 lakh for subsequent ones.
• SEBI's digital accessibility circulars (first issued 31 July 2025) apply to every regulated entity. After a clarification in December 2025 and an extension on 31 July 2026, the accessibility audit and remediation of its findings are due by 31 October 2026, conducted through certified accessibility professionals, with the annual compliance report due 30 April 2027. An auditor tests against WCAG success criteria with a screen reader and a keyboard. A widget does not change the result of that test.
• Any Indian business selling into the EU has been inside the European Accessibility Act's enforcement window since 28 June 2025. The reference standard is EN 301 549 v3.2.1, based on WCAG 2.1 AA; version 4.1.1, based on WCAG 2.2, was published in September 2026 and applies once formally cited in the EU's Official Journal.

In each case, the question a regulator, auditor or complainant asks is "does the site conform?" - not "did you install something?". Once you know the six error categories above, most remediation is predictable, and for many sites it costs less than a few years of overlay subscription fees.

What Should You Do Instead of an Overlay?

Fix at the source. Contrast, alt text, form labels, link text, button names and the lang attribute - the six categories behind 96% of detected errors - are mostly template-level fixes. On a WordPress or Shopify theme they are often days of work, not months.

Choose your stack with the data in hand. The WebAIM Million 2026 technology tables show home pages built with Astro (84% fewer errors than average), Next.js (27% fewer) and React (22.5% fewer) outperforming the norm, while pages using jQuery UI (+42%), Magento (+35%) and carousel libraries such as Swiper, Slick and OWL Carousel (+26% to +32%) do worse. If you are commissioning a build, accessibility is a specification line, not a plugin - our guide to what's included in website development services explains why a WCAG conformance target belongs in the scope document.

Test with real assistive technology. Automated scanners catch only part of the problem: in the UK Government Digital Service's 2017 test, individual tools found 17% to 41% of deliberately planted barriers, and Deque reports its own axe engine finds 57% by volume. The rest needs a keyboard-only pass and a screen-reader pass (NVDA on Windows, VoiceOver on Mac and iOS). A UX audit that includes these is a different exercise from a widget report.

Put it in the design system. Accessible components - visible focus states, consistent error patterns, colour tokens with contrast built in - mean every new page starts conformant. That is the argument for a design system rather than page-by-page fixes.

Keep it in maintenance. Accessibility regresses with every content update and plugin install; the WebAIM Million found average errors per home page rose 10.1% in 2026, to 56.1, reversing years of gradual improvement. Add an automated accessibility check to your CI pipeline and a quarterly manual pass to your website maintenance checklist.

If you already have an overlay installed, the practical advice from the Overlay Fact Sheet's signatories is to remove it and redirect the subscription fee into remediation. If you must keep it during a transition, do not describe your site as compliant because of it.

Frequently Asked Questions

Do accessibility overlays make a website ADA or WCAG compliant?

No. WCAG conformance requires every applicable success criterion to be met, and overlays cannot reliably fix keyboard access, form labels, error handling, focus control or image alt text. The Overlay Fact Sheet, signed by contributors to the WCAG, ARIA and HTML specifications, states that no overlay product can make a website fully compliant with any existing accessibility standard.

Why did the FTC fine accessiBe?

In January 2025 the US Federal Trade Commission found that accessiBe's claims that its accessWidget could make any website WCAG compliant were false, misleading or unsubstantiated, and that it had formatted paid articles and reviews to look independent. The final order, approved on 22 April 2025, bars those claims without evidence and required a $1 million payment.

Will an accessibility widget protect my business from lawsuits?

The data says no. UsableNet's review of 2025 US filings found lawsuits against websites that already had a widget installed ran at roughly 95 to 155 a month all year, with no meaningful reduction. Some filings now claim the widget itself interferes with screen readers.

Are accessibility overlays legal in India?

Installing one is legal. Relying on one for compliance is the problem: the RPwD Act, the IS 17802 standard and SEBI's digital accessibility circulars all require conformance to a standard, assessed by testing the site itself. An overlay does not change the outcome of that assessment.

What percentage of accessibility issues can automated tools find?

Far from all of them. In the UK government's 2017 test, individual automated tools found between 17% and 41% of deliberately planted barriers, and all ten tools combined found 71%. Deque, which sells automated testing tools, reports its axe engine finds 57% of issues by volume. Either way, a large share needs manual testing with a keyboard and a screen reader.

What should I do if my site already has an overlay?

Audit the underlying site against WCAG 2.2 AA, fix the six high-frequency error categories at the template level, test with a keyboard and a screen reader, and then remove the overlay. Do not describe the site as compliant on the strength of the widget in the meantime.

Working With Codevibe

Codevibe builds accessibility into the code, not on top of it: WCAG 2.2 AA as a scope line item, accessible components in the design system, and keyboard and screen-reader testing before launch. If you have an overlay installed and want to know what it is hiding, our UI/UX design team can audit the underlying site and plan the remediation - tell us about your site.

Sources

1. US Federal Trade Commission, order requiring accessiBe to pay $1 million (3 January 2025) and final order approval (22 April 2025).
2. UsableNet, ADA Web Lawsuit Trends for 2026: What 2025 Filings Reveal (8 January 2026). UsableNet sells remediation services; its figures are presented as its own counts, and the monthly widget range is read from its published chart.
3. WebAIM, Survey of Web Accessibility Practitioners #3 (January 2021) - the latest in the series.
4. Overlay Fact Sheet - an advocacy document, cited for its documented technical limitations and its signatories.
5. WebAIM, The WebAIM Million 2026.
6. Department of Empowerment of Persons with Disabilities, RPwD (Amendment) Rules 2023 on ICT products and services (10 May 2023); Rights of Persons with Disabilities Act, 2016, sections 40, 42, 46 and 89.
7. SEBI digital accessibility circulars: 29 August 2025, 25 September 2025, 8 December 2025 and 31 July 2026.
8. AccessibleEU (European Commission), EN 301 549 has been updated (7 September 2026).
9. UK Government Digital Service, What we found when we tested tools on the world's least-accessible webpage (February 2017); Deque, Automated testing study identifies 57 percent of digital accessibility issues (2021, vendor study).

Last reviewed: 22 September 2026 - every figure checked against its primary source; SEBI timelines reflect the 31 July 2026 extension. Nothing here is legal advice.