Most small business owners have never heard of AODA. Some have heard the name but assume it applies to physical spaces, ramps, door widths, that kind of thing. Very few know it has anything to do with their website.
The short answer: Ontario’s AODA requires public sector organizations and private businesses with 50 or more employees to make their public websites meet the WCAG 2.0 Level AA accessibility standard. If you have fewer than 50 employees, you have no legal WCAG obligation for your site, but accessibility still costs you real customers, and separate reporting rules may still apply to you. Here’s what that actually means.
What AODA is
The Accessibility for Ontarians with Disabilities Act is Ontario legislation that sets accessibility standards across a range of areas, customer service, employment, and yes, the web. The web-specific requirements are part of the Integrated Accessibility Standards Regulation (IASR) and reference an international standard called WCAG 2.0 Level AA.
The short version: if you operate a business in Ontario and have a website, that website is expected to meet a baseline accessibility standard. The requirements have been phased in over time, and enforcement has been inconsistent, but the law exists, and the direction it’s moving is toward broader enforcement, not less.
Who the AODA website requirements apply to
The web content requirement breaks down by organization size:
- Public sector organizations: must meet WCAG 2.0 Level AA, and have for years.
- Private businesses and non-profits with 50 or more employees: legally required to make all public websites meet WCAG 2.0 Level AA (since January 1, 2021).
- Businesses with fewer than 50 employees: the WCAG website standard does not legally apply to you.
So if you run a small business with a team under 50, the letter of the web content standard doesn’t require you to meet WCAG. That’s the honest answer, and a lot of “you must be AODA compliant” marketing glosses over it.
Two things keep it relevant anyway. First, the trend is toward wider coverage as digital accessibility becomes mainstream. Second, and more practically: accessibility problems hurt real customers today, regardless of what the law says.
The reporting rule is separate (and catches smaller businesses)
There’s a second AODA obligation people confuse with the website standard: the accessibility compliance report. Businesses and non-profits with 20 or more employees must file one with the Government of Ontario by December 31, 2026, and every three years after that. That’s a lower threshold than the 50-employee website standard, so a mid-sized small business can be off the hook for WCAG but still on the hook to report.
What it actually means for your website
WCAG 2.0 AA, the standard AODA references, covers a long list of technical requirements. The ones most commonly failed by small business websites are:
Colour contrast. Text needs to have enough contrast against its background to be readable by people with low vision. Light grey text on a white background is a common failure.
Image alt text. Every meaningful image on your site should have a text description. Screen readers (used by blind and low-vision visitors) read these descriptions aloud. A missing alt text means a blind visitor gets no information about that image.
Keyboard navigation. Your site should be fully navigable with a keyboard alone, no mouse required. This matters for people with motor disabilities and for users of assistive technology.
Form labels. Every form field needs a proper label, not just placeholder text inside the field, which disappears when someone starts typing.
Tap target size. Buttons and links need to be large enough to tap on a touchscreen. Small, closely-spaced links are a common mobile accessibility failure.
Video captions. If you have video on your site, it needs captions for deaf and hard-of-hearing visitors.
Why this matters beyond legal compliance
The legal angle gets people’s attention, but the practical reason to care about accessibility is simpler: accessibility problems are customer experience problems.
Older visitors, a significant and growing share of most local markets, often struggle with low-contrast text, small buttons, and sites that don’t behave consistently. People on lower-end phones encounter many of the same issues. Anyone with a temporary disability (a broken wrist, eye strain from staring at screens all day) hits these barriers too.
When someone can’t use your website, they go to a competitor who has one they can use. That’s a lost customer you never knew you had.
Where most small business sites fall short
The most common failures I see in audits:
- Low text contrast, especially popular “modern” designs with light grey text
- Missing alt text on photos
- Form fields with no real labels
- Hamburger menus and dropdowns that don’t work with keyboard navigation
- Buttons that are too small to tap reliably on mobile
None of these are hard to fix. They just require someone to actually check for them, which most designers don’t, unless accessibility is explicitly part of their process.
What to do
If you want to know where your site stands, run it through the free website audit. I include an accessibility check as part of every audit. You’ll see your score and a plain-English explanation of what’s failing. (Accessibility is one of the four things Google’s Lighthouse score grades, too.)
All sites I build are designed to WCAG 2.1 AA standard from the start. It’s not an add-on, it’s part of how I build. That means you’re covered under AODA, your site works for every customer, and you’re not quietly losing business to barriers most owners never see.
If you’re not sure where your current site stands, run a free website audit. It flags the accessibility issues above in plain English, alongside your speed and SEO scores.