development
Is Website Accessibility Mandatory for Businesses in Canada? AODA, ACA and What Applies to You
The short answer: it depends on where you operate, which sector you're in and how many people you employ. Some Canadian organizations have a specific legal duty to meet a web accessibility standard. Many more have broader accessibility and human rights obligations that an inaccessible website can put at risk.
For a marketing team, the practical answer is simpler. Accessibility is part of building and running a good company website, it is far cheaper to build in than to retrofit, and it keeps going after launch with every page, PDF and campaign you publish.
This is general information to help you plan, not legal advice. Confirm your obligations with someone qualified in the legislation that applies to you.
Key takeaways
It depends on where and how you operate
Ontario's AODA, the federal Accessible Canada Act and provincial laws apply to different organizations.
WCAG is the working standard
Ontario's rules reference WCAG 2.0 Level AA; newer WCAG versions are good practice.
Accessibility is ongoing
Every new page, PDF and campaign can introduce issues, so it belongs in your publishing process.
Get legal advice for your obligations
This article is general information, not legal advice.
Web accessibility, in plain terms
Web accessibility means people with disabilities, including visual, hearing, motor and cognitive disabilities, can perceive, navigate and use your website on equal terms. The reference standard is the Web Content Accessibility Guidelines (WCAG), published by the W3C, with three conformance levels: A, AA and AAA. Canadian rules generally point to Level AA.
It matters commercially too. Statistics Canada's 2022 Canadian Survey on Disability found that 27% of Canadians aged 15 and over, about 8.0 million people, have a disability that limits their daily activities.
The main Canadian frameworks
| Law | Who it mainly covers | Web standard referenced | What to know |
|---|---|---|---|
| Accessible Canada Act (ACA) | Federally regulated organizations: federal government, Crown corporations, banks, telecoms, broadcasters, interprovincial transportation | CAN/ASC-EN 301 549, which incorporates WCAG 2.1 AA for web content | Requires accessibility plans, feedback processes and progress reports; further digital requirements have been proposed |
| AODA (Ontario) | Ontario public sector and private and non-profit organizations with employees in Ontario | WCAG 2.0 Level AA for the website requirement | The website requirement applies to designated public-sector organizations and organizations with 50+ employees in Ontario |
| Accessible British Columbia Act | B.C. public-sector organizations, with scope expected to grow | Not specified in the Act; WCAG 2.1 AA is the common benchmark | Requires committees, plans and feedback mechanisms |
| Human rights codes | Every employer and service provider | No fixed standard | A website that blocks people with disabilities from a service can raise a human rights issue |
Manitoba, Nova Scotia, Newfoundland and Labrador and other provinces have their own accessibility laws at different stages of development.
Ontario: what AODA asks of companies
AODA is the most developed provincial framework, and it's where most of our clients' questions start.
- Organizations with 50 or more employees in Ontario must make public websites and web content posted after January 1, 2012 conform to WCAG 2.0 Level AA, with exceptions for live captions and pre-recorded audio descriptions. The deadline was January 1, 2021.
- Organizations with 20 or more employees in Ontario must file accessibility compliance reports with the province. The next reporting deadline is December 31, 2026.
- Organizations with fewer employees still have AODA obligations, including accessible customer service, training and providing information in accessible formats on request.
The Act allows for significant penalties, including fines for corporations of up to $100,000 per day in the most serious cases. In practice, the bigger day-to-day exposure for most companies is a complaint, a lost procurement opportunity or a customer who can't complete a form.
Federally regulated organizations
If your company is federally regulated, such as a bank, telecom, airline or interprovincial carrier, the Accessible Canada Act applies. The technical standard it points to for web content incorporates WCAG 2.1 Level AA. Proposed amendments to the Accessible Canada Regulations would add more specific requirements for websites, apps and documents on phased timelines; check the current status before you plan a rebuild.
If none of these apply directly
Provincial human rights codes apply to every business that serves the public. A website that prevents people with disabilities from accessing a service can still raise a human rights issue, whatever your size or province. Many procurement processes and larger customers also ask suppliers about accessibility.
What WCAG 2.1 AA means for your site
These are the issues that come up most often in audits:
- Colour contrast. Body text needs a contrast ratio of at least 4.5:1. Light grey text on white often fails.
- Keyboard access. Menus, buttons, dialogs and forms must work with a keyboard alone.
- Visible focus. Users need to see where they are on the page when tabbing.
- Text alternatives. Meaningful images need descriptive alt text; decorative images should be marked as decorative.
- Form labels. Every field needs a real label. Placeholder text is not a label.
- Captions and transcripts for pre-recorded video and audio.
- Resizing. Text should scale to 200% without breaking the layout.
- Structure. One H1 and a logical heading order, so screen reader users can navigate.
About accessibility overlays: widgets that promise instant compliance don't fix the underlying code and content, and can introduce new problems. Accessibility has to be built into templates, components and content.
Making accessibility part of how your team publishes
A site that launches accessible can drift within months. The fix is process, not a one-time audit:
- Accessible components. Build templates and blocks that are accessible by default, so editors can't easily break them.
- A short publishing checklist. Alt text, headings, link text, captions and accessible PDFs, for anyone who publishes.
- Regular testing. Automated scans catch some issues; periodic manual testing with a keyboard and a screen reader catches the rest.
- Fixes in the normal workflow. Treat accessibility issues like any other website request, prioritized and tracked.
- Campaign assets too. Landing pages, emails and downloadable documents count.
Accessibility and search
Many accessibility practices are also good technical SEO: semantic HTML, descriptive alt text, a logical heading structure, clear link text and transcripts. They help search engines and AI systems understand your content as well as people using assistive technology.
Where to start
- Run a quick automated check to see where you stand. Our free accessibility check is a first look, not a certification.
- Confirm which laws apply to your organization and when.
- Prioritize fixes on the pages and forms that matter most: contact, quote and demo forms, key service pages and checkout.
- Plan the rest into your next website project or ongoing support, and add accessibility to your publishing process.
Frequently Asked Questions
Does AODA apply to my company's website?
Ontario's AODA website requirements apply to the Ontario government, designated public-sector organizations, and private and non-profit organizations with 50 or more employees in Ontario. Smaller organizations have other AODA obligations. Check the current requirements and get legal advice for your situation.
What standard should a website meet?
Ontario's rules reference WCAG 2.0 Level AA. Many organizations now design to WCAG 2.1 or 2.2 AA because they include more criteria for mobile and cognitive accessibility.
Can an accessibility plugin or overlay make a site compliant?
No. Overlays can't fix underlying issues in structure, content and code, and they can introduce new problems. Accessibility needs to be built into templates and content.
How do we keep a site accessible after launch?
Accessible components and templates, a short checklist for anyone who publishes, periodic automated and manual testing, and fixes handled as part of ongoing website support.
Conclusion
Accessibility is easier and cheaper to build in than to retrofit. Start with a free accessibility check for a first look, then plan the fixes into your next website project or ongoing support. For legal obligations, speak to a lawyer familiar with the legislation that applies to you.
Explore this topic with AI
Get an AI-powered summary and save this article as a reference for future conversations.
