In January 2025, the Federal Trade Commission fined accessiBe one million dollars for lying about what its product could do. The company had been telling businesses that a single line of JavaScript would make their websites comply with the Web Content Accessibility Guidelines. The FTC called that claim false, misleading, and unsubstantiated. That same month, 85 companies running third-party accessibility overlays got sued anyway — overlay installed, lawsuit served.
This should have been the end of the conversation. It wasn't.
Overlay vendors are still running ads. They're still cold-emailing small business owners. They're still promising ADA compliance for $49 a month. And businesses — mostly small ones who can't afford a lawyer, let alone a proper accessibility remediation — are still buying it, believing they've checked the box.
They haven't. We've watched this play out for years, and we're going to say it plainly: accessibility overlays are snake oil. They don't fix the problems they claim to fix. They actively harm the people they claim to help. And they leave the businesses using them more exposed, not less.
What Overlays Claim to Do
The pitch is appealing. Drop a single JavaScript snippet into your site, and a widget appears — usually in the bottom corner. It offers toggles: bigger text, higher contrast, screen reader mode, dyslexia-friendly fonts, keyboard navigation. The marketing copy says things like "AI-powered accessibility" and "WCAG compliance in 48 hours." Some vendors guarantee legal protection.
AccessiBe, UserWay, AudioEye, EqualWeb — the products vary slightly, but the promise is the same. Automated code, zero developer involvement, instant compliance.
If you don't know much about how accessibility works, this sounds reasonable. A lot of website problems are visual, right? So a visual tool should fix them?
No. And the gap between what overlays promise and what they deliver is where people get hurt.
Why They Fail Technically
Web accessibility isn't a coat of paint. It's structural.
When a screen reader user visits your website, the screen reader doesn't see what you see. It reads the underlying HTML — the code. It looks for semantic elements: headings that mark sections, labels that describe form fields, alt text that conveys what an image shows, ARIA attributes that explain interactive components. If those things aren't in the HTML, they don't exist. No overlay can invent them.
An overlay can change font sizes and colour contrast on the visible page. That's CSS — surface-level styling. But the real barriers are deeper. Missing form labels. Broken heading hierarchy. Images with no alt text, or alt text that says "IMG_4582.jpg." Interactive elements that can't be reached with a keyboard. Modal dialogs that trap screen reader focus in an infinite loop. A JavaScript widget sitting on top of the page can't fix any of this, because these are problems in the source code.
Here's a specific example. Your contact form has three fields — name, email, and message. Each field uses placeholder text instead of a proper <label> element. A sighted user can read the grey hint text inside each box. A screen reader user hears nothing. The overlay can't generate the missing labels because it doesn't know what the fields are for. It can guess, and guessing wrong is worse than not guessing at all — imagine a screen reader announcing "email" for a phone number field.
WebAIM's 2024 analysis of the top one million home pages detected an average of 56.8 accessibility errors per page. Those are just the ones an automated tool can find. The real count is higher. An overlay running on top of all those errors is like putting a fresh tablecloth on a broken table.
And then there's the interference problem. Screen reader users already have a screen reader. They've spent years learning it, configuring it, building muscle memory around how it handles web content. When an overlay injects its own "screen reader mode," it often conflicts with the user's actual assistive technology. Keyboard shortcuts get hijacked. Focus order gets scrambled. Elements that were partially usable become completely unusable. The overlay makes the experience worse for the exact people it claims to help.
What the Disability Community Actually Says
This isn't a matter of opinion among the people who use assistive technology daily. The opposition is near-universal.
The National Federation of the Blind — the oldest and largest organization of blind people in the United States — revoked accessiBe's sponsorship of their 2021 national convention after reviewing the product and hearing from members. Their statement was blunt: the NFB board believes that accessiBe "currently engages in behavior that is harmful to the advancement of blind people in society." In 2025, the NFB filed comments supporting the FTC's consent order against the company.
The Overlay Fact Sheet, an open letter maintained by accessibility expert Karl Groves, has been signed by over 800 professionals and advocates — including contributors to the WCAG and ARIA specifications themselves, internal accessibility leads at Google, Microsoft, Apple, and the BBC, and researchers from MIT, Syracuse, and Carnegie Mellon. The statement is clear: overlays don't work, and their marketing is deceptive.
Accessibility isn't a widget you bolt onto a broken building. It's the foundation. If the structure is wrong, no amount of surface-level adjustment will make the building safe.
The International Association of Accessibility Professionals issued its own position statement calling out two specific false claims: that you can fix your site's accessibility with a single line of code, and that you can fix it in 24 hours. IAAP's recommendation is that overlays should not be used as a substitute for addressing actual code-level accessibility issues.
The European Disability Forum issued a joint statement with IAAP opposing accessibility overlays.
WebAIM's screen reader user surveys consistently show that when users encounter overlay widgets on websites, the most common response is to turn them off. The widgets interfere with tools they already rely on. Screen reader users don't need a website's "screen reader mode." They have a screen reader. They need the website's code to be written properly.
The Legal Risk Is Real — and Growing
Overlays don't just fail to protect you legally. In a growing number of cases, they make things worse.
In 2024, accessiBe itself was hit with a class action lawsuit by Tribeca Skin Care, a dermatology practice in New York City. The practice had purchased an accessWidget subscription in 2022 for $490 a year, believing the overlay would make their site ADA-compliant. In January 2024, they were sued for accessibility violations anyway. They ended up spending $4,000 in legal fees and another $3,500 remediating the actual code. The $490 overlay didn't prevent the lawsuit — it just delayed the real work.
In February 2025, BloomsyBox — an online flower delivery company — filed a class action suit against UserWay. BloomsyBox had installed UserWay's overlay in 2023, trusting the company's marketing that it was a "one-stop solution" for ADA compliance. Six months later, a blind customer filed suit because the site was still inaccessible. When BloomsyBox reached out to UserWay for the legal support they'd been promised, they were told their monthly plan didn't qualify. After upgrading to an annual plan, the "support" they received was a generic PDF guide. UserWay closed the support ticket. BloomsyBox ended up paying $4,000 in legal fees and settling independently.
These aren't isolated incidents. According to UsableNet, 25% of all web accessibility lawsuits filed in 2024 specifically cited overlay products — not as a defence for the website owner, but as evidence that the barrier hadn't been properly addressed. Over 1,000 lawsuits were filed against companies using overlays.
The courts have been consistent. An overlay is not remediation. Courts want to see the actual HTML and CSS fixed — proper heading structures, form labels, alt text, keyboard access. A JavaScript widget running on top of broken code doesn't meet that bar.
In Canada, the landscape is heading the same direction. The Accessible Canada Act targets a barrier-free Canada by 2040. Ontario's AODA has been enforceable for over a decade. Alberta doesn't yet have standalone accessibility legislation, but provincial human rights commissions already handle digital access complaints, and municipal procurement processes in Calgary increasingly require WCAG 2.1 AA compliance. An overlay won't satisfy any of these requirements because it doesn't produce a conformant website.
Why Businesses Keep Buying Them
We don't blame business owners who've purchased overlays. The sales pitch is designed to exploit a real anxiety.
Most business owners know accessibility matters but don't understand the technical specifics. They hear "ADA lawsuit" and panic. Along comes a vendor offering protection for less than the cost of dinner for two, every month. No developers needed. No code changes. Install a snippet and you're covered.
That's a compelling offer when the alternative sounds like a five-figure remediation project. And some overlay vendors have been aggressive in their marketing — accessiBe was paying for fake reviews and planting sponsored articles disguised as independent opinions, which was part of what the FTC fined them for.
The problem is that the cheap, easy option isn't actually cheap or easy once you get sued, pay legal fees, pay for real remediation, and deal with the reputational damage of a public accessibility complaint. The overlay was never the affordable path. It was the deferred-cost path, and deferred costs always come with interest.
What Actually Works
Accessibility is built into code. That's not a selling point — it's just how it works. There's no shortcut, the same way there's no shortcut to making a building wheelchair-accessible after it's been built with stairs and no elevator shaft. You can tape a sign to the stairs that says "accessible entrance." But the entrance doesn't exist until someone builds it.
Here's what real accessibility remediation looks like.
What Fixes Accessibility (For Real)
Semantic HTML. Use the right elements for the right purpose. Headings for headings (
<h1>through<h6>in order). Lists for lists. Buttons for actions, links for navigation. This is the foundation screen readers depend on.Proper form labels. Every input field needs a visible
<label>element tied to it in the code. Not placeholder text. Not a nearby<span>. An actual label that a screen reader will announce.Alt text on every meaningful image. Descriptive, specific, and honest. "Team of four developers reviewing wireframes in a Calgary office" — not "image1" or "photo."
Keyboard access to everything. Every link, button, form, menu, dropdown, and interactive component must be usable with a keyboard alone. Tab order should follow visual order.
Visible focus indicators. When someone tabs through your site, a visible outline must show them where they are. Removing the focus ring because it "looks ugly" is like removing a curb cut because it disrupts the sidewalk aesthetic.
Colour contrast. WCAG 2.1 AA requires a minimum 4.5:1 contrast ratio for normal text. Check every text-and-background combination. That soft grey on white might look clean, but it fails.
ARIA attributes where needed. For custom interactive components (modals, tabs, accordions), ARIA tells assistive technology what the component is and what state it's in. Used correctly, it fills gaps. Used incorrectly, it makes things worse — which is another reason automated tools can't just inject it.
Testing with real assistive technology. Automated tools like WAVE and axe DevTools catch 30-40% of accessibility issues. The rest requires manual testing with a screen reader, keyboard-only navigation, and input from people with disabilities.
None of this is mysterious. It's not new. WCAG 2.1 was published in 2018. The techniques have been documented for years. The problem isn't a lack of knowledge — it's a lack of will, budget, or awareness among the teams building websites.
When we build accessible websites, accessibility goes into the code from the first commit. It's not a phase at the end. It's not a checklist we run after launch. It's how the HTML is written, how the CSS handles focus states, how the JavaScript manages interactive components. Retrofitting accessibility is always more expensive than building it in.
We put together an accessibility checklist for business owners that you can run yourself in 30 minutes — no developer needed for the testing part. It won't catch everything, but it'll tell you fast whether your current site has serious problems.
The Cost Difference
A proper WCAG 2.1 AA audit from a qualified professional typically runs $2,000 to $5,000. Remediation depends on the severity of the issues and the size of the site, but for a typical small business website, budget $3,000 to $8,000 for thorough fixes.
Compare that to an overlay at $500 per year that doesn't work, followed by a lawsuit that costs $5,000 to $15,000 to defend, followed by the remediation you should have done in the first place. The math is not complicated.
And the audit isn't just about legal protection. Accessibility improvements directly affect usability for everyone — faster navigation, clearer forms, better mobile experience, and improved search visibility. The structural improvements that make a site accessible also make it easier for search engines and AI crawlers to understand.
Our Position
We don't install overlays. We don't recommend them. If a client comes to us with one installed, we remove it and do the actual work.
This isn't a nuanced issue with valid perspectives on both sides. The disability community — the people overlays claim to serve — has been clear and consistent for years. The professional accessibility community has been clear. The FTC has been clear. The courts have been clear.
Overlays are marketed to people who don't know enough about accessibility to evaluate the claims. That's what makes the business model work. And that's what makes it dishonest.
If you care about accessibility — and if you're serving Canadians, the law increasingly says you should — do the work. Fix the code. Test with real users. Build it properly. There is no shortcut, and the people selling you one are counting on the fact that you won't check whether it works until it's too late.
Sources
- FTC Order Requires Online Marketer to Pay $1 Million for Deceptive Claims (January 2025) — Federal Trade Commission press release on the accessiBe consent order, detailing false advertising claims and the $1M fine.
- FTC Approves Final Order Requiring accessiBe to Pay $1 Million (April 2025) — Final FTC order approved unanimously (5-0), barring accessiBe from making unsubstantiated WCAG compliance claims.
- Overlay Fact Sheet — Open letter signed by 800+ accessibility professionals, WCAG/ARIA specification contributors, and disability advocates opposing overlay products. Maintained by Karl Groves.
- NFB Convention Sponsorship Statement Regarding accessiBe (2021) — National Federation of the Blind statement revoking accessiBe's sponsorship, calling the company's practices "harmful to the advancement of blind people in society."
- IAAP Overlay Position and Recommendations — International Association of Accessibility Professionals position statement rejecting claims that overlays can fix accessibility with one line of code or in 24 hours.
- Another Web Access Overlay Company Sued by a Small Business (February 2025) — Lainey Feingold's analysis of the BloomsyBox v. UserWay class action lawsuit. Source for case details and timeline.
- Beware of AI Accessibility Promises: US Federal Agency Fines an Overlay Company One Million Dollars (January 2025) — Lainey Feingold's legal analysis of the FTC's action against accessiBe.
- The WebAIM Million — 2024 Report — Annual analysis of the top 1,000,000 home pages, reporting an average of 56.8 detectable accessibility errors per page.
- Web Content Accessibility Guidelines (WCAG) 2.1 — W3C Recommendation. The technical standard overlay vendors claim (falsely) to achieve compliance with.
- AccessiBe Faces Class Action Lawsuit Over Alleged Misrepresentation (2024) — Legal analysis of the Tribeca Skin Care v. accessiBe class action, source for case cost details.