Under Ontario’s Accessibility for Ontarians with Disabilities Act (AODA), private and non-profit organizations with 50 or more employees in Ontario must make their public websites and web content conform to WCAG 2.0 Level AA, with limited exceptions such as live captions and pre-recorded audio descriptions. Organizations with 20 or more employees must also file an accessibility compliance report every three years, and the next reporting deadline is December 31, 2026. Smaller businesses are not legally bound by the website rule, but accessible sites reach more customers and tend to perform better in search.
If you have 50+ employees in Ontario, your public website should meet WCAG 2.0 AA now. If you have 20+, plan your compliance report before the end of 2026.
Who the AODA website rule applies to
| Organization | Website requirement | Compliance report |
|---|---|---|
| 1 to 19 employees in Ontario | No mandatory WCAG standard (recommended) | Not required |
| 20 to 49 employees | No mandatory WCAG standard for websites | Required every three years |
| 50+ employees | WCAG 2.0 Level AA for public websites and web content | Required every three years |
| Public sector organizations | WCAG 2.0 Level AA | Separate reporting rules |
Employee counts and obligations are summarized here as of 2026. Confirm the exact rules that apply to your organization with the Government of Ontario or a legal advisor. This article is general information, not legal advice.
What WCAG 2.0 Level AA means in practice
WCAG (Web Content Accessibility Guidelines) is an international standard built on four principles: content must be perceivable, operable, understandable and robust. Level AA is the middle level and the one most laws reference. For a typical business website, it means:
- Images have meaningful alternative text
- Text and buttons have sufficient colour contrast
- Every function works with a keyboard alone
- Forms have visible labels and clear error messages
- Headings follow a logical structure
- Videos have captions
- Content can be zoomed to 200% without breaking the layout
- Links make sense out of context (no “click here” everywhere)
What about businesses outside Ontario?
Other provinces are developing their own accessibility laws, and federally regulated organizations have obligations under the Accessible Canada Act. In Quebec, public bodies follow government web accessibility standards. Private businesses in other provinces are not always legally required to meet WCAG yet, but the standard is the best benchmark wherever you operate. If you sell in Ontario from Quebec or elsewhere, consider building to WCAG AA from the start. It is far cheaper than retrofitting later.
The most common accessibility problems we see
- Low-contrast text, such as light grey on white or text over busy photos
- Missing alt text on product photos, logos and icons
- Unlabelled forms where placeholder text disappears as you type
- Keyboard traps in menus, sliders and pop-ups
- PDFs that are scanned images with no readable text
- Auto-playing carousels that cannot be paused
Many of these issues also slow pages down or confuse search engines. Fixing them often improves performance too; see our guide to improving Core Web Vitals.
Step-by-step AODA website checklist
- Inventory your public web content: pages, forms, PDFs, videos and third-party widgets.
- Run an automated scan to catch obvious issues such as contrast and missing alt text.
- Test manually with a keyboard and a screen reader; automated tools find only part of the problems.
- Prioritize templates: fixing the header, footer and page templates repairs hundreds of pages at once.
- Fix forms and checkout flows first, because they block customers directly.
- Caption videos and replace image-only PDFs with accessible HTML pages where possible.
- Publish an accessibility statement with a contact method for feedback.
- Train content editors so new pages stay compliant.
- Re-test after every redesign or plugin update. Our WordPress maintenance checklist is a good place to add this step.
Are accessibility overlays enough?
Accessibility overlay widgets promise one-line compliance. They can adjust font sizes or contrast, but they do not fix underlying code problems such as unlabelled forms or keyboard traps. Treat them as an extra, not a replacement for real fixes in your theme and content.
Accessibility and bilingual sites
If your site runs in English and French, both versions need to be accessible, and the language of each page should be declared correctly so screen readers pronounce it properly. Our bilingual website best practices cover the language side in detail.
Frequently asked questions
Does AODA apply to my business if I am based in Quebec?
AODA applies to organizations that provide goods, services or facilities in Ontario and have employees in Ontario. If you have staff there, check your obligations.
Is WCAG 2.1 or 2.2 required?
The AODA references WCAG 2.0 Level AA. Newer versions add useful criteria, so building to WCAG 2.1 or 2.2 AA also covers 2.0.
What happens if we do not comply?
The Ontario government can issue orders and administrative penalties. Inaccessible sites also lose customers who cannot complete a purchase or form.
How long does an accessibility fix take?
For a typical small business site, a focused audit and template fixes can often be done in a few weeks, depending on size and complexity.
Conclusion
AODA compliance is a legal requirement for many Ontario businesses and good practice for everyone else. Start with an audit, fix templates and forms first, and keep accessibility in your maintenance routine. Need help? Request a free quote from Loubane.
Website, SEO or marketing: let’s talk about your project
Custom quote, starting at $999 + tax
Free, no-obligation quote. Bilingual agency based in Montreal.
Get my free quote