The $1 Million Wake-Up Call for Ontario Businesses
In 2024, the U.S. Federal Trade Commission took action against accessiBe, one of the most widely marketed accessibility overlay widgets on the internet, resulting in a $1 million settlement over deceptive claims. The company had told thousands of businesses that installing a single line of code on their website would make them fully compliant with accessibility laws. It did not. It could not. And businesses that believed those promises were left exposed.
If you operate a business in Ontario, this story matters to you — because the Accessibility for Ontarians with Disabilities Act (AODA) places real, enforceable obligations on your organization, and a widget cannot fulfill them.
What the AODA Actually Requires
The AODA is Ontario's landmark accessibility legislation, and its digital requirements are found in Ontario Regulation 191/11, also known as the Integrated Accessibility Standards Regulation (IASR). Under this regulation, organizations with one or more employees must ensure their websites and web content conform to the Web Content Accessibility Guidelines (WCAG) 2.0 Level AA.
For private and non-profit organizations, the compliance deadlines have already passed:
- January 1, 2014 — New public websites and significantly refreshed content must meet WCAG 2.0 Level A
- January 1, 2021 — All public websites and web content must meet WCAG 2.0 Level AA
This is not a suggestion. Non-compliance can result in fines of up to $100,000 per day for corporations under the AODA. The Government of Ontario has been increasing enforcement efforts, and businesses of all sizes are being audited.
What Overlay Widgets Actually Do
Accessibility overlay widgets — products like accessiBe, UserWay, and similar tools — are JavaScript plugins that attach a toolbar to your website. They typically offer options for users to increase font size, adjust contrast, or activate screen reader modes.
The appeal is obvious. They are cheap, fast to install, and come with bold claims about instant compliance. The problem is that these claims are fundamentally misleading.
Why Overlays Fall Short
- They do not fix the underlying code. WCAG 2.0 Level AA compliance requires that your HTML, CSS, and content structure be built accessibly from the ground up. An overlay sits on top of broken code — it does not repair it.
- Screen readers often ignore them. Users who rely on assistive technologies like JAWS or NVDA interact directly with your website's source code. An overlay toolbar they cannot see or reach does not help them.
- They create new barriers. Multiple accessibility researchers and disability advocates have documented cases where overlays actively interfered with assistive technology, making sites harder to use for people with disabilities.
- They do not satisfy a legal audit. Ontario's AODA compliance is assessed against WCAG 2.0 Level AA criteria. An automated overlay cannot remediate issues like missing form labels, poor heading structure, inadequate keyboard navigation, or inaccessible PDFs.
The National Federation of the Blind, WebAIM, and hundreds of accessibility professionals have signed open letters stating clearly that overlay products do not and cannot make a website compliant.
The Real-World Consequences of Getting This Wrong
Beyond regulatory fines, there are practical business consequences to ignoring accessibility:
- Lost customers. Approximately 2.6 million Canadians live with a disability that affects their internet use. These are customers you may be turning away.
- Legal and reputational risk. Ontario's Human Rights Code also protects people with disabilities. Inaccessible websites have been the subject of human rights complaints in addition to AODA enforcement.
- Wasted money. Businesses that paid monthly subscription fees for overlay tools believing they were protected discovered — often after an audit or complaint — that they were not.
What Genuine AODA Compliance Looks Like
True compliance requires a structured, ongoing approach:
- Accessibility audit — A professional review of your site against WCAG 2.0 Level AA criteria, identifying specific failures
- Remediation — Fixing issues in the actual code, content, and structure of your website
- Accessible content practices — Writing alt text for images, using proper heading hierarchy, ensuring videos have captions
- Accessibility statement — Publishing a clear statement on your site about your commitment and contact method for accommodation requests
- Ongoing monitoring — Accessibility is not a one-time fix; new content and updates must be reviewed regularly
None of these steps can be replaced by a widget.
Start With a Clear Picture of Where You Stand
The first step toward genuine AODA compliance is understanding exactly what needs to be fixed on your current site. You cannot solve a problem you have not measured.
Run a free AODA accessibility scan of your website today. In minutes, you will receive a plain-language report showing where your site falls short of WCAG 2.0 Level AA requirements — no technical background needed. From there, you can make informed decisions about remediation without spending money on tools that offer false protection. Start your free scan now and take your first real step toward compliance.