What Ontario Law Actually Requires
If your business operates a public-facing website in Ontario, you likely have legal obligations under the Accessibility for Ontarians with Disabilities Act (AODA). Specifically, Ontario Regulation 191/11 — the Integrated Accessibility Standards Regulation — sets out clear requirements for digital content. Organizations with one or more employees must meet WCAG 2.0 Level AA standards for their websites and web content, with deadlines that have already passed for most businesses.
In plain terms, this means your website must be usable by people with visual, auditory, motor, and cognitive disabilities. That includes screen reader compatibility, sufficient colour contrast, keyboard navigation, and more. Ignoring these requirements isn't just a legal risk — it means a meaningful portion of your customers simply cannot use your site.
Why This Matters Beyond Compliance
Approximately 2.6 million Ontarians live with a disability. Many of them are your customers, employees, or potential clients. An inaccessible website doesn't just expose you to complaints filed with the Accessibility Directorate of Ontario — it actively turns away business.
Non-compliance can result in inspections, compliance orders, and fines up to $100,000 per day for corporations under the AODA. While enforcement has been gradual, the Ontario government has signalled increasing scrutiny, particularly for organizations with 50 or more employees. More importantly, accessibility improvements almost always benefit all users — faster load times, cleaner layouts, and better mobile experiences tend to follow.
Understanding WCAG 2.0 Level AA
WCAG stands for Web Content Accessibility Guidelines, published by the World Wide Web Consortium (W3C). Level AA is the middle tier — it's practical to achieve without redesigning your entire site, yet comprehensive enough to address most barriers disabled users encounter.
The guidelines are organized around four principles. Your content must be:
- Perceivable — users can see or hear the information (e.g., images have alt text, videos have captions)
- Operable — users can navigate using a keyboard alone, and have enough time to interact
- Understandable — content is readable, predictable, and forms give clear error messages
- Robust — the site works with assistive technologies like screen readers
Practical Steps to Test Your Website
You don't need to be a developer to start evaluating your site. Here's a straightforward process you can begin today.
Step 1: Run an Automated Scan
Automated tools catch roughly 30–40% of WCAG issues quickly and at no cost. Reliable free tools include:
- WAVE (wave.webaim.org) — paste your URL and get a visual overlay of errors and alerts
- axe DevTools — a browser extension for Chrome or Firefox that flags issues by severity
- Google Lighthouse — built into Chrome's developer tools under the "Accessibility" tab
Look for errors (critical failures) versus warnings (things worth reviewing). Common findings include missing image alt text, low colour contrast, and unlabelled form fields.
Step 2: Check Colour Contrast Manually
WCAG 2.0 Level AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. Use the WebAIM Contrast Checker (webaim.org/resources/contrastchecker) to input your text and background colours. Your brand colours may look attractive but still fail this test.
Step 3: Navigate With Only a Keyboard
Unplug your mouse and try to use your own website using only the Tab, Enter, Escape, and Arrow keys. Can you reach every menu item? Can you complete a contact form? If you find yourself stuck, your users who rely on keyboards or switch devices will be stuck too.
Step 4: Test with a Free Screen Reader
Download NVDA (free for Windows) or use VoiceOver (built into Mac and iPhone). Navigate your homepage and one or two key pages. Listen for whether images are described, whether headings make sense in sequence, and whether form inputs are announced correctly.
Step 5: Review Your PDFs and Documents
Ontario Regulation 191/11 covers documents too. If you post PDFs — menus, price lists, application forms — they also need to be accessible. Use Adobe Acrobat's built-in accessibility checker to identify issues.
The Real Cost of Doing Nothing
Businesses that skip accessibility testing often discover the problem through a formal complaint to the Accessibility Directorate. At that point, you're required to remediate the site under a compliance order, often under a tight timeline and with external scrutiny. Proactive testing is significantly less disruptive and less expensive than reactive remediation.
More practically, an inaccessible website communicates — unintentionally — that certain customers aren't welcome. That's a reputational consequence that no fine schedule fully captures.
Take the First Step Today
Testing your website doesn't require a big budget or a technical team. A free automated scan takes less than five minutes and gives you an immediate picture of where your site stands. Run a free AODA compliance scan on your website today to identify your highest-priority issues, understand your obligations under Ontario Regulation 191/11, and start making improvements that open your business to every customer in Ontario. The sooner you begin, the simpler the path to compliance.