Does AODA Apply to Your Website? Ontario Small Business

Short answer: if your business has fewer than 50 employees in Ontario, the AODA website accessibility rule almost certainly does not apply to you. The requirement to meet WCAG 2.0 Level AA falls on public sector organizations and businesses with 50 or more employees. That's the actual regulation, not a loophole.

If you've been scrolling accessibility company websites getting steadily more anxious about fines and deadlines, take a breath. Much of what you're reading is written by people who sell compliance products, and the alarm is doing some work for them.

Here's the honest version — what the law says, what it doesn't, and why I'd still recommend making your site accessible anyway.

Who the website rule actually covers

The AODA's website requirement lives in the Integrated Accessibility Standards Regulation (IASR), section 14. It says designated public sector organizations and large organizations must make their public websites conform to WCAG 2.0 Level AA.

And "large organization" isn't vague marketing language. The regulation defines it: 50 or more employees in Ontario.

So a roofing company with nine people, a dental practice with twelve, a restaurant with twenty — none of them are covered by the website rule. That's most of the businesses I build for, and probably yours.

The deadlines you may have seen are already behind us

This one causes real confusion, because there are dates floating around that sound urgent and aren't.

The website compliance dates were January 1, 2014 (WCAG 2.0 Level A for new sites) and January 1, 2021 (Level AA for all sites). Both applied to those large organizations and public sector bodies. Both are firmly in the past.

If someone is quoting you an upcoming website deadline for a small business, ask them which section of which regulation it comes from. It's a fair question and the answer is usually an uncomfortable silence.

What does apply to smaller businesses

Now the part the "you're exempt, relax" crowd skips. AODA is broader than websites, and plenty of it reaches businesses with as few as one employee:

• Accessible customer service. Businesses with employees are expected to serve customers with disabilities appropriately and to train staff on how to do it.
• Accessible formats on request. If someone asks for your information in a format they can actually use, you're expected to work with them to provide it.
• Compliance reporting. Businesses with 20 or more employees file periodic accessibility compliance reports with the province.

So "the website rule doesn't apply to me" is true. "AODA doesn't apply to me" usually isn't. Those are different sentences and it's worth keeping them separate.

One honest caveat: this is a plain-English summary, not legal advice, and obligations shift with headcount and sector. If you're near the 20 or 50 employee lines, or you're not sure which standards you fall under, confirm your specific duties rather than taking a blog post's word for it — including this one.

Why I'd make your site accessible anyway

Here's where I'll argue against my own headline, because "not legally required" and "not worth doing" are very different things.

Your customers include people with disabilities. Roughly one in five Canadians has one. If your booking form can't be completed with a keyboard, that isn't a compliance problem — it's a customer walking away, and you'll never see it in your analytics.

Accessibility and SEO overlap almost completely. Alt text, proper heading structure, real text instead of text baked into images, sensible link labels, good colour contrast. Every one of those is an accessibility item and a ranking item. You are, genuinely, doing the same work twice with one effort — which is why accessible sites tend to get found more easily.

It's cheap when you build it in, expensive when you retrofit. Fixing contrast and heading structure during a build costs nothing extra. Auditing and repairing a finished site later is a real invoice.

Your headcount can change. Hire your way past fifty and the rule arrives with you.

The parts that are worth doing regardless

You don't need a formal audit to remove most of the friction. These are the ones that matter and cost nothing but attention:

• Real alt text on meaningful images. Describe what it shows, not "image1."
• Proper heading order. One H1, then H2s and H3s in sequence, not chosen by which font size looked nicest.
• Colour contrast that survives daylight. Light grey text on white fails for a lot of people, including anyone outdoors on a phone.
• Keyboard navigation. Try reaching your phone number and your contact form using only the Tab key. If you can't get there, neither can some of your customers.
• Labelled form fields. Placeholder text vanishing the moment someone types is not a label.
• Captions on video. Also handy for the large number of people who watch with the sound off.
• Text as text. Menus, prices and hours locked inside a JPEG can't be read by a screen reader or a search engine. Same problem, two victims.

Free tools like WAVE and axe DevTools will flag most of this in a couple of minutes. They're not a legal certification, but they'll catch the obvious stuff before a customer does.

What it costs

If accessibility is part of the build, the honest answer is close to nothing — it's craft, not a line item. Retrofitting an existing site depends on how it was built: a clean site might need a few hours of contrast and markup fixes, while a heavy page-builder site stacked with plugins can be more work to fix than to rebuild lean.

That's the same maths as most website problems, which we broke down in what a website actually costs in Toronto.

Be sceptical of overlay widgets that promise instant compliance from one line of JavaScript. They have a poor reputation among the people who actually use assistive technology, and they don't fix the underlying markup — they just put a hat on it.

The bottom line

If you have fewer than 50 employees in Ontario, nobody is coming for your website over WCAG. You can stop worrying about that particular deadline, because it was for someone else and it already passed.

But accessible sites are clearer, faster, easier to find, and usable by more of your customers — which is the same list of things a good website was supposed to do anyway. Build it in and it's free. Panic-buy it later and it isn't.

If you'd like a site that's built this way from the start, we'll design you a free demo homepage — proper structure, real text, readable contrast. You see it before you pay a dollar.

Frequently asked questions

Does AODA apply to my small business if I only have a few employees?

Parts of it do, but the website accessibility rule does not. The requirement to meet WCAG 2.0 Level AA applies to public sector organizations and businesses with 50 or more employees in Ontario. Smaller businesses still have obligations around accessible customer service, staff training, and providing information in accessible formats on request.

Do I legally have to make my website AODA compliant?

Only if you are a designated public sector organization or have 50 or more employees in Ontario. Below that threshold there is no legal requirement for your website to meet WCAG 2.0 Level AA, though making it accessible is still strongly worth doing for customers and for search visibility.

What is the deadline for AODA website compliance in Ontario?

The deadlines have already passed. New websites had to meet WCAG 2.0 Level A by January 1, 2014, and all covered websites had to meet Level AA by January 1, 2021. Both applied to public sector organizations and businesses with 50 or more employees. There is no upcoming website deadline for small businesses.

How much does it cost to make a website accessible?

Built in from the start it costs essentially nothing extra, because it is mostly good markup, sensible headings, real text and readable contrast. Retrofitting an existing site varies: a cleanly built site may need only a few hours of fixes, while a heavy page-builder site can cost more to repair than to rebuild.

Do I need WCAG Level A or Level AA for my business website?

The AODA standard for covered organizations is WCAG 2.0 Level AA, which includes Level A. If your business is under 50 employees you are not required to meet either, but Level AA is a sensible target to build toward since it covers the issues that most affect real users, such as contrast, keyboard access and form labels.