What AODA actually requires of your Ontario business website in 2026

If you run a small business in Ontario, you have probably gotten the email. Some agency or compliance vendor warns that your website must be “AODA compliant” or you face fines of up to $100,000 a day. It is a good scare. It is also, for most small businesses, misleading.

Here is the honest version. The accessibility law that marketing leans on has real teeth, real deadlines, and real penalties. But the specific requirement to make your website conform to a technical accessibility standard does not apply to a business with fewer than 50 employees. If you are a typical GTA small business, AODA does not legally force your website to meet WCAG. That does not mean you should ignore accessibility, and we will get to why. But you deserve to know what the law actually says before someone sells you a fix for a problem you may not have.

What AODA is, and the 2025 goal

AODA is the Accessibility for Ontarians with Disabilities Act, passed in 2005. Its stated goal is to make Ontario accessible for people with disabilities on or before January 1, 2025. The Act itself is a framework. The detailed rules live in a regulation under it called the Integrated Accessibility Standards Regulation (IASR), and within that is the Information and Communications standard, the part that talks about websites.

So when someone says “AODA compliance” about your website, what they technically mean is the web-content rule inside the IASR. That distinction matters, because the web-content rule does not apply to everyone.

The website rule: WCAG 2.0 Level AA, and who it binds

The IASR requires that internet websites and web content conform to the Web Content Accessibility Guidelines (WCAG) 2.0 at Level AA. Even for organizations that must comply, two criteria are carved out: success criterion 1.2.4 (live captions on live video) and success criterion 1.2.5 (audio descriptions for pre-recorded video).

The part the warning emails skip over is the “who.” Per Ontario’s own guidance, this website requirement applies to:

• The Government of Ontario and the Legislative Assembly.
• Designated public sector organizations, which is a defined list including municipalities, school boards, hospitals, colleges, universities, and public transit.
• Large organizations, meaning businesses or non-profits with 50 or more employees.

The compliance deadline for those groups was January 1, 2021. It has already passed. If you are a hospital or a 200-person company, you should already be conforming.

Why most small businesses are exempt

Here is the line the fear-based marketing leaves out. Under AODA, a “small organization” is one with at least one but fewer than 50 employees, and small organizations are exempt from the accessible-website requirement. Ontario’s guidance is explicit that the legal duty to make all public websites accessible falls only on the public sector and on organizations with 50 or more employees.

So if you run a 6-person clinic, a 12-person trades company, or a 30-person retailer, AODA does not legally require your website to meet WCAG 2.0 Level AA. You still have other AODA obligations that scale with your size, such as accessible customer service, training staff, and providing information in accessible formats on request, and businesses with 20 to 49 employees also have to file a compliance report. But the website-conformance rule is not on your list.

Plenty of vendors will quote you for “AODA website remediation” without ever asking how many employees you have. That question is the first thing an honest advisor asks, because for most small businesses it ends the conversation.

What the penalties really look like

The numbers in the scary emails are real, but they are the statutory maximums, not what a corner store gets fined for a missing alt tag. Under the Act, the maximum fine for an individual or unincorporated organization is up to $50,000 for each day an offence occurs, and for a corporation it is up to $100,000 per day. Directors and officers carry their own potential liability.

Two honest caveats. First, those maximums attach to the obligations that apply to you, and the website rule is not one of them if you are under 50 employees. Second, in practice enforcement against very small businesses for web content has been light, focused on compliance reporting and larger organizations rather than auditing the alt text of every small-business homepage in the GTA. We are not telling you the law is toothless. We are telling you the marketing exaggerates the risk for your size of shop.

Why you should do it anyway

This is where we argue against our own headline. Even when AODA does not compel you, building an accessible website is usually still the right call, for reasons that have nothing to do with a regulator:

• The Ontario Human Rights Code still applies. The Code prohibits discrimination based on disability in services, and it has no 50-employee threshold. A website that locks out blind or low-vision users can be a Code problem even when it is an AODA non-issue. It is the broader, quieter obligation that does cover small businesses.
• Accessibility and SEO overlap heavily. Semantic headings, alt text, real link text, keyboard navigation, and proper contrast are the same things that help search engines understand your site. We covered how Google keeps rewarding genuinely usable pages in the March 2026 core update. Accessible markup is not a tax on SEO; it is part of it.
• You reach more customers. Roughly one in five people has a disability. A site that works with a screen reader, on a phone with large text, and without a mouse is simply a site more people can buy from.
• You are future-proofing. If you grow past 50 employees, or ever want to sell to a hospital, a school board, or the province, the website requirement lands on you for real. Building it accessibly now is far cheaper than remediating later.
• It is nearly free if you build correctly from the start. Accessibility is expensive as a bolt-on and cheap as a default. This is the same argument we make in why small businesses deserve better websites: doing it right the first time costs about the same and ages better.

One practical note. AODA references WCAG 2.0, which is now over a decade old. The modern baseline is WCAG 2.1 or 2.2 at Level AA, which adds criteria around mobile, touch targets, and reflow that matter in 2026. If you are going to do this, target 2.1 or 2.2 AA. You satisfy the older 2.0 standard automatically and end up with a better site.

Where we fit

We are a small Toronto studio, and we build accessibility in by default, so for the sites we ship there is usually nothing to “remediate” later. We will also tell you the truth about where you stand: if you are a small business under 50 employees, we will say plainly that AODA does not legally require your website to meet WCAG, and we will not sell you a compliance package you do not need. What we will do is build the accessibility in because it is good for your customers, your search ranking, and your future self.

If you have had one of those compliance-warning emails and want a straight answer about whether it applies to you, send us the details. The first call is free, and you will leave knowing exactly what the law asks of your business and what it does not.