AODA and your website: what Ontario businesses actually have to do

Reviewed September 6, 2026.

Every year or two a business owner in Ontario gets an email warning them their website is illegal and offering to fix it for a monthly fee. Some of those emails are from honest companies. Check who sent it and what requirement they claim you have missed before buying anything.

The underlying law is real, though, and there is a filing deadline at the end of this year that catches a lot of businesses by surprise. Here is the plain version: who it applies to, what it actually requires, and what is worth doing even if it does not apply to you.

This is general website guidance, not legal advice or a compliance certification. The linked provincial guidance explains the requirements; get qualified advice where your organization’s obligations are unclear.

What the law says

The Accessibility for Ontarians with Disabilities Act became law in 2005. The part that touches your website lives in the Integrated Accessibility Standards Regulation, and it points at an international technical standard called WCAG, the Web Content Accessibility Guidelines.

For covered organizations, Ontario requires WCAG 2.0 Level AA, except criteria 1.2.4 (live captions) and 1.2.5 (prerecorded audio descriptions). The public website requirements cover content published after January 1, 2012; the compliance date was January 1, 2021. Ontario’s website accessibility guidance explains the scope, control requirements and exceptions.

Who this applies to

For private businesses and nonprofits, employee count changes which requirements apply. Use the peak Ontario employee count during the previous twelve months, including full time, part time, seasonal and contract employees. Exclude outside contractors and staff outside Ontario. Seek advice if employment status is unclear. Ontario’s industry guide explains the count and reporting cycle. Designated public sector organizations have separate requirements.

50 or more employees. The covered public website and content must meet the website standard described above. You also need a written multi year accessibility plan, reviewed at least every five years.

20 or more employees. You must file an accessibility compliance report with the province. Private sector organizations file every three years, and the next deadline is December 31, 2026. The report is a self certification, and the province can audit it.

Fewer than 20 employees. Private businesses and nonprofits below this threshold do not file the report, and those with fewer than 50 employees are outside the specific website requirement described above. You still have obligations: accessible customer service, staff training, providing information in accessible formats when somebody asks, and a feedback process people can actually use.

Being below a reporting threshold does not remove every accessibility obligation. Ontario’s Human Rights Code may also be relevant to access to services. A usable booking form is worth having whether or not the website rule applies to your business.

What the penalties actually look like

The AODA sets maximum fines on conviction of an offence of $50,000 per day for individuals and $100,000 per day for corporations. Directors and officers can also face liability for failing their statutory duty. These are not automatic charges for each website defect. The Act distinguishes inspections, orders, administrative penalties and offences.

Do not assume enforcement happens only after a customer complaint. The province can review compliance and inspect organizations. Missing a required report or ignoring an order deserves attention, even if nobody has complained about the website.

The realistic risks for a small business are more boring and more likely: a missed report deadline that triggers a review, failing an accessibility question in a procurement process, and losing customers who could not use your booking form.

What WCAG 2.0 AA means in practice

The standard is detailed and can feel like a tax form. Here is what it actually means for an ordinary business site, in the order that matters.

Informative images need useful text alternatives. Describe the information or function, not just the filename. Decorative images should be hidden from assistive technology appropriately, such as with an empty alt attribute on an image element.

Text needs enough contrast. WCAG AA generally requires 4.5 to 1 for normal text and 3 to 1 for large text, with stated exceptions. Check the actual foreground and background, including buttons and form states.

Everything has to work with a keyboard. Tab through your own site. If you cannot reach the menu, open the booking form and submit it without touching a mouse, neither can somebody using assistive technology.

You have to be able to see where you are. That outline around a button when you tab to it, a lot of themes delete it on purpose because designers find it ugly. Removing it is a failure.

Form fields need real labels. Placeholder text inside the box is not a label. It disappears the moment somebody types, and screen readers handle it inconsistently.

Headings have to be real headings, in order. H1, then H2, then H3. Not bold text sized up to look like a heading. Screen reader users navigate by heading the way you navigate by scrolling.

Video needs captions. Pre recorded video, anyway. Live captions are one of the two carve outs.

Text must resize to 200% without loss of content or functionality, apart from the stated exceptions for captions and images of text. WCAG’s resize text criterion does not itself ban horizontal scrolling. Reflow is a separate, newer criterion and a useful design target.

Don't rely on colour alone to communicate anything. A form field that turns red with no error text tells a colour blind visitor nothing.

Documents need attention too. Menus, price lists and intake forms can carry accessibility obligations. A scanned image without a usable text layer is difficult for a screen reader to interpret. Consider an accessible web page or properly prepared document rather than assuming a PDF export is sufficient.

Most accessibility failures on small business sites are not access ramps. They are a designer's aesthetic choice that nobody checked.

A word about accessibility overlay widgets

You have seen them: a little accessibility icon in the corner that opens a panel with contrast and font size controls, sold for a monthly fee with a promise of compliance.

A widget is not evidence that the site meets the standard. Test the actual page, forms and keyboard flow. A contrast control cannot fix an unlabelled field or an inaccessible booking calendar on its own. Vendor claims should be checked against the underlying requirements.

Why smaller businesses should care anyway

Statistics Canada’s 2022 Canadian Survey on Disability found that 27% of Canadians aged fifteen and older had a disability. That is 2022 data, not a new 2026 count. Vision, dexterity, hearing and other access needs matter across many customer groups.

There is also a straightforward commercial overlap. Proper headings, real labels, text descriptions on images and readable contrast are the same things that make a site easier for search engines to understand and easier for everybody to use on a phone in the sun. Accessibility work and the nine jobs a local site has to do are largely the same list approached from a different direction.

Where to start if you only have an afternoon. Run your homepage through a free checker like WAVE or Lighthouse. Fix the contrast failures, add text descriptions to every image that carries information, and tab through your booking or contact form with the mouse untouched. These checks can reveal useful starting points. Automated tools do not find every barrier, and a complete review also needs manual testing.

The December deadline

If your private business or nonprofit has twenty or more Ontario employees under the province’s counting rules, put December 31, 2026 in your calendar. Use Ontario’s reporting instructions to prepare. Training records, policies and a plan where required take longer than opening the form.