AODA website compliance: what the law actually requires

On December 31, 2026, every Ontario business and non-profit with 20 or more employees owes the province an accessibility compliance report. The last one was due three years ago, which is long enough for most of us to have forgotten what the rules say about our websites.

AODA website compliance is one of those subjects where the sales pitch is louder than the law. You will hear that every website in Ontario must meet a technical standard by now, that you face a $100,000-a-day fine, and that a widget will fix it by Friday. Each of those claims is wrong in a different way. This article sets out what the regulation actually says, who it covers, what a small law office, dental clinic or accounting practice still owes, and which fixes are worth doing whether or not the law makes you.

What AODA website compliance means

The Accessibility for Ontarians with Disabilities Act, 2005 (AODA) is the statute. The detailed rules sit in a regulation under it, O. Reg. 191/11, the Integrated Accessibility Standards. Section 14 of that regulation is the website rule, and it is shorter than most people expect.

Section 14 borrows its technical standard from outside Ontario. It requires covered organizations to make their websites and web content conform with the World Wide Web Consortium's Web Content Accessibility Guidelines (WCAG) 2.0, the December 2008 version, at Level AA. WCAG is the international standard for whether people with disabilities can use a website: people who are blind and use a screen reader, people who cannot use a mouse, people with low vision, people who are deaf and rely on captions.

WCAG is organized into success criteria, each a testable statement, and each criterion has a level: A is the floor, AA is the middle, AAA is the strictest. The Ontario rule requires Level AA but exempts two AA criteria, under section 14(4): captions on live video (success criterion 1.2.4) and audio description of pre-recorded video (1.2.5).

Who has to meet WCAG 2.0 AA

Here is the part the sales emails skip. Sections 14(1) and 14(2) apply the WCAG requirement to the Government of Ontario, the Legislative Assembly, designated public sector organizations and large organizations. Section 2 of the regulation defines a large organization as one with 50 or more employees in Ontario.

For large organizations, the schedule in section 14(4) had two steps:

• From January 1, 2014, new internet websites and their content had to meet WCAG 2.0 Level A.
• From January 1, 2021, all internet websites and web content had to meet WCAG 2.0 Level AA, except for the two video criteria above.

Both dates are behind us. If your practice has 50 or more people on the Ontario payroll, the WCAG obligation is not a future project. It has applied for almost six years to your public site and everything published on it since January 1, 2012. Section 14(5) does excuse a requirement where meeting it "is not practicable", but that is an exception you would have to justify, not a default.

Two parts of section 14 matter for anyone planning a redesign. Under the definitions in section 14(7), a "new internet website" includes a site on an existing domain "undergoing a significant refresh", so a rebuild counts as new. And under section 14(5)(a), the rule covers websites and web content an organization "controls directly or through a contractual relationship that allows for modification of the product", which means you cannot hand the obligation to your web developer and walk away. If you can tell them to change it, it is yours.

What small organizations still owe

A small organization under the regulation has at least one but fewer than 50 employees in Ontario. Section 14 does not impose the WCAG standard on small organizations. That is the honest answer, and anyone who tells a five-person firm otherwise is selling something.

Small organizations are not off the hook entirely, though. Three other sections reach every business with one or more employees:

• Accessible formats on request (section 12). If a person with a disability asks, you must provide or arrange accessible formats and communication supports, in a timely way, at no more than your regular cost, after consulting the person about what works. You must also tell the public that this is available. Small organizations have been bound by this since January 1, 2017.
• A feedback process (section 80.50). The customer service standard requires every provider of goods or services, small ones included, to have a process for receiving and responding to feedback about how it serves people with disabilities. That process has to be accessible on request, and information about it has to be made public.
• Accessible feedback (section 11). Any feedback process you run has to be accessible on request, and you must tell the public so.

Your website is the obvious place to make both notices. The province's page on accessibility rules for businesses and non-profits lists "including a note on your website" as one way to let people know accessible formats are available. That is a sentence and a contact method in your footer, and it takes ten minutes.

The December 31, 2026 accessibility compliance report

The compliance report is a separate obligation from the website standard, and it catches more firms. According to Ontario's guide to completing your accessibility compliance report, businesses and non-profits with 20 or more employees must file a report every three years, and the next deadline is December 31, 2026.

Read those two thresholds together. A firm with 20 to 49 employees files a report but is not bound by the WCAG website rule. A firm with 50 or more files the report and must meet WCAG 2.0 AA. A firm under 20 does neither, but still owes accessible formats and feedback on request.

Filing is not a formality you can wing. Section 37 of the AODA makes it an offence to give false or misleading information in an accessibility report, or to fail to comply with a director's order. On conviction, the fine can reach $50,000 for each day the offence continues, or $100,000 a day for a corporation. That is where the scary number in the sales emails comes from. It is real, but it attaches to specific offences such as a false report or an ignored order. It does not arrive in the mail because a photo on your homepage lacks alt text.

There is a second route, and it is the one that applies to a breach of the standards themselves. Under section 21(4) of the AODA, a director who finds you have not complied with an accessibility standard can order you to comply, to pay an administrative penalty, or both. Section 83 and Schedule 3 of O. Reg. 191/11 set the amounts. For a corporation they start at $500, run to $15,000, and reach $100,000 a day only where both the impact and the history of the breach are rated major. Those numbers are smaller than the sales emails suggest, but they are not zero.

Firms with 50 or more employees also have to document accessibility policies and post a multi-year accessibility plan on their website, according to the province's page on accessibility rules for businesses and non-profits. If your site has no accessibility page at all, the plan has nowhere to live.

Which WCAG version to build to

The regulation names WCAG 2.0, published in 2008. The W3C has since published WCAG 2.1 and WCAG 2.2. If you are building or rebuilding a site today, build to 2.2.

That is not gold-plating. The W3C says in the WCAG 2.2 recommendation that "content that conforms to WCAG 2.2 also conforms to WCAG 2.0 and WCAG 2.1." Meeting the newer version meets the older one, and it covers things 2.0 never imagined, such as touch targets on phones and focus indicators that are not hidden behind sticky headers. Many of your clients will visit on a phone, so those later criteria are often the ones they actually run into.

What an accessible professional website actually needs

WCAG has dozens of success criteria, and a full audit should test all of them. But the same short list of problems turns up on the websites of law offices, dental clinics, accounting practices and vet clinics alike, because they are built from the same templates and the same habits. If you fix these, you have dealt with most of what a screen reader user or a keyboard user will trip over on a typical practice website.

Images that say what they are

Every meaningful image needs alt text, a short written description that a screen reader reads aloud. "Photo of Dr. Patel at the reception desk" helps. "IMG_4471.jpg" does not, and neither does "dentist dentist Hamilton best dentist", which is how alt text looks when someone wrote it for search engines instead of people. Decorative images, such as a background swirl, should have empty alt text so the screen reader skips them.

This one pays twice. Google's guidance on image SEO best practices says it uses alt text, along with computer vision and page content, to understand what an image is about. We covered the rest of that page-level work in the on-page SEO checklist that actually matters.

A site you can use without a mouse

Put your mouse in a drawer and try to book an appointment on your own website using only the Tab key, Shift-Tab and Enter. You should be able to reach every link, menu and form field in a sensible order, and you should always be able to see where you are, because the focused item is outlined.

Many sites fail this test in the first ten seconds. The menu opens only on hover, or the designer removed the focus outline because it looked untidy, or the booking widget traps the cursor so you can never get out. For someone who cannot use a mouse, any one of those makes the site unusable.

Headings, contrast and readable text

Screen reader users navigate by headings the way sighted readers skim. A page should have one main heading and a logical order of subheadings beneath it, built with real heading tags, not with large bold paragraphs that only look like headings.

Text needs enough contrast against its background. WCAG 2.0 AA asks for a contrast ratio of at least 4.5 to 1 for normal text. Pale grey text on white, which has been fashionable for a decade, often fails. So does white text laid over a busy photograph. The fix is usually a darker grey or an overlay behind the text, and your designer can do it without changing the look of the brand.

Forms that tell people what went wrong

Your contact form and booking form are where clients turn into appointments, which makes them the worst place for a barrier. Every field needs a visible label tied to it in the code, not placeholder text that disappears once someone starts typing. When a field is wrong, the message has to say which field and why, in words. A red border on its own means nothing to someone who cannot see red.

Video, PDFs and the documents you forgot about

Pre-recorded video needs captions. Auto-generated captions are a start, but they turn "Small Claims Court" into something a court would not recognize, so read them before you publish. And the PDFs on your site count as web content. A scanned intake form with no text layer is a picture of words, and a screen reader cannot read a picture. Under section 14(5), content published after January 1, 2012 is in scope for large organizations, so the old brochure from 2015 is too.

Why an overlay widget will not make you compliant

You have probably seen the small round icon in the corner of some websites that opens a panel of accessibility settings. These are called overlays, and several companies sell them as a one-line fix for WCAG compliance.

The United States Federal Trade Commission tested that promise. In January 2025 it brought a complaint against accessiBe, which sold an overlay called accessWidget and claimed it could make any website WCAG-compliant. The FTC alleged that the tool did not make all websites compliant, and that the company "deceptively formatted third-party articles and reviews to appear as if they were independent opinions" without disclosing its material connections to them. On April 22, 2025, the FTC approved a final order requiring accessiBe to pay $1 million and barring it from claiming its automated products can make any website WCAG-compliant without evidence to support the claim.

An overlay sits on top of the website. The problems sit inside it: in the headings, the form labels, the image descriptions and the code that decides what happens when someone presses Tab. A widget that promises compliance in 48 hours is the website equivalent of buying a gym membership and counting it as cardio.

How to check your own site this week

You do not need to commission a formal audit to find out roughly where you stand. Here is a check you can run yourself in an afternoon:

1. Count your employees in Ontario. Under 20, 20 to 49, or 50 and over. That number decides which of the obligations above apply to you.
2. Run the W3C's easy checks. The W3C Web Accessibility Initiative publishes Easy Checks, a first review of web accessibility, covering page titles, alt text, headings, contrast, keyboard access and forms. It is written for non-developers.
3. Do the keyboard test. Mouse in the drawer, then book an appointment or send a message using only the keyboard.
4. Run a free automated scan. Tools such as WAVE flag missing alt text, empty links and contrast errors on any page you paste in. Automated tools catch only part of the problem, so treat a clean scan as a start, not a certificate.
5. Add the notice. Put a short accessibility statement on the site that says accessible formats and communication supports are available on request, and how to ask.
6. Diary the report. If you have 20 or more employees, put December 31, 2026 in the calendar now, and read the province's compliance report guide before December, when everyone else does.

If your staff need the training the regulation requires, the province points to AccessForward, a set of free education modules.

AODA is Ontario law, so the deadlines and thresholds in this article are Ontario's. WCAG is international, and the checks above are worth doing wherever your practice is. A client who uses a screen reader in Vancouver has the same trouble with an unlabelled form as one in Hamilton.

Who fixes it when the developer built it wrong

Under section 14(5), the obligation sits with the organization that controls the website "directly or through a contractual relationship that allows for modification of the product". In practice, that means two things before you sign with any developer.

First, put the standard in the contract. "The site will conform with WCAG 2.2 Level AA" is a sentence a developer can be held to. "The site will be accessible" is not. Our guide to comparing website design quotes with one scope worksheet shows how to line up quotes so that a requirement like this does not quietly disappear from the cheapest one.

Second, make sure you can actually change the site. If your website lives on a platform where only the vendor can edit the templates, the vendor controls whether your headings and form labels ever get fixed, and the regulation still treats the problem as yours. That is one more reason to own your website and its code, which we wrote about in you don't own your website, you're renting it. Accessibility is also not a launch-day task. Every new page, PDF and photo can break it again, which is why it belongs on the list in what website maintenance should include.

Frequently asked questions

Does my small business website have to meet WCAG?

Not under Ontario's website rule if you have fewer than 50 employees in Ontario. Section 14 of O. Reg. 191/11 applies WCAG 2.0 AA to large organizations and the public sector. Every business with at least one employee must still provide accessible formats and communication supports on request, and tell the public they are available, often with a note on the website.

What is the AODA website compliance deadline?

For organizations with 50 or more employees in Ontario, the deadline has passed. Under section 14 of O. Reg. 191/11, all public websites and web content had to meet WCAG 2.0 Level AA from January 1, 2021, apart from live captions and pre-recorded audio description. The separate deadline coming up is the accessibility compliance report, due December 31, 2026 for businesses and non-profits with 20 or more employees, according to Ontario's compliance report guide.

Who has to file an accessibility compliance report in 2026?

Ontario businesses and non-profit organizations with 20 or more employees must file an accessibility compliance report every three years, and the current deadline is December 31, 2026. The province publishes a step-by-step guide, Completing your accessibility compliance report. Firms with fewer than 20 employees do not file the report but still have other obligations under the Integrated Accessibility Standards.

What happens if my website is not AODA compliant?

A director can order you to comply, and can add an administrative penalty, under section 21(4) of the AODA. For a corporation, penalties start at $500 and reach the $100,000 daily maximum only for major breaches with a major history. Separately, section 37 makes it an offence to give false information in a report or ignore an order, with fines up to $50,000 a day, or $100,000 for a corporation.

Do accessibility overlay widgets make a website compliant?

No. In April 2025 the United States Federal Trade Commission approved a final order requiring accessiBe to pay $1 million after alleging its overlay did not make every website WCAG-compliant as advertised. Accessibility problems live in the site's code and content, such as headings, form labels and alt text, and an add-on layer cannot reliably fix them.

Should I build my new website to WCAG 2.0 or 2.2?

Build to WCAG 2.2 Level AA. Ontario's regulation names WCAG 2.0, but the W3C's WCAG 2.2 recommendation states that content conforming to WCAG 2.2 also conforms to WCAG 2.0 and 2.1. Building to the newer version meets the legal standard and adds criteria for phones and touchscreens, where many of your clients will visit.

If you want a second set of eyes on your site before the December 31 report, book a call with us and we will go through the checks above with you, page by page.