If you ever pasted an "accessibility widget" onto your website to deal with AODA, this one's for you.
In 2025, the U.S. Federal Trade Commission took action against accessiBe — the largest accessibility-overlay vendor in the world — and the company agreed to pay $1,000,000 to settle charges that it made false, misleading, or unsubstantiated claims that its widget could make websites compliant with accessibility standards.
Read that again. The biggest player in the "instant compliance" business paid a million dollars because "instant compliance" wasn't real.
If you're an Ontario business owner with a December 31, 2026 AODA report on your horizon, you need to understand what this means — because the widget you may have installed to protect yourself could be doing the opposite.
What an overlay actually is (and isn't)
An accessibility overlay (accessiBe, UserWay, AudioEye, EqualWeb and similar) is a snippet of JavaScript you drop onto your site. It adds a little floating icon and tries to patch accessibility issues automatically, in the browser, without changing your actual website.
That's the problem. It doesn't change your website. It puts a layer on top.
Independent testing has consistently found that automated tools — including overlays — catch only 30–40% of WCAG accessibility failures. The other 60–70% require a human testing with a keyboard and the screen readers that disabled people actually use. An overlay can't see most of what it claims to fix.
"But at least it's something, right?"
Here's the uncomfortable part. In the first half of 2025, 456 businesses were sued over website accessibility with an overlay widget already installed — that's roughly 1 in 5 of all such lawsuits filed in that period. Having a widget didn't prevent the lawsuits. In many cases, it's what attracted them.
Plaintiff-side firms know the overlay scripts on sight. The widget is a signal — a flag that says "this business thinks a plug-in handled it." And courts have repeatedly declined to accept overlays as a legal defense. Settlements routinely require the business to remove the overlay and do real remediation anyway.
So the widget can be the cheapest way to get sued — not to avoid it.
What this means in Ontario specifically
A few Ontario-specific points worth being precise about:
- The deadline is real. Organizations with 20+ employees must file an Accessibility Compliance Report under the AODA, with the next deadline December 31, 2026. At 50+ employees (and across the public sector), the Integrated Accessibility Standards Regulation requires your public website and content to meet WCAG 2.0 Level AA.
- The lawsuit path is the Human Rights Code, not AODA directly. The AODA itself doesn't let an individual sue you. The real litigation exposure comes through the Human Rights Tribunal of Ontario, where someone can file a disability-discrimination complaint. Defending even one commonly runs $30,000+ — win or lose. If you also sell into the U.S., you carry ADA exposure on top.
- The fines are a backstop, not the everyday risk. You'll see "$100,000/day" quoted a lot. That's the statutory maximum on conviction — and as of 2026 it has never actually been applied; real administrative penalties have run in the hundreds-to-low-thousands range under a progressive enforcement process. The honest motivator here isn't a scary headline number. It's the deadline, the very real cost of a single complaint, and the fact that an overlay gives you none of the protection it advertises.
What actually holds up
There's no magic here, which is exactly the point. Real, defensible accessibility looks like this:
- A real audit — automated plus manual testing with keyboards and screen readers, against WCAG 2.2 AA.
- Source-code remediation — fixing the actual HTML, components, and content, so the site is accessible whether or not any script is running.
- Documentation — an audit and a remediation plan you can put in front of a regulator or a tribunal. This is what turns "we ignored it" into "we acted in good faith," and that distinction is what meaningfully reduces both the odds and the cost of a complaint.
That's the difference between looking compliant and being compliant — and being able to prove it.
See where your site actually stands — free
We built a free tool for exactly this moment. The PassProof Report scans your site against Ontario's AODA/WCAG rules in about 30 seconds and tells you:
- your top accessibility failures, in plain English,
- whether you've got an overlay installed and what it isn't covering,
- what legally applies to a company your size, and
- a fixed-price path to fix it.
No obligation, no sales call required to get it.
👉 Get your free PassProof Report
PassProof is a remote-first accessibility-engineering studio serving Ontario. We fix the real source code to WCAG 2.2 AA — the kind that holds up — and help Ontario businesses fund the work through programs like CSBFP and CanExport. This article is accessibility-engineering guidance, not legal advice; we work alongside your counsel.