
⚡ Quick answer: Under Ontario’s Integrated Accessibility Standards (O. Reg. 191/11), private businesses and non-profits with 50 or more employees in Ontario must make their public websites conform to WCAG 2.0 Level AA, with two exceptions: live captions and pre-recorded audio description. The deadline for all such websites was January 1, 2021. Smaller organizations are not covered by the website rule itself, but every organization with at least one employee in Ontario must still provide information in an accessible format on request.
Below is what the official Ontario sources actually say about AODA website compliance, followed by a plain-English checklist you can work through with free tools, and notes on fixing common problems in WordPress.
This article is general information, not legal advice. If your situation is unusual (for example, you are unsure how to count employees or whether a web application is covered), check with a lawyer who works with the AODA.
The Accessibility for Ontarians with Disabilities Act, 2005 (AODA) sets the framework, and the detailed rules live in Ontario Regulation 191/11, the Integrated Accessibility Standards. Section 14 of that regulation covers websites. It defines a “large organization” as one with 50 or more employees in Ontario, and a “small organization” as one with at least one but fewer than 50 employees in Ontario (Source).
The website requirement in section 14 applies to the Government of Ontario, the Legislative Assembly, designated public sector organizations, and large organizations. In practice, for a private company it comes down to headcount:
| Organization in Ontario | Public website must meet WCAG 2.0 AA? | Accessibility compliance report? | Accessible formats on request? |
|---|---|---|---|
| 1–19 employees | Not required by section 14 | Not required | Yes |
| 20–49 employees | Not required by section 14 | Yes, every three years | Yes |
| 50+ employees | Yes, since January 1, 2021 | Yes, every three years | Yes |
| No employees in Ontario | Exempt | Exempt | Exempt |
Ontario counts full-time, part-time, seasonal and contract workers as employees, but not volunteers or independent contractors, and states that you are exempt if you do not have employees in Ontario (Source).
One detail that catches people out: the obligation sits with the organization that controls the website, “directly or through a contractual relationship that allows for modification of the product”. If an agency or freelancer built your site but you can ask them to change it, it is still your site for AODA purposes (Source).
The regulation names WCAG 2.0, the Web Content Accessibility Guidelines published by the W3C. For large private organizations the schedule was:
Both dates come straight from section 14(4) of O. Reg. 191/11 (Source). Both deadlines have passed, so if your organization has 50+ employees in Ontario, there is no grace period left: the requirement is in force now.
A few scope notes from the official guidance:
For private organizations, two WCAG 2.0 AA success criteria are carved out: 1.2.4 Captions (Live) and 1.2.5 Audio Descriptions (Pre-recorded) (Source). So you do not have to caption live streams or add a narrated description track to recorded video, but pre-recorded video with sound still needs captions (Level A, 1.2.2).
The law says 2.0, but the W3C has since published WCAG 2.1 (2018) and 2.2 (2023). According to the W3C, “content that conforms to WCAG 2.2 also conforms to WCAG 2.1 and WCAG 2.0”, with one exception: success criterion 4.1.1 Parsing is obsolete in 2.2 (Source). Building to 2.1 or 2.2 AA therefore covers the AODA baseline and gets you closer to the standards used in other markets.
Businesses and non-profits with 20 or more employees must file an accessibility compliance report every three years, and Ontario lists the current reporting deadline as December 31, 2026 (Source). As of November 2026, that is weeks away. Organizations with 50+ employees also need a documented multi-year accessibility plan, posted on their website and reviewed at least once every five years (Source).
On penalties, Ontario’s reporting page warns that if you do not comply “you could face enforcement measures which can include financial penalties” (Source). The amounts are set in two places:
Those maximums apply to specific offences, not to a missing alt attribute. For most businesses the realistic risk is an audit, an order to fix the site, and the cost of a rushed remediation.
WCAG has dozens of success criteria. The items below are the ones that come up on almost every small-business site we review. The criterion numbers are from WCAG 2.0 (Source).
| Check | WCAG 2.0 criterion | What “pass” looks like |
|---|---|---|
| Alt text on images | 1.1.1 (A) | Meaningful images describe their purpose; decorative ones have empty alt so screen readers skip them |
| Colour contrast | 1.4.3 (AA) | Body text at least 4.5:1 against its background; large text at least 3:1 |
| Keyboard access | 2.1.1 (A) | Menus, sliders, pop-ups and forms all work with Tab, Enter, Space and arrow keys |
| Visible focus | 2.4.7 (AA) | You can always see which link or button is selected when tabbing |
| Form labels | 3.3.2 (A) | Every field has a visible label, not just placeholder text that disappears |
| Headings and structure | 1.3.1 (A) | One H1 per page, logical H2/H3 order, lists marked up as lists |
| Captions on video | 1.2.2 (A) | Pre-recorded videos with sound have accurate captions, not just auto-generated ones left unedited |
| Text resize | 1.4.4 (AA) | Page still works when text is zoomed to 200% |
| Page language | 3.1.1 (A) | The HTML declares the page language (for example, lang=”en-CA”) |
| PDFs and documents | Same criteria apply | Tagged PDFs with real text, headings and alt text, or an accessible HTML version |
Alt text. Describe what the image does, not what it is. A logo linking home should read “Company name, home page”; icons next to text labels are usually decorative.
Contrast. Light grey text on white and white text on brand-coloured buttons are the usual failures; check buttons and footer links too.
Forms. Error messages should say in text what went wrong, not only turn a border red, and required fields must not be marked by colour alone.
PDFs. Scanned menus and brochures are invisible to screen readers. Export a tagged PDF from the original file, or publish the content as a normal web page.
No automated tool can confirm AODA compliance on its own: tools find missing alt attributes, but cannot tell whether “image123.jpg” is a useful description. Use them for the obvious issues, then test by hand.
Then test manually: tab through your home page, contact form and checkout without a mouse, zoom to 200%, and try a screen reader such as VoiceOver or NVDA.
Most WordPress accessibility problems come from the theme, page builder add-ons and how content is entered, not from WordPress core.
Every plugin adds markup you then have to test, so check our list of WordPress plugins worth knowing before adding more. If the theme itself is the problem (no keyboard menu, hard-coded low contrast), patching may cost more than rebuilding; that is one of the signs covered in when a website needs a redesign.
If you also sell to customers in the European Union, the EU’s European Accessibility Act sets its own rules for certain products and services, including e-commerce. Both point to WCAG, so a site built properly to WCAG AA covers most of the shared ground, but scope, deadlines and enforcement differ. We cover the EU side in Website Accessibility: EAA Requirements and How to Check.
Netloria is a Ukrainian web studio working remotely with Canadian businesses. We are not an AODA certification body, but we build custom WordPress sites to WCAG 2.x AA practices as standard: real heading structure, labelled forms, keyboard-friendly menus, contrast checked against the brand palette, and an editor setup that makes alt text hard to skip. Pricing is fixed and in USD: a corporate website is $1500, a “Landing PRO” page starts from $450, and technical support starts from $100/month. Our evening overlaps with the Canadian business day, so calls happen in your working hours. If you want a second pair of eyes on an existing site or a new build planned around accessibility from day one, start with a free consultation on our website development page for Canadian businesses.
The WCAG 2.0 AA website requirement in section 14 of O. Reg. 191/11 applies to private organizations with 50 or more employees in Ontario. Smaller organizations are not covered by that section, but anyone with at least one employee in Ontario must provide information in an accessible format when a person with a disability asks for it. Building to WCAG AA anyway is the simplest way to meet those requests.
No. Ontario does not certify websites or endorse a specific testing tool. Free tools such as WAVE, Lighthouse and axe DevTools find many technical issues, but meeting WCAG 2.0 AA also requires manual checks such as keyboard navigation and meaningful alt text.
The regulation names WCAG 2.0 Level AA, excluding live captions and pre-recorded audio description. The W3C states that content conforming to WCAG 2.2 also conforms to 2.1 and 2.0 (apart from the obsolete 4.1.1 Parsing criterion), so building to a newer version covers the AODA requirement.
Ontario can use enforcement measures that include administrative penalties, with the amount set by the severity and history of the contravention. For offences under section 37 of the AODA, such as false information in a compliance report or ignoring a director’s order, fines on conviction can reach $50,000 per day for individuals and $100,000 per day for corporations.
For businesses and non-profits with 20 or more employees, Ontario lists the deadline as December 31, 2026, and reports are filed every three years. Organizations with fewer than 20 employees do not file a report but must still meet the requirements that apply to them.
Обговорюємо саме цю послугу у вашому проєкті?
Website Development for Canadian Businesses