AODA and Web Accessibility for Ontario Businesses

Compliance · Published September 17, 2026

Ontario's accessibility legislation puts a specific, testable standard on the websites of larger organisations, and a broader duty on everyone else that most businesses have never considered. The technical requirement is less daunting than it sounds, and the handful of failures that make most small business sites unusable are the same handful every time. General information rather than legal advice; the thresholds in particular are worth confirming for your own organisation.

Get a free quoteCall (613) 800-8028

Who actually has to comply

The Integrated Accessibility Standards Regulation sets the website obligation on designated public sector organisations and on large organisations, where large means 50 or more employees in Ontario. Those organisations are required to conform their internet websites and web content to WCAG 2.0 Level AA, with two carve-outs: live captions and pre-recorded audio descriptions are excluded.

Smaller private and non-profit organisations, from one to 49 employees, sit outside that particular requirement. They are not outside accessibility obligations generally: other parts of the regulation apply on their own timelines, and the Ontario Human Rights Code's duty to accommodate does not have an employee threshold at all.

That second point is the one worth sitting with. The Human Rights Code operates independently of the AODA, and a service offered to the public that a person cannot use because of a disability raises a question under it regardless of how many people you employ. The AODA sets a floor with a threshold. The Code does not.

What WCAG Level AA actually asks for

The guidelines are organised under four principles: content must be perceivable, operable, understandable and robust. Level AA is the middle conformance level and the one regulators and procurement processes consistently name. In practice it comes down to a manageable set of properties.

• Every image that carries meaning has text describing it, and decorative images are marked so screen readers skip them.
• Text has sufficient contrast against its background. The Level AA thresholds are 4.5 to 1 for body text and 3 to 1 for large text.
• Everything that works with a mouse works with a keyboard, in a sensible order, with a visible focus indicator, and with no trap that a keyboard user cannot get out of.
• Form fields have labels that are programmatically associated with them, and errors are described in text rather than signalled only by turning a border red.
• Video has captions, and audio content has an alternative.
• Headings describe structure honestly, so a screen reader user can navigate by them rather than reading everything.
• The page works when text is enlarged substantially, and reflows on a small screen without requiring horizontal scrolling.
• Nothing flashes in a way that could trigger a seizure, and moving or auto-updating content can be paused.
• Page language is declared, so a screen reader pronounces the content correctly.

The six failures that account for most of it

Audits of small business sites return the same findings with striking regularity. Fixing these six gets most sites most of the way there.

• Images with no alternative text, or alternative text that says "image" or repeats the filename.
• Light grey text on white, which is a design fashion that fails contrast almost every time it appears.
• Form fields labelled only by placeholder text, which disappears when typing starts and is often not announced at all.
• Buttons and links that are actually styled div elements, invisible to a keyboard and meaningless to a screen reader.
• Link text reading "click here" or "read more", which tells a user listening to a list of links nothing whatsoever.
• Carousels, modals and dropdown menus that cannot be operated or escaped from a keyboard.

How to check

Automated tools catch perhaps a third of real issues and are worth running because that third is cheap to find. Free ones will identify contrast failures, missing alternative text and missing labels in minutes.

The rest needs a person. Two tests find most of what the tools miss, and neither requires expertise: unplug the mouse and complete your most important task, a booking or an enquiry, using only the keyboard. Then turn on the screen reader already built into your operating system and try the same thing. If you cannot finish, neither can your customer.

Avoid accessibility overlay widgets, the scripts that promise compliance from one line of JavaScript. They do not deliver what they claim, disability advocacy organisations have been consistently critical of them, and in the United States they have featured in litigation rather than preventing it.

Why it is worth doing below the threshold

A large share of the adult population has a disability, and a much larger share has an age-related impairment they would never describe that way. Every one of the fixes above also helps someone on a phone in bright sunlight, someone with a cracked screen, or someone who is simply older than the person who designed the site.

The overlap with everything else is also close to total. Proper headings, real buttons, labelled forms and readable contrast are the same things that make a site work for search engines, for assistive technology and for a text-only crawler. Accessibility done during a build costs very little. Retrofitted afterwards it is a project.

Related reading

• PIPEDA: what your website must do
• The Ottawa small business website checklist
• Websites for Ottawa clinics and practices
• Our web development service
• Ottawa web design pricing, published in full
• Ottawa web design by Shinobi Media

Frequently asked questions