Does AODA apply to my small business?

AODA's website compliance rules (Information and Communications Standards) legally apply to private organizations with 50 or more employees. Smaller organizations are encouraged to comply but not legally required. That said, accessibility-focused design improves SEO, broadens your audience, and reduces legal exposure under the Ontario Human Rights Code (which applies regardless of size), so we recommend it for any Ontario business.

What standard does AODA require?

The Information and Communications Standards under AODA require WCAG 2.0 Level AA compliance for websites and web content. WCAG 2.1 and 2.2 are newer versions; AODA hasn't formally adopted them yet, but most accessibility experts recommend building to the more recent standards. The core requirements (contrast, keyboard navigation, alt text, captions, proper structure) are the same across versions.

What are the penalties for AODA non-compliance?

Maximum administrative penalties under AODA are $50,000 per day for an individual director and $100,000 per day for a corporation. In practice, enforcement has been light. Most penalties have been smaller, targeted at organizations that ignored compliance notices. The bigger risk for most businesses is private discrimination complaints under the Ontario Human Rights Code, which can result in damages awards and order-to-comply remedies.

How much does AODA compliance cost for a website?

For a new build done right from the start, AODA compliance adds little to no cost. It's mostly about design and development decisions during the build. For retroactive compliance work on an existing site, costs range from $3,000 to $20,000 depending on site size and how far off baseline the site is. Larger sites with custom interactive elements (e-commerce, dashboards) cost more.

Can a tool like accessiBe or UserWay make my site AODA compliant?

No, and using these tools may create additional legal exposure. Overlay tools (accessiBe, UserWay, AudioEye) claim to automatically fix accessibility issues but have been repeatedly shown to be ineffective and sometimes harmful. They have been the subject of multiple lawsuits in the US. The Canadian disability advocacy community broadly opposes them. Real compliance means addressing accessibility in the underlying code. Bolted-on overlays don't qualify.

AODA Compliance for Ontario Business Websites: A Practical Guide

The Accessibility for Ontarians with Disabilities Act (AODA) became the headline-grabbing law it isn't because most businesses ignored the website compliance deadlines for years. Now, with enforcement starting to ramp up and Human Rights Code complaints becoming more common, Ontario businesses are paying attention.

This guide is for Ontario small business owners, marketing leads, and anyone responsible for a business website. It explains what AODA requires of websites in plain English, who's legally on the hook, what compliance looks like in practice, and the real costs and risks of getting it wrong.

What AODA is and who it applies to

AODA is Ontario provincial legislation passed in 2005 with the goal of making Ontario accessible by 2025. It applies in stages, with different requirements for different organization sizes and types.

For website compliance specifically, the relevant rules sit under the Integrated Accessibility Standards Regulation (IASR), particularly the Information and Communications Standards. The website requirements have applied since:

January 1, 2014 for the Government of Ontario and Legislative Assembly
January 1, 2014 for designated public sector organizations (universities, hospitals, municipalities)
January 1, 2021 for private and non-profit organizations with 50+ employees

Under 50 employees? You're not legally required to comply with the IASR. But the Ontario Human Rights Code still applies, and discrimination complaints related to inaccessible websites can be brought by anyone, regardless of business size.

The standard: WCAG 2.0 Level AA

AODA's website requirements reference WCAG 2.0 Level AA, the Web Content Accessibility Guidelines published by the W3C. It's the most widely-used accessibility standard globally.

WCAG organizes requirements under four principles:

Perceivable: information must be presentable in ways users can perceive
Operable: interface and navigation must be operable
Understandable: content and operation must be understandable
Compatible: content must work with current and future tools, including assistive technologies

Level AA is the middle of three conformance levels (A, AA, AAA). It's the standard most regulators, including Ontario, require.

What WCAG 2.0 Level AA requires in practice

In practical website terms, here's what compliance means.

Perceivable

Text alternatives for all non-text content. Every image needs alt text. Every video needs captions or a transcript. Every audio file needs a transcript.
Captions for video content (recorded or live).
Audio descriptions for video where visual information is critical and not described in the audio.
Adaptable content: layout and structure don't depend on visual presentation alone. Screen readers need to be able to convey the same information.
Distinguishable: text has at least 4.5:1 contrast against its background for normal text, 3:1 for large text. Information isn't conveyed by colour alone.

Operable

Keyboard accessible: all functionality available via keyboard. No "mouse only" interactions.
Enough time: users can pause or extend time-limited content.
Seizure-safe: no content that flashes more than 3 times per second.
Navigable: clear page titles, descriptive link text, headings used properly to organize content, focus visible when navigating via keyboard.

Understandable

Readable: language of the page declared (lang attribute in HTML). Plain language preferred where possible.
Predictable: navigation works consistently across pages. Components that look the same behave the same.
Input assistance: form errors clearly identified. Labels and instructions provided. Help available for inputs in critical contexts.

Compatible

Code uses valid HTML so assistive technologies can interpret it correctly.

Common AODA violations on Ontario business websites

After auditing dozens of Ontario business sites, here are the violations that show up most consistently.

1. Missing or unhelpful alt text on images.

The most common violation. Images without alt text are invisible to screen readers. Decorative images need alt="" (empty, intentionally). Informational images need descriptive alt text: "Sarah Smith, founder, holding a wooden surfboard" rather than "image1.jpg".

2. Insufficient colour contrast.

Light grey text on white backgrounds is a designer favourite and a WCAG violation. Run your site through a contrast checker (WebAIM's Contrast Checker is free and reliable). Body text needs 4.5:1. Large text (24px+ regular, 19px+ bold) needs 3:1.

3. Forms without proper labels.

Forms where the placeholder text doubles as the label fail screen readers. Every form input needs a <label> element associated with it, or aria-label/aria-labelledby attributes.

4. Links that say "click here" or "read more".

Screen reader users navigate by listing links. "Click here, click here, click here" tells them nothing. Use descriptive link text: "Read our 2026 SEO guide" instead of "Read more".

5. Headings used for styling instead of structure.

Using H2 because you like how big it looks, regardless of document structure, breaks screen reader navigation. Headings (H1, H2, H3) must reflect actual content hierarchy.

6. Video without captions.

Embedded YouTube videos default to no captions. Either upload captioned versions or use YouTube's caption feature (and review the auto-generated captions for accuracy; auto-captions are often wrong on Canadian English).

7. Carousel sliders that move automatically.

Auto-advancing carousels are an accessibility nightmare. Users with cognitive disabilities, screen readers, or motor impairments all struggle. If you must use a carousel, make it user-controlled (no auto-play) and pausable.

8. PDF documents that aren't accessible.

Scanned PDFs are images of text, invisible to screen readers. PDFs need to be properly tagged with reading order, alt text, and proper heading structure. For most businesses, HTML alternatives are easier than accessible PDFs.

9. Modal popups that trap keyboard focus.

Popups that can't be dismissed via keyboard, or that don't return focus to the trigger element when closed, fail WCAG. Common in newsletter signup popups and cookie banners.

10. Inaccessible custom dropdowns and dropdown menus.

Custom-built dropdown menus that look pretty but don't work with keyboard navigation are a frequent failure point. Either use standard <select> elements or implement the full keyboard interaction pattern.

High-risk industries for AODA enforcement

Some sectors face more scrutiny than others:

Healthcare and medical practices: vulnerable populations directly affected
Legal services: clients with disabilities accessing legal information
Financial services: clients managing finances who need accessibility
Government contractors: AODA compliance often required to bid on contracts
Universities and colleges: heavily enforced sector
Retailers with significant online sales: scope and visibility raise risk

If you operate in one of these sectors, AODA compliance isn't optional from a risk management standpoint, even if you're under 50 employees.

The overlay tool problem

Several companies sell accessibility overlay widgets (accessiBe, UserWay, AudioEye, EqualWeb) that claim to make any website AODA compliant with one line of JavaScript.

These don't work, and we don't recommend them.

The independent accessibility research community is unanimous on this. Overlays often break the assistive technologies they claim to help. The Canadian disability advocacy community has issued statements opposing them. Multiple lawsuits in the US have specifically targeted businesses using these tools as inadequate compliance.

The legal exposure: an overlay creates an appearance of compliance without the reality. If a user files a complaint, "we have an accessibility widget" is not a defence. Real compliance means addressing accessibility in your actual HTML, CSS, and JavaScript.

The real solution is more work, but it works: audit, remediate, test with real users where possible, and maintain ongoing accessibility as part of your development process.

The cost of compliance vs the cost of non-compliance

For a new build done right: minimal extra cost. Accessibility is most cost-effective when baked into design and development from the start. The decisions that drive compliance (proper contrast, semantic HTML, keyboard support, clear structure) are also decisions that drive good design and SEO.

For retroactive compliance on an existing non-compliant site: typically $3,000-$20,000 depending on site size and how far off baseline the site is. Small marketing sites cost less; large sites with custom interactive features cost more.

For ongoing maintenance: $500-$2,000 per year to test for regressions when new features ship. Easier if accessibility is part of your standard process; harder if it's treated as a separate workstream.

Cost of non-compliance:

AODA administrative penalties: maximum $100,000 per day for corporations, $50,000 per day for individual directors. Enforcement to date has been lighter, but ramping up.
Ontario Human Rights Code complaints: damages awards typically $10,000-$50,000 plus order-to-comply remedies and costs.
Lost customers: 22% of Canadians have a disability. Sites they can't use are sites they don't buy from.
Reputational risk: failed accessibility lawsuits make news. Customer-facing reputation damage is hard to quantify but real.

A practical path to compliance for your Ontario business website

Step 1: Audit.

Use one of these to get a baseline:

WAVE (free): browser-based automated checker. Catches the obvious violations.
axe DevTools (free for basic, paid for advanced): developer-focused automated testing.
Manual testing with a screen reader: NVDA (free, Windows), VoiceOver (built into Mac, iOS), JAWS (paid, industry standard).
Professional audit: $2,500-$10,000 for a manual review by an accessibility specialist.

Automated tools catch 30-40% of issues. The rest require manual review. For high-stakes compliance, you need both.

Step 2: Prioritize.

Group violations by impact and effort:

Critical and easy: missing alt text, contrast violations, link text; fix immediately
Critical and hard: complex forms, dynamic content, custom interactive components; plan a project
Lower impact: rare edge cases, optimizations beyond AA; schedule for later

Step 3: Remediate.

Work through the priority list. Most small-to-mid Ontario business sites can be brought to substantial compliance in 4-12 weeks of focused work.

Step 4: Test.

Don't trust automated tools alone. Test with:

Real keyboard navigation (tab through the entire site)
A screen reader (NVDA or VoiceOver)
Mobile screen readers (TalkBack on Android, VoiceOver on iOS)
Where possible, users with disabilities (paid usability sessions)

Step 5: Maintain.

Add accessibility checks to your design and development workflow. Every new feature gets accessibility-reviewed before launch. Quarterly audits catch regressions.

What we recommend for Ontario small businesses

For most Ontario small businesses, the right approach is:

If you're under 50 employees and building a new site: build to WCAG 2.1 AA from day one. The extra cost is minimal at the design stage.
If you're under 50 employees with an existing site: do an audit, fix the critical violations, plan ongoing accessibility into your maintenance budget.
If you're 50+ employees: you're legally required. Treat it accordingly. Get a professional audit and remediation plan.
If you're in healthcare, legal, financial services, or government contracting: assume the compliance bar applies regardless of headcount.

Working with us

We build websites that meet WCAG 2.1 AA from day one for all Ontario clients. For existing sites needing remediation, we offer audits, remediation, and ongoing maintenance.

If you want to talk about where your business stands and what an AODA-compliant path looks like, get in touch. The first conversation usually clarifies the scope and timeline you're looking at.