AODA Requirements: A Guide for Businesses Serving Ontario

Ontario got to digital accessibility earlier than almost anyone. The Accessibility for Ontarians with Disabilities Act — the AODA — became law in 2005, years before most jurisdictions had put web accessibility into writing. If your business serves customers in Ontario, whether you're headquartered in Toronto or shipping there from somewhere else entirely, it's worth understanding what the law actually asks of your website.

The good news: it's more approachable than most people expect, and the work you do for the AODA overlaps almost completely with what other regulations around the world are asking for.

What the AODA is

The AODA is Ontario's framework for making the province accessible to people with disabilities. It covers a lot of ground — customer service, employment, transportation, public spaces — but the piece that matters most for your website is the Information and Communications standard, part of the Integrated Accessibility Standards Regulation.

That standard sets a clear technical baseline for websites: WCAG 2.0 Level AA, the internationally recognized Web Content Accessibility Guidelines. Since January 1, 2021, covered organizations have been required to make their public websites and web content conform to that level, with two narrow carve-outs (live captioning and pre-recorded audio description aren't required).

The requirement applies to public-facing websites and to web content published after January 1, 2012 — so a genuinely archived page from 2009 isn't the priority, but everything your customers actually use today is in scope.

Who's covered

The website requirements apply to:

• Public sector organizations in Ontario, of any size — government, municipalities, schools, hospitals, and similar bodies.
• Businesses and non-profits with 50 or more employees in Ontario.

Two practical notes. First, the employee count is about employees in Ontario — a US company with a small Ontario team may not hit the threshold, but one with a significant Ontario workforce might. Second, smaller organizations aren't off the hook entirely: the AODA's customer service and general requirements still apply to organizations with even one employee, and an accessible website is one of the most direct ways to serve customers with disabilities well. If you're a growing company, building accessibly now is far cheaper than retrofitting when you cross the threshold.

Filing and reporting duties

The AODA isn't purely an honor system. Businesses and non-profits with 20 or more employees in Ontario must file accessibility reports with the province on a recurring cycle — roughly every three years for the private sector, with public sector organizations reporting more frequently. The report is a self-attestation that you're meeting your obligations, signed by someone with authority to bind the organization.

The province can and does follow up. Ontario's accessibility directorate conducts audits, and organizations that misreport or ignore their obligations can face administrative penalties. You don't need to memorize the enforcement details — you need a truthful answer when the form asks whether your website meets the standard, and documented, ongoing work behind that answer.

How the AODA overlaps with WCAG and US rules

Here's the part that should simplify your planning: almost every major accessibility regulation converges on WCAG.

• AODA requires WCAG 2.0 Level AA.
• The US Department of Justice rule for state and local governments under the ADA requires WCAG 2.1 Level AA.
• Europe's requirements, including those flowing from the European Accessibility Act, are built on standards that incorporate WCAG as well.

WCAG 2.0 is the oldest of these baselines, and each newer version is backwards-compatible — a site that meets WCAG 2.1 or 2.2 Level AA also satisfies everything in 2.0 Level AA. So the smart move isn't to build narrowly to Ontario's 2.0 requirement. It's to work toward current WCAG at Level AA, which covers your AODA baseline and positions you for every other market you serve in one effort.

Practical first steps

If Ontario customers matter to your business, here's a realistic sequence:

1. Audit your site against WCAG. You can't report on — or fix — what you haven't measured. An automated audit surfaces the bulk of detectable issues: missing image descriptions, poor contrast, unlabeled form fields, broken heading structure.
2. Prioritize the pages customers actually use. Your homepage, product pages, checkout, and contact flows come first. A Kitchener retailer we'd point to as a typical case found that three templates — product listing, product detail, and cart — accounted for the majority of its issues; fixing those templates improved thousands of pages at once.
3. Fix steadily, with human review. This is where AllAccessible's human-in-the-loop agentic remediation earns its keep: AllAccessible AI drafts fixes for the issues your audit finds, and your team reviews and approves each one before it goes live. You make real progress week over week without handing your site to a black box.
4. Document as you go. Keep records of audits, fixes, and training. When a reporting deadline arrives, you'll have evidence instead of a scramble.

One honest caveat: no tool — ours included — can declare your site "done." Accessibility is ongoing work, and the AODA treats it that way too. What you can do is show steady, verifiable progress against a recognized standard, which is exactly what the law is designed to encourage.

Serve Ontario well, and everyone else too

The AODA's baseline is one of the most achievable in the world, and meeting it makes your site better for every visitor — in Ontario and everywhere else. Start with an audit, see where you stand, and let your team approve the fixes one by one.

Get started with AllAccessible and turn your AODA to-do list into steady, reviewable progress.