AODA website accessibility requirements in Ontario

This guide is general information about a regulation, not legal advice, and it is not a substitute for advice from a lawyer about your own organization. Accessibility is also sold dishonestly in this market, usually by implying that every Ontario business is legally required to have an accessible website. Most are not. Here is what the rule actually says.

Who the web content rule applies to, and from when

The Accessibility for Ontarians with Disabilities Act sets standards through the Integrated Accessibility Standards Regulation, O. Reg. 191/11. The part about websites is section 14. It requires conformance with WCAG 2.0 Level AA, and it binds two groups: designated public sector organizations of any size, and what the regulation calls large organizations, meaning 50 or more employees in Ontario. The compliance date for Level AA passed on 1 January 2021. It reaches public-facing websites you control, directly or through a contract that lets you change the product, and the web content published on them after 1 January 2012.

Two success criteria are carved out: live captions on live audio, and audio description for pre-recorded video. Everything else in WCAG 2.0 Level AA is in scope. The section also opens with the words "except where meeting the requirement is not practicable", and the regulation sets out what an organization may weigh in deciding that. It is a real qualifier, and it is not a general exemption.

If you have fewer than 50 employees and you are not a public sector organization, the web content standard in section 14 is not pointed at you. Other parts of AODA still are.

What still applies to a smaller business

Being outside section 14 is not the same as being outside the Act. Three obligations reach smaller Ontario employers, and the third one surprises people:

• Accessible formats and communication supports on request. If a customer asks for your information in a format they can use, you have to work with them to provide it in a timely way and at no extra cost. Your website is often where that request starts.
• The customer service standard: accessible service, service animals and support persons, notice of service disruptions, and staff training.
• Accessibility compliance reporting. Businesses and non-profits with 20 or more employees file a report with the province every three years, and the current cycle is due 31 December 2026. The report is a self-certification rather than an audit, and it is shorter for organizations under 50 employees, because fewer of the standards apply to them.

If you are near the 50-employee line, or you bid on public sector, municipal, hospital or school board work, treat the web content standard as a requirement rather than a quality choice. Public sector procurement asks about it, and your buyer is bound by section 14 even when you are not. There is a shorter version of this on the FAQ.

What WCAG 2.0 Level AA actually asks for

The standard reads like a technical document and is usually described in the abstract, which is why people assume it is expensive. In practice, for a five to ten page small business site, it comes down to a short list of concrete things.

• Text has enough contrast against its background: a ratio of at least 4.5 to 1 for normal text, 3 to 1 for large text.
• Every image that carries meaning has alt text that says what it carries. Decorative images are marked as decorative rather than described.
• Everything usable with a mouse is usable with a keyboard alone, with no trap you cannot tab out of, and you can always see which element has focus.
• Every form field has a real label, not just placeholder text, and errors say what went wrong and how to fix it.
• Headings describe structure rather than font size: one H1, then H2s and H3s in order, so a screen reader can navigate the page the way a sighted reader skims it.
• Link text makes sense on its own. "Read the pricing page" works; five links all reading "click here" do not.
• The page has a title that describes it, and the page declares its language.
• Text can be resized to 200 percent without content breaking or disappearing.
• Pre-recorded video has captions. Live captions and audio description are the two criteria Ontario carves out.

Read as a list of design decisions rather than a compliance exercise, most of that is just building the page properly. That is why every site I build targets WCAG 2.2 Level AA whether or not the client is bound by section 14: it is the same afternoon either way, and a site a screen reader cannot read is a site that quietly loses those calls.

The five failures on almost every small business site

These come up so consistently that they are worth checking on your own site this week. Four of the five need no developer.

Brand colors that fail contrast

The single most common failure, and it usually arrives through the brand palette. A pale gold or a mid-gray that looks refined on a designer's monitor fails 4.5 to 1 on body text. The fix is rarely abandoning the color. It is using a darkened version of it for text and keeping the original for backgrounds, borders and large display type.

Images with no alt text, or useless alt text

Empty alt attributes on photos of your work, or alt text reading "image1" or "DSC_0042". A screen reader announces exactly that. Write what the picture shows and why it is there: "Completed kitchen backsplash in a Vaughan home" tells someone something. Purely decorative images should carry an empty alt attribute so they are skipped rather than announced.

Forms with placeholder text instead of labels

A contact form where the field just says "Email" in gray inside the box. The placeholder disappears the moment someone types, so anyone who loses their place has nothing to check against, and some screen readers never announce it at all. Visible labels above the fields, permanently.

Menus and pop-ups that trap the keyboard

Open the mobile menu or a booking pop-up on your own site and try to close it with the Escape key, then tab through it without touching the mouse. If focus escapes into the page behind, or gets stuck inside with no way out, that is a hard failure and it is also just a bug. This one needs a developer.

Headings chosen for size

Three H1s on one page because they all needed to look big, or a section title marked up as bold paragraph text because the real heading was too large. Screen reader users navigate by heading the way you navigate by scrolling. Out-of-order headings turn that into guesswork.

Cheap at design time, expensive at retrofit

Accessibility done during a build costs close to nothing. Choosing an accessible text color takes the same five minutes as choosing an inaccessible one. Writing alt text as you place images adds a minute per image. Labeling form fields properly is the same amount of typing.

Retrofitting is a different job. A palette change late in a project means revisiting every button, every link state and every hover treatment across every page, and someone has to check each one. A rebuilt navigation means re-testing every page it appears on. Nothing about the individual fixes is hard, but they touch everything, which is why an accessibility remediation quote arrives looking like a redesign quote. The cost is not the standard. The cost is doing it twice.

The practical version: if you are rebuilding anyway, get it built to the standard now. If you are not rebuilding, the four non-developer failures above are worth fixing on the site you have. The Toronto website cost guide covers where accessibility sits in a build quote, which is to say it should not be a line item at all.

A word about accessibility overlay widgets

These are the scripts that add a floating accessibility button offering high contrast and larger text. They are marketed as one-line compliance, and they are not that. They sit on top of a page rather than correcting its underlying markup, they cannot reliably supply meaningful alt text or real form labels, and accessibility practitioners and organizations of disabled users have objected to them publicly and at length. Treat a widget as a supplement to a correctly built page at best, never as the fix.

What to do next

Count your employees. At 50 or more, or in the public sector, section 14 applies and the compliance date has passed, so get the site assessed. Between 20 and 49, the web content standard does not bind you but the December 2026 compliance report does. Under 20, none of the reporting applies, and the five failures above are still worth an afternoon because they cost you customers rather than fines.

For the specifics of your own obligations, ask a lawyer. For the site itself, WCAG 2.2 Level AA is the target on every build here rather than a line item you add on, and the AODA and WCAG section of the build page sets out what is included. If you want the site you already have looked at first, the written audit, $49 plus tax, puts it next to three GTA competitors on a phone and lists the fixes in priority order, and accessibility is worth naming as something you want covered when you book it. Not available to businesses billed in Quebec. The pricing page states what a rebuild costs if that is where it lands, and the person doing the work is one operator, which is why the same standard applies to every build.

Accessibility is one part of whether a page works for the person in front of it. The free website scan covers the rest of that first impression. It is not a legal accessibility audit and does not test for compliance.