Accessibility Overlays, Explained: What They Are and Why Blind Users Block Them
In short
Accessibility overlays promise to fix websites with one line of code; blind users overwhelmingly say they do the opposite, interfering with the screen readers people actually use. This guide explains what overlays are, how they hurt, and what regulators and courts have said — including the FTC’s $1 million fine against accessiBe in January 2025. It also tells you how to fight back: on a Mac or PC, a free blocker extension removes the widgets; on iPhone, where no blocker exists, it covers what you can do instead.
If you have ever landed on a website and been told to "press a hotkey for screen reader mode," or noticed a little icon floating in the corner offering an "accessibility menu," you have met an accessibility overlay. They promise to make websites accessible with one line of code. Blind users overwhelmingly say they do the opposite — and enough of them install extensions specifically to block these widgets that one exists just for that job. This guide explains what overlays are, how they interfere with screen readers, what the law now says, and how to get them out of your way.
What an overlay actually is
An accessibility overlay is a piece of JavaScript a website owner adds to their pages — often sold as a single line of code. It injects a floating toolbar or icon (usually in a bottom corner) offering modes like "screen reader mode," text resizing, contrast toggles, and "profiles" marketed as ADHD-friendly or seizure-safe. The best-known vendors are accessiBe (accessWidget), AudioEye, UserWay, EqualWeb, and Essential Accessibility.
The sales pitch is seductive: instant accessibility, legal protection, AI that fixes your site automatically. The technical reality is thinner. An overlay applies runtime patches in your browser on top of the site's broken code — it does not rewrite the underlying page. Automated tools can catch roughly a third to half of accessibility issues; the rest needs a human looking at the actual code. If the overlay's script fails to load, or the site owner cancels the subscription, every "fix" vanishes instantly.
How they hurt screen-reader users
Blind users do not just find overlays unhelpful. They report that overlays actively break the setups they already use. The damage falls into a few repeatable patterns:
They hijack your keyboard
An overlay intercepts key presses before your screen reader receives them. You press Tab expecting to move through a form and instead land inside the widget's own menu — where Escape may not dismiss it. Accessibility writers have documented the exact scenario: a screen-reader user trying to book a restaurant reservation presses Tab, gets stuck in the overlay's menu, and cannot reach the booking form at all. As one technical teardown put it, the overlay script "attempts to interpret key events before the operating system screen reader receives them."
They trap your focus
Overlays frequently create keyboard traps — spots on the page you can Tab into but cannot Tab out of, like date pickers and search boxes. This is a hard WCAG failure (criterion 2.1.2, "no keyboard trap"), and it appeared in the FTC's own complaint: the Commission documented keyboard traps on sites using accessiBe's widget that prevented users from leaving search boxes or navigating date pickers. Sometimes the overlay's toolbar is itself the trap.
They double-announce everything
If you already use JAWS, NVDA, or VoiceOver and you activate the overlay's own "screen reader mode," you get two screen readers talking over each other. Every field gets announced twice: "Name, edit, name, edit." It is confusing and exhausting — the overlay's narration adds nothing your screen reader wasn't already saying.
They bulldoze your carefully tuned setup
This is the complaint that stings most. Blind users spend years refining their screen-reader configuration — speech rates, verbosity, shortcut mappings. Overlays override those choices and decide they know better. The FTC's complaint against accessiBe catalogued what that looks like in practice on customer websites: product images labeled "img_4534 scaled" instead of a real description, "add to cart" actions never announced to screen readers, price sliders and filters that cannot be operated by keyboard, and status messages that simply never reach the user.
Low-vision note: overlay contrast and text-size toggles duplicate what your operating system and browser already do — usually better, and system-wide. If a site's contrast mode fights the high-contrast or dark-mode settings you have already tuned at the OS level, that is the overlay's problem, not yours. Your system settings are the authority; an overlay is a guest.
The record: what regulators, courts, and the community say
This is not just grumbling. The case against overlays has been made on the record, repeatedly:
The FTC fined accessiBe $1 million. In January 2025 the Federal Trade Commission announced an enforcement action against accessiBe, the largest overlay vendor. The Commission alleged the company made false, misleading, or unsubstantiated claims that its accessWidget could make any website WCAG-compliant — including claims that an AI process reached full conformance within 48 hours — and that it disguised paid endorsements as independent reviews. The final consent order, approved in April 2025, requires accessiBe to pay $1 million and bars it from claiming its automated products can make websites WCAG-compliant without competent, reliable evidence. The company settled without admitting liability. Read the full breakdown in this explainer of the accessiBe FTC settlement.
- More than 800 accessibility professionals, advocates, and organizations signed the Overlay Fact Sheet, a public statement whose core conclusion is that "full compliance cannot be achieved with an overlay." Signatories include people working at Google, Microsoft, Shopify, eBay, Target, and Dell, plus the National Federation of the Blind and the American Council of the Blind. This evidence roundup quotes the fact sheet and the data behind it.
- The National Federation of the Blind condemned overlays in a 2021 resolution, calling on overlay providers to stop making misleading, unproven, and unethical claims — and ended accessiBe's convention sponsorship over concerns about its product and conduct toward blind users.
- Blind users themselves are blunt. When the OurBlind community asked whether accessiBe had improved, the response was, as the accessibility press summarized it, "unanimous and blunt: 'No, it absolutely has not.'" One user called overlays "malware." Another wrote: "I know with 100% certainty, any site which has deployed an overlay in the past year and a half has been less useable for both my wife and me — both blind." The a11y-collective's overlay investigation covers the community response and walks through the keyboard-hijacking scenario in detail.
- Overlays do not shield sites from lawsuits. In Murphy v. Eyebobs (2021), a court ruled that installing an overlay did not moot the plaintiff's ADA claim. Analysis of court records found more than 1,000 businesses were sued over accessibility in 2023–2024 while a widget was live on their sites — roughly a quarter of that year's digital-accessibility lawsuits. Some complaints specifically argue the overlay itself interfered with the user's screen reader.
How to bypass and block them
You do not have to put up with overlays. Here is the practical playbook:
On a Mac or PC: install an overlay blocker. Desktop Chrome — along with Edge and Brave, which share its extension system — lets you install AccessiByeBye, made by Pneuma Solutions. It is a free extension that blocks the major overlays — accessiBe, AudioEye, EqualWeb, MaxAccess, TruAbilities, User1st, and UserWay — so they never load on your pages. It collects no browsing data, it will not slow down your browser, and it is open-source (MIT license) on GitHub. If you ever want an overlay back, disabling the extension takes seconds. It is in the Chrome Web Store as AccessiByeBye. The blind-community podcast Living Blindfully demonstrated it in episode 261.
On an iPhone: no overlay blocker exists for Safari as of October 2026. Chrome on iPhone cannot install extensions — Apple does not allow them on iOS — so AccessiByeBye is not an option on your phone. What you can do: dismiss the widget's "screen reader mode" prompt and browse with VoiceOver as usual. And if an overlay is blocking something you need — a checkout, a form, a booking flow — report it to the site owner through their accessibility contact or feedback form, telling them specifically what broke and that you are using VoiceOver on an iPhone. That complaint is the iPhone user's leverage; there is no blocker to install instead.
Ignore "screen reader mode" prompts. If you already run JAWS, NVDA, or VoiceOver, a website's own "screen reader mode" adds nothing and risks the double-announcing problem above. Dismiss the prompt and browse with your own tools.
Trust your OS and browser over the widget's toggles. Text size, contrast, reduced motion, keyboard navigation — your operating system provides all of these system-wide, and respects them across every site. A per-site widget that fights those settings is strictly worse.
If an overlay is actively blocking something you need on a site — a checkout, a form, a booking flow — find that site's accessibility contact or feedback form and tell them, specifically, what broke and which screen reader you use. Site owners respond to customers more than to critics, and mentioning the FTC's 2025 order tends to focus minds. You should never have to install a blocker to use a store; until sites get the message, the blocker keeps you shopping on a desktop, and reporting the breakage is how iPhone users push back.
A note for sighted family and friends who run websites
Overlays are marketed to small businesses as lawsuit insurance. The evidence says they are the opposite: more than 1,000 businesses were sued in 2023–2024 with a widget live on their sites, courts have ruled an overlay does not fix the underlying violations, and the FTC has fined the largest vendor $1 million for saying otherwise. A widget is not a substitute for an accessible site.
What actually works is fixing the code. The WebAIM Million project finds that six failure types account for the overwhelming majority of automatically detectable WCAG errors: low contrast, missing alt text, missing form labels, empty links, empty buttons, and missing document language. Fix those in your source HTML, do a keyboard-only pass through your main flows, and test with a real screen reader. It takes longer than pasting a script. It is also the only approach that removes the barriers — and the risk. This plain-language guide to overlays is a good starting point for a site owner who wants the full picture.
About this guide
Accessibility overlays sit directly between blind shoppers and the stores they use — which makes them The Blind Bridge's business to explain. The facts above are drawn from the FTC's enforcement documents, court records, the Overlay Fact Sheet, and blind-community reporting, all checked in October 2026. Nothing on this page is for sale and no vendor paid for a word of it.
This is an informational guide — there is nothing to buy here, and no product links. For products blind shoppers actually recommend, see The Workaround Shelf.