AODA Website Compliance: What Actually Applies to Your Business

If you run a business in Ontario, you have probably been told your website is breaking the law.

I am a bilingual web designer based in Hamilton, and over the past year nearly every Ontario client conversation has landed on the same question: does my website really need to be accessible, and what happens if it is not?

The honest answer depends on how many people you employ. That part gets left out of most guides on this subject — usually the ones with an audit for sale at the bottom of the page. So let me start there, then walk you through what the standard actually asks for and how I build accessible sites without a stressful, expensive rebuild.

Does AODA website compliance apply to your website?

The Accessibility for Ontarians with Disabilities Act became law in 2005, with the goal of making the province fully accessible. What it asks of your website depends on the size and type of your organization.

Since January 1, 2021, designated public sector organizations and private businesses or non-profits with 50 or more employees must make their public websites conform to WCAG 2.0 Level AA, along with any web content published after January 1, 2012.

If you have fewer than 50 employees, the Government of Ontario is direct about it: you are not required under the Integrated Accessibility Standards Regulation to meet those website requirements, though you are encouraged to. You can read that on the province’s own guidance page.

That is not the same as being exempt from the AODA. If you employ anyone in Ontario, several obligations apply regardless of your size:

  • Since 2017, you must provide publicly available information in an accessible format when someone asks for it, and let people know that option exists
  • The customer service standard applies to your business, including if you only serve other businesses
  • With 20 or more employees, you must file an accessibility compliance report with the province
  • The Ontario Human Rights Code requires you to accommodate people with disabilities, and it has no employee threshold at all
  • So for most of the studios, service businesses and independent professionals I work with, WCAG conformance is not yet a legal requirement. The rest of it is. And as you will see, there are better reasons to build an accessible website than the ones fear-based marketing gives you.

    What WCAG 2.0 Level AA actually asks for

    Where the AODA does apply to websites, it is measured against the Web Content Accessibility Guidelines at Level AA — the internationally recognised technical standard for accessible digital content. Level AA sits in the middle of the scale: more demanding than the basic Level A, less exhaustive than Level AAA. Live captioning and pre-recorded audio description are excluded.

    WCAG is organised around four principles, easy to remember as POUR. Your website should be Perceivable, Operable, Understandable and Robust. In plain terms: someone using a screen reader, navigating by keyboard, or living with low vision can use your site as easily as anyone else.

    I build to WCAG 2.2 Level AA rather than the 2.0 minimum. It future-proofs the site, aligns with federal expectations under the Accessible Canada Act, and covers the newer criteria for mobile and cognitive accessibility. If you want the standard itself, it is published by the W3C Web Accessibility Initiative.

    The December 2026 deadline, and who it applies to

    Businesses and non-profits in Ontario with 20 or more employees must file an accessibility compliance report with the province, and the next one is due December 31, 2026. That report is a formal declaration that you are meeting the obligations that apply to you.

    It is worth being precise here, because this deadline gets quoted loosely. It is a reporting deadline, not a new web requirement, and it does not apply to a business of three people. The web requirements themselves have been in force since 2021, for organisations above the 50-employee threshold.

    There is one trap worth naming. If you file a report declaring compliance while your website obviously fails basic checks, you are in a weaker position than if you had never filed. Penalties under the AODA can reach six figures per day on paper, though in practice enforcement has produced modest fines, and mostly for failing to report rather than for accessibility itself. Honest effort and accurate reporting matter more than any single fix.

    Why I would build an accessible site anyway

    Not the law. The people. In 2022, 28% of Ontarians aged 15 and over reported a disability that limited their daily activities — more than one in four, according to the Canadian Survey on Disability. That share grows as the population ages.

    Accessibility is also quietly becoming a commercial requirement. It turns up in client contracts, in public-sector requests for proposals, and in grant conditions. Businesses that build it in are not scrambling when a tender asks for it.

    And there is the everyday case, which I find more persuasive than either. A site with readable contrast, real headings, labelled forms and full keyboard navigation is easier for everyone — including the client reading your services page on her phone, outdoors, in full afternoon sun.

    Accessibility and SEO are the same work

    Most of what brings a site toward accessibility also helps it rank. Alt text helps Google understand your images. A clean heading structure is an on-page SEO fundamental. Semantic, well-structured HTML helps search engines crawl your content, and increasingly helps AI-generated answers cite you correctly. You do the work once and it pays twice.

    The overlay widget trap

    Before we talk about doing this properly, let me flag the shortcut everyone gets sold: the accessibility overlay, a floating icon that promises instant compliance for a monthly fee.

    I steer clients away from them. Overlays address a fraction of accessibility issues, they can conflict with the screen readers they claim to help, and screen reader users have consistently reported that they make sites harder to use, not easier. They have also been the subject of litigation elsewhere. No widget makes a site conform to WCAG on its own.

    Automated scanners have the same limitation in a milder form. They are genuinely useful for a first pass, but a meaningful share of accessibility problems can only be found by a person testing with a keyboard and a screen reader.

    Where most Ontario websites fall short

    When I audit a site, the same handful of issues come up again and again:

    None of these are exotic. Most are fixable, and fixing them rarely requires throwing your whole site away.

    How I make a site accessible without a full rebuild

    My approach is staged, because an all-or-nothing rebuild helps no one. I start with a manual audit — real testing with a keyboard and a screen reader, not only an automated scan — and map each gap against WCAG 2.2 Level AA.

    From there I prioritise the fixes that affect the most people: navigation, forms, colour contrast and heading structure. Then alt text, descriptive links and accessible documents. I also prepare a clear, current accessibility statement for the site, which most web projects quietly skip.

    For redesign projects I treat accessibility as a foundation rather than a final checklist item. Retrofitting an inaccessible site always costs more than building it right the first time.

    Let's make your website accessible and findable

    If you would like a clear picture of where your website stands and a practical plan to get compliant before the 2026 deadline, I would be glad to help. You can see how I approach accessible, bilingual web design on my services page, and when you are ready, get in touch through my contact page.

    No jargon and no overlay gimmicks, just a site that works for everyone and ranks better while doing it.

    Share :