Why Ontario Businesses Are Rethinking Their Accessibility Widgets
If you've been using UserWay or a similar overlay widget to meet your web accessibility obligations, you're not alone — and you're not necessarily doing anything wrong. But there's growing evidence that these tools fall short of what Ontario law actually requires. For small and medium-sized businesses in the province, understanding the gap between a quick-fix widget and genuine AODA compliance could save you from complaints, legal exposure, and lost customers.
What Ontario Law Actually Requires
The Accessibility for Ontarians with Disabilities Act (AODA) sets out clear obligations for businesses operating in Ontario. Specifically, Ontario Regulation 191/11 — also known as the Integrated Accessibility Standards Regulation (IASR) — requires that websites and web content conform to the Web Content Accessibility Guidelines (WCAG) 2.0 Level AA.
Here's what that means in plain language:
- If your organization has 50 or more employees, your public-facing website and web content must already meet WCAG 2.0 Level AA
- If you have 1 to 49 employees, you must still ensure your internet and intranet websites conform to these standards
- These requirements apply to new and significantly refreshed websites under specific timelines
WCAG 2.0 Level AA covers a wide range of accessibility needs — screen reader compatibility, keyboard navigation, sufficient colour contrast, accessible forms, and much more. It's a technical standard, and meeting it properly requires more than a floating toolbar added to your site.
The Problem with Overlay Widgets Like UserWay
Accessibility overlay widgets are tools that inject a layer of code onto your website, offering users options like larger text, high contrast, or screen reader enhancements. They're easy to install and often marketed as an immediate compliance solution.
The reality is more complicated.
Why Overlays Often Fall Short
- They don't fix the underlying code. If your website has inaccessible markup, missing alt text, or broken keyboard navigation, an overlay masks these issues rather than resolving them
- Screen reader users frequently report conflicts. Overlays can interfere with assistive technologies that people already use, sometimes making websites *harder* to navigate
- They don't satisfy WCAG 2.0 Level AA on their own. Regulators and accessibility auditors evaluate the actual source code and user experience — not what a widget claims to fix
- Legal exposure remains. Several organizations have faced complaints and legal action even while using overlay products
More than 750 accessibility professionals signed an open letter specifically calling out overlays as insufficient. Ontario's compliance framework doesn't make exceptions for them.
What Canadian Businesses Should Use Instead
The good news is that genuine accessibility doesn't have to be overwhelming. Here's a practical path forward.
1. Start with a Proper Accessibility Audit
Before spending money on fixes, understand where you actually stand. A credible audit reviews your website's code, content, and user flows against WCAG 2.0 Level AA criteria. This gives you a prioritized list of real issues to address — not a generic report.
2. Work with a Developer Who Understands WCAG
Make sure the person building or maintaining your website knows what semantic HTML, ARIA labels, and keyboard accessibility mean. Ask specifically whether they have experience with WCAG 2.0 Level AA. This is increasingly a standard expectation for web development in Ontario.
3. Use Accessible Design Principles from the Start
The most cost-effective approach is building accessibility in rather than layering it on top. This means:
- Choosing website themes and templates built with accessibility in mind
- Ensuring all images have descriptive alt text
- Using proper heading structures (H1, H2, H3)
- Making sure forms have clear labels
- Checking that colour contrast meets the minimum 4.5:1 ratio for normal text
4. Test with Real Users and Real Tools
Free tools like WAVE and axe DevTools can identify many common accessibility issues. Even better, test your site with someone who uses a screen reader. Automated tools catch roughly 30–40% of issues — human review catches the rest.
What Happens If You Ignore This
The Accessibility Directorate of Ontario has the authority to audit businesses and issue compliance orders. Organizations found in violation can face fines up to $100,000 per day for corporations and $50,000 per day for individuals or unincorporated organizations.
Beyond the legal risk, consider this: approximately 2.9 million Ontarians live with a disability. An inaccessible website isn't just a compliance issue — it's a barrier that costs you customers who are actively looking to spend money with businesses they can actually use.
The Bottom Line
UserWay and similar tools have a role to play as a supplemental feature, but they are not a compliance strategy on their own. Ontario Regulation 191/11 is clear: your website needs to meet WCAG 2.0 Level AA, and that requires real technical work, not a widget.
The businesses that get this right gain customer trust, reduce legal risk, and reach a broader audience — all at the same time.
Ready to find out where your website actually stands? Run a free AODA accessibility scan today and get a clear picture of what needs attention. It takes minutes and gives you the starting point for a compliance plan that actually holds up.