AODA Website Compliance for Ontario Small Businesses: What You're Actually Required to Do (And by When)

You’ve probably heard about AODA compliance. Maybe a client mentioned it, maybe it came up in a Chamber of Commerce email, or maybe you’ve been quietly ignoring it hoping it goes away. It won’t.

Ontario’s Accessibility for Ontarians with Disabilities Act has been rolling out in phases since 2005, and 2026 brings a hard reporting deadline that catches a lot of small businesses off guard. The law affects every Ontario business with at least one employee — and while the strictest web requirements technically kick in at 50 employees, even smaller businesses have real obligations here.

At Databending, we build websites for Windsor and Ontario businesses and we’ve been fielding more AODA questions in the past year than ever before. This is what we tell clients.

What Is the AODA, and Why Does It Affect Your Website?

The Accessibility for Ontarians with Disabilities Act (AODA) is provincial law, passed in 2005, with a stated goal of making Ontario fully accessible by 2025. It covers five areas: customer service, information and communications, employment, transportation, and the built environment.

Your website falls under Information and Communications — specifically the Integrated Accessibility Standards Regulation (IASR). The IASR requires that public-facing websites and web content meet the Web Content Accessibility Guidelines (WCAG) 2.0 at Level AA.

Why does this matter beyond legal compliance? About 2.9 million Ontarians — roughly 20% of the population — live with a disability that affects how they use the internet. If your site doesn’t work for them, they go to a competitor who built theirs properly. That’s real lost revenue, not just a compliance checkbox.

Who Has to Comply (The Size Breakdown)

The AODA isn’t one-size-fits-all. Here’s what applies based on your headcount — full-time, part-time, seasonal, and contract workers all count:

Self-Employed With No Employees

Fully exempt from AODA requirements.

1–19 Employees

• Must make emergency information accessible upon request
• Must provide information in accessible formats upon request
• No mandatory WCAG website compliance
• No compliance reporting required
• Still strongly advisable to meet basic accessibility standards

20–49 Employees

• Must file an accessibility compliance report every three years
• Next deadline: December 31, 2026
• Must provide information in accessible formats
• Web accessibility requirements apply — WCAG 2.0 Level A (not the full AA)
• Must have documented multi-year accessibility plan

50+ Employees

• Full WCAG 2.0 Level AA compliance required for all public-facing web content and web-based applications
• Compliance reporting every three years
• Next deadline: December 31, 2026
• New internet websites and significantly refreshed content must meet WCAG 2.0 Level AA

The December 31, 2026 deadline is the reporting deadline — meaning you submit a form to the province confirming you’re meeting your obligations. But the web accessibility requirements themselves were technically due years ago. The longer your site remains non-compliant, the longer you’re exposed to penalties.

What Does WCAG 2.0 Level AA Actually Mean?

WCAG (Web Content Accessibility Guidelines) is a set of technical standards from the W3C — the international body that governs web standards. Level AA is the middle tier: more rigorous than basic Level A, but not as demanding as the research-grade Level AAA.

The guidelines are organized around four principles — your website must be Perceivable, Operable, Understandable, and Robust (POUR). In practice, for a typical Ontario business website, that breaks down like this:

1. Alt Text on Every Image

Screen readers — software used by people with visual impairments — cannot “see” images. Every image on your site needs a descriptive alt text attribute so screen readers can describe it to the user.

What to do:

• Add alt="[description]" to every <img> tag
• Decorative images get alt="" (empty, not missing) so screen readers skip them
• Avoid generic alt text like “image1.jpg” or “photo”
• For charts and graphs, describe the data, not just the visual

What this looks like: A photo of your Windsor storefront should have alt text like alt="Databending office on Ouellette Avenue, Windsor Ontario" — not alt="storefront".

2. Sufficient Color Contrast

Text must have enough contrast against its background to be readable by people with low vision or color blindness. WCAG 2.0 AA requires:

• 4.5:1 contrast ratio for normal text
• 3:1 contrast ratio for large text (18pt+ or 14pt bold+)

This catches a lot of Ontario business websites — light grey text on white backgrounds, white text on pale blue buttons, or brand colors that “look fine” but fail the contrast check. Tools like the WebAIM Contrast Checker let you test any color pair in seconds.

3. Keyboard-Only Navigation

Some users cannot use a mouse — they navigate entirely by keyboard, typically using Tab to move between elements. Every clickable element on your site (menus, buttons, forms, links) must be reachable and usable with a keyboard alone.

Common failures:

• Dropdown menus that only work on hover (not keyboard)
• Modal popups with no keyboard-accessible close button
• Forms where Tab order jumps around unpredictably
• No visible focus indicator (the outline that shows which element is active)

How to test: Open your site and unplug your mouse. Try to complete a task — fill out a contact form, navigate to a service page, find your phone number. If you get stuck, so will users who rely on keyboards.

4. Captions and Transcripts for Video

If you have video on your website — a promotional reel, an explainer, a testimonial — it needs captions. Prerecorded video with audio requires accurate synchronized captions that identify speakers. Audio-only content (like a podcast) needs a transcript.

Auto-generated captions from YouTube or Vimeo don’t meet WCAG 2.0 AA on their own — they’re often inaccurate enough to fail. You need reviewed and corrected captions.

5. Descriptive Page Titles and Headings

Every page needs a unique, descriptive <title> tag and a logical heading structure (<h1> through <h6>). Screen readers use headings to navigate pages the way sighted users skim visually. A page with no <h1>, or with headings that jump from <h1> to <h4>, is disorienting for screen reader users.

What to check:

• Every page has a unique <title> that describes its content
• One <h1> per page (your main topic)
• Headings follow a logical order (no skipping levels)
• Headings describe the section content, not just style choices

6. Form Labels and Error Messages

Every input field on your contact forms, booking forms, or checkout needs a visible <label> element linked to it. Placeholder text inside fields doesn’t count — it disappears when the user starts typing.

Error messages must be specific. “Invalid input” fails. “Please enter a valid 10-digit phone number” passes.

7. Accessible PDFs and Documents

If your site links to downloadable PDFs — menus, price lists, brochures, application forms — those documents must also meet accessibility standards. That means tagged PDFs with readable structure, not scanned image files.

Scanned PDFs are images of text. A screen reader sees a blank page. This is one of the most common AODA failures we see on Windsor business websites.

8. No Seizure-Triggering Content

Content that flashes more than three times per second can trigger seizures in people with photosensitive epilepsy. This applies to animations, GIFs, and video. If you have animated elements on your site, check that nothing flashes at that rate.

The December 2026 Deadline: What You Actually Need to File

If your business has 20 or more employees, you must submit an Accessibility Compliance Report through the Ontario government portal by December 31, 2026. This report is a declaration that you are meeting your AODA obligations — it covers both your website accessibility and other areas like employment and customer service accessibility.

Filing is done at ontario.ca/page/completing-your-accessibility-compliance-report. The report itself isn’t complex, but it triggers scrutiny — if you declare compliance and your website clearly fails basic accessibility checks, you’re in a worse legal position than if you hadn’t filed a misleading report at all.

Our recommendation: Get your website assessed and remediated before filing, not after.

Penalties: What Non-Compliance Actually Costs

The AODA has real enforcement teeth:

• Individuals and unincorporated businesses: Up to $50,000 per day
• Corporations: Up to $100,000 per day
• Directors and officers can face personal liability if they directed or permitted non-compliance

In practice, enforcement has historically focused on larger organizations and repeat offenders, and fines for reporting failures tend to start lower ($500–$15,000). But that enforcement posture has been tightening, and the 2026 reporting cycle is expected to come with increased scrutiny.

Beyond government penalties, there’s litigation risk. Ontario’s Human Rights Code provides an independent path for people with disabilities to file complaints against businesses whose websites exclude them — and Human Rights Tribunal settlements can be substantial.

Getting compliant costs less than a single enforcement action. Usually far less.

How to Audit Your Site for AODA Compliance

You don’t need to hire an accessibility consultant to start. Here’s a practical audit approach:

Free automated tools:

• WAVE Web Accessibility Evaluator — paste your URL and get a visual breakdown of issues
• axe DevTools — Chrome extension for developers
• Google Lighthouse (built into Chrome DevTools) — includes an accessibility score

Manual checks to do yourself:

1. Tab through your entire site with a keyboard only
2. Turn off your monitor’s color display (or use a grayscale browser extension) and check readability
3. Right-click every image and look for alt text in the page source
4. Download any PDFs from your site and try to select/copy text — if you can’t, it’s a scanned image
5. Play any videos with the sound off and check whether captions appear

Automated tools typically catch 30–40% of accessibility issues. Manual testing is essential for the rest.

Getting Compliant Without a Full Rebuild

Most AODA compliance issues don’t require tearing down and rebuilding your site.

Quick wins that fix common issues:

• Adding alt text to images (can be done in any CMS in an afternoon)
• Fixing color contrast (usually a CSS change to text or background colors)
• Adding labels to form fields (a developer task, usually a few hours)
• Installing a caption plugin on embedded YouTube/Vimeo videos
• Converting key PDFs to properly tagged documents

Where it gets more complex:

• Keyboard navigation on custom-built menus and interactive elements
• Accessible modal dialogs and popups
• Complex forms with conditional logic
• Custom JavaScript components that weren’t built with accessibility in mind

If your site was built on WordPress, Squarespace, or Shopify, much of the heavy lifting is handled at the theme/platform level. The issues tend to be in your specific content and customizations, not the platform itself.

If your site was custom-built years ago without accessibility in mind, a targeted audit and remediation project is worth doing before December 2026.

Why Accessibility Also Helps Your SEO

Many AODA/WCAG fixes directly improve your Google rankings — most Ontario business owners don’t realize this until they see it happen.

• Alt text helps Google understand your images and surfaces them in Google Image Search
• Descriptive page titles and heading structure are on-page SEO fundamentals
• Faster load times (often improved during accessibility audits) are a direct ranking factor
• Clean, semantic HTML helps Googlebot crawl and index your content more accurately
• Accessible forms that convert better drive more leads — which Google interprets as engagement signals

Fixing your site for AODA compliance and fixing it for SEO are often the same work. For more on how on-page factors affect your rankings, see our guide on building a website that ranks on Google for Windsor and Kingsville businesses.

How Databending Approaches AODA Compliance

Every website we build at Databending goes out the door with AODA compliance as a baseline, not an afterthought. That means:

• Semantic HTML structure from the ground up
• Alt text fields built into every image component in the CMS
• Contrast ratios checked against brand colors during the design phase
• Keyboard navigation tested before launch
• Forms built with proper labels and accessible error states
• A Lighthouse accessibility score target of 90+ on every project

If you have an existing site that needs remediation before the December 2026 deadline, we offer accessibility audits and targeted fixes — we’ll tell you exactly what needs to change and handle the development work.

Ready to Get Your Ontario Website AODA Compliant?

December 31, 2026 is the filing deadline — and accessibility issues don’t get fixed overnight. If you start in November, you’re patching, not fixing. Get assessed now while there’s time to do it properly.

Book a free accessibility consultation with Databending

Or explore more:

• Our Windsor web design services
• How much does a website cost in Canada?
• Top 10 SEO mistakes Ontario businesses make