Website Accessibility and AODA: What Ontario Businesses Actually Have to Do
Most Ontario business owners first hear about AODA from a nervous email: a customer couldn’t use the booking form, or a procurement team asked for an accessibility statement before signing. Suddenly a law you’d filed under “someone else’s problem” is attached to a sale. The good news is that the website side of AODA is narrower and more mechanical than the panic suggests.
This guide explains what the legislation points at, what that means for the pages you actually ship, and how to get a site into defensible shape without rebuilding it. It is general guidance, not legal advice. Your specific obligations depend on your organisation’s size and sector, so confirm them against the current regulation or with counsel before you rely on any summary, including this one.
What does AODA actually require of a website?
The Accessibility for Ontarians with Disabilities Act is a framework law. The detail lives in the Integrated Accessibility Standards Regulation, and the part that touches websites is the information and communications standard. Rather than inventing its own technical rules, that standard points at an external benchmark: the Web Content Accessibility Guidelines, WCAG 2.0, at conformance Level AA.
That reference matters more than anything else you’ll read about AODA. It means the question “is my site compliant?” reduces to “does my site meet WCAG 2.0 Level AA?” — a published, testable standard maintained by the W3C, with documented success criteria you can work through one at a time.
Two structural points are worth knowing. First, the obligations scale with organisation type and size: public sector bodies, large private organisations and small private organisations are treated differently, and some requirements apply only above certain thresholds. Second, the regulation carves out specific exceptions, including live captions and pre-recorded audio descriptions, and content published before the standard took effect. We’re deliberately not quoting employee counts, dates or penalty figures here, because those are exactly the details that get misremembered in blog posts and then repeated. Check the regulation text for your own category.
What does WCAG 2.0 Level AA mean in practice?
WCAG is organised around four principles: content must be perceivable, operable, understandable and robust. Strip away the vocabulary and the Level AA criteria mostly come down to a handful of engineering habits.
- Text alternatives. Every image that carries meaning needs alt text that conveys the same information. Decorative images get an empty alt attribute so screen readers skip them.
- Keyboard operability. Everything you can do with a mouse must be doable with a keyboard alone, in a sensible order, with a visible focus indicator. This is where custom dropdowns, sliders and modal windows usually fail.
- Colour contrast. Body text needs sufficient contrast against its background, and large text a somewhat lower ratio. Pale grey on white is the single most common failure on otherwise well-built brochure sites.
- Structure and labels. Headings in order, lists marked up as lists, form fields tied to real labels, and tables with proper header cells. Screen readers navigate by structure, so visual-only hierarchy is invisible to them.
- Resizing and reflow. Text has to stay readable when the user enlarges it, without content overlapping or getting clipped.
- Video and audio. Pre-recorded video with speech needs captions. If you can’t caption it, don’t publish it.
- Error handling. When a form rejects an entry, the message must be available as text, identify which field failed, and say what to do about it.
None of this is exotic. It’s largely what careful front-end development looks like anyway, which is why accessibility is cheapest when it’s part of the build rather than a remediation project. Our web development work treats these as build-time requirements rather than an afterthought.
Where do most Ontario business websites fail?
In our experience the failures cluster in predictable places, and they’re rarely in the hand-written body copy. They’re in the interactive parts, because that’s where a theme or plugin has made decisions on your behalf.
Contact and booking forms are the worst offenders: placeholder text used instead of labels, required fields signalled only by colour, and validation errors that appear visually but are never announced. Navigation menus that open on hover and can’t be reached by keyboard are close behind. Image carousels that auto-advance, PDFs scanned as images with no text layer, and cookie banners that trap keyboard focus round out the list.
How do you test a site without hiring a specialist?
Start with the free tools, then stop trusting them. Automated checkers reliably catch contrast failures, missing alt attributes, unlabelled form fields and broken heading order — a meaningful share of issues, but nowhere near all of them. They cannot judge whether alt text is accurate or whether a keyboard journey makes sense.
- Run an automated scan on your highest-traffic pages: home, services, contact, and whichever page carries your conversion form. Browser extensions built on the open-source axe engine are a reasonable starting point.
- Unplug your mouse and complete your own primary conversion path using Tab, Shift+Tab, Enter and the arrow keys. If you lose track of where focus is, so will everyone else.
- Zoom the browser to 200 per cent and read a service page. Watch for text that’s clipped, overlapped or pushed off-screen.
- Turn on a screen reader — VoiceOver on macOS, Narrator on Windows, both built in — and listen to your home page. It’s uncomfortable the first time and extremely informative.
- Document what you find with the page, the criterion and a proposed fix. That log becomes your remediation plan and your evidence of good faith.
Is it cheaper to remediate or rebuild?
It depends almost entirely on where the failures originate. If the problems are in content — alt text, heading structure, link wording, uncaptioned video — remediation is the obvious answer, and most of it is work your own team can do. If the failures are baked into a page builder, a purchased theme or a stack of plugins that generate inaccessible markup, you’ll fight the same battle on every new page you publish.
The honest test is this: can your team publish a new, accessible page next week using the tools you have, without developer help? If yes, remediate. If every new page reintroduces the same failures, you’re paying rent on a bad foundation. For reference, our web design engagements start at CAD 500 for a Starter Website of up to five pages and CAD 1,500 for a Business Website of up to fifteen, which is often less than a long remediation project on a site that will never quite get there.
Does accessibility help anything besides compliance?
Yes, and the mechanism is straightforward rather than magical. The same markup that lets a screen reader understand your page — real headings, labelled fields, descriptive link text, semantic lists and tables — is the markup that search crawlers and AI answer engines parse to work out what your page is about. Clean structure is a shared dependency, which is why accessibility work and AI visibility work keep landing on the same tickets.
Treat it as a standing practice rather than a project. Add an accessibility line to your publishing checklist, re-test your conversion paths after any theme or plugin update, and keep a dated record of what you’ve checked. If you want a second pair of eyes on where your site stands, start a project and we’ll walk the critical paths with you.
Frequently asked questions
Does AODA apply to my small business website?
The information and communications requirements apply differently depending on whether you’re a public sector organisation, a large private organisation or a small one, and some requirements apply only above certain size thresholds. Rather than guessing, check which category you fall into under the Integrated Accessibility Standards Regulation and confirm your obligations with counsel if a contract or tender depends on the answer.
Which WCAG version does AODA reference?
AODA’s information and communications standard references WCAG 2.0 at Level AA. Later versions, WCAG 2.1 and 2.2, add criteria on top of 2.0 and are generally backwards-compatible, so building to a newer version typically satisfies the 2.0 Level AA requirement as well.
Will an accessibility overlay widget make my site compliant?
No. Overlay widgets that bolt a floating accessibility menu onto an existing page can adjust some surface properties, but they can’t repair inaccessible markup, unlabelled form fields or keyboard traps in the underlying code. Fix the source; don’t paper over it.
How often should we re-test accessibility?
Re-test your primary conversion paths after any theme update, plugin addition or template change, and run a fuller review on a set cadence — quarterly is a reasonable default for a site that publishes regularly. Accessibility regresses quietly, usually through a plugin that changed how a form renders.
Get the next one in your inbox.
Practical insights — no fluff, straight to your inbox.
Or follow us on LinkedIn:
Follow StrategyPeeps






