Under the Accessibility for Ontarians with Disabilities Act (AODA), your public website must meet WCAG 2.0 Level AA if you are an Ontario public sector organization, or a private business or non-profit with 50 or more employees in Ontario. Organizations with fewer than 50 employees don’t have a website requirement, though making your site accessible is still worth doing.
This guide explains who the rule applies to, what it requires, and how to tell whether your site meets it. It’s a plain-language overview, not legal advice.
Who has to comply
The website requirement comes from the Integrated Accessibility Standards Regulation under the AODA. It applies to:
- The Government of Ontario and the Legislative Assembly.
- Designated public sector organizations, such as municipalities, school boards, colleges, universities, and hospitals.
- Large organizations: businesses and non-profits with 50 or more employees in Ontario.
Small organizations with 1 to 49 employees have other AODA obligations, such as accessible customer service, but are not required to meet the website standard.
What the website standard requires
Covered organizations must make their public websites and web content conform to WCAG 2.0 Level AA. WCAG, the Web Content Accessibility Guidelines, is the international standard for accessible websites. Two criteria are exempt under the AODA: live captions and pre-recorded audio descriptions.
The rule covers your public website and web content posted after January 1, 2012. In practice, WCAG 2.0 AA means things like:
- Text has enough colour contrast against its background.
- Every image that conveys information has meaningful alt text.
- The whole site can be used with a keyboard alone, with a visible focus indicator.
- Forms have proper labels and clear error messages.
- Headings and page structure make sense to screen readers.
- Videos have captions.
- Content doesn’t rely on colour alone to convey meaning.
What happens if you don’t comply
Covered organizations must file accessibility compliance reports with the Ontario government. The AODA allows administrative penalties, and the Act sets maximum fines of up to $100,000 per day for corporations convicted of an offence. Beyond penalties, an inaccessible site turns away customers who use screen readers, keyboards, or magnification, and can lead to complaints.
Why WCAG 2.2 AA is the safer target
The AODA references WCAG 2.0, but the guidelines have since been updated to versions 2.1 and 2.2. Each version adds criteria on top of the previous one, mostly for mobile users and people with cognitive disabilities. Meeting WCAG 2.2 AA covers everything in 2.0 AA, so auditing against 2.2 means you meet the AODA requirement with room to spare.
How to check your website
- Run an automated scan with a free tool such as WAVE or Lighthouse. This catches some issues, like missing alt text and low contrast.
- Test with a keyboard. Press Tab through your pages, menus, forms, and checkout. Can you reach and use everything, and can you always see where you are?
- Try a screen reader, such as NVDA on Windows or VoiceOver on Mac, on your key pages.
- Review forms and media for labels, error messages, and captions.
- Document what you tested and fixed so you have a record.
Automated tools only catch part of the problems, so manual testing matters.
Need an accessibility audit?
We audit WordPress and Shopify sites against WCAG 2.2 AA, fix the issues in the code, and give you a report to keep on file.
A note on accessibility overlay widgets
Some products promise instant compliance with a script that adds an accessibility toolbar to your site. Overlays can’t fix underlying code problems like missing form labels, poor heading structure, or keyboard traps, and many people who rely on assistive technology find them harder to use. Real compliance comes from fixing the site itself.
Frequently asked questions
Does the AODA apply to small businesses?
Businesses and non-profits with fewer than 50 employees in Ontario don’t have to meet the AODA website standard, although they have other obligations such as accessible customer service.
Is WCAG 2.0 or WCAG 2.1 required under the AODA?
The AODA requires WCAG 2.0 Level AA, excluding live captions and pre-recorded audio descriptions. Meeting WCAG 2.1 or 2.2 AA covers 2.0 AA as well.
Do PDFs on my website need to be accessible?
Web content includes documents posted on your website, so PDFs published after January 1, 2012 should be accessible or available in an accessible format on request.
Does an accessibility overlay make my site AODA compliant?
No. Overlays don’t fix the underlying code issues WCAG tests for. Compliance requires fixing the site’s structure, forms, contrast, and navigation.
Stratus Web Care · Toronto
Need a hand with your website?
We build, maintain, repair, and optimize WordPress and Shopify sites for Toronto businesses. Book a free 30-minute consultation, or read more about our AODA accessibility audits service.