Illustration showing Ontario website accessibility requirements — a shop owner beside a glowing website screen with an accessibility symbol, keyboard, speaker and magnifier

Who Has to Make Their Website Accessible in Ontario — and to What Standard

简短回答: Ontario website accessibility requirements come from the Accessibility for Ontarians with Disabilities Act (AODA) and its Integrated Accessibility Standards. The formal web rule is specific: organizations with 50 or more employees in Ontario, plus public-sector and designated organizations, must make their public websites and web content conform to WCAG 2.0 Level AA, with a few stated exceptions. Smaller businesses are not covered by that specific web rule, but they are covered by other AODA duties — accessible customer service and information in accessible formats on request.

Where the requirements actually come from

Ontario accessibility law is a stack, not a single rule. At the top sits the AODA, the provincial law whose purpose is to develop, implement and enforce accessibility standards. Under it, the Integrated Accessibility Standards Regulation sets the detailed duties by area: customer service, information and communications, employment, transportation and the design of public spaces. Websites fall under information and communications.

The province explains this structure on its page about accessibility laws in Ontario, and summarizes who owes what on its page of accessibility rules for businesses and non-profits. Those official pages separate duties that apply to almost every organization from duties that switch on only at certain employee counts. This article follows that separation, and it is general information, not legal advice: if your organization sits near a threshold, confirm your position with the province or a qualified adviser.

Ontario website accessibility requirements: who must comply

Start with the web-specific rule, because it is the one most often misstated online. Under the information and communications standard, organizations with 50 or more employees in Ontario — and public-sector organizations, which followed their own earlier timelines — must ensure their public websites and the content on them conform to the Web Content Accessibility Guidelines at Level AA, subject to exceptions where meeting a requirement is not practicable, and excluding criteria 1.2.4 (captions for live audio) and 1.2.5 (audio descriptions for pre-recorded video). The rule reaches content the organization controls, including content it did not build itself but directs or pays for.

Count your Ontario employees honestly: the threshold is 50 employees in Ontario, not 50 people worldwide, and part-time or seasonal patterns can complicate the count — a reason borderline organizations should take advice rather than self-certify. Some organizations carry duties because of what they are: public-sector bodies, educational and health institutions, libraries and other designated organizations have their own obligations, including accessibility plans, and their requirements can reach suppliers contractually. Organizations with 20 or more employees must also file accessibility compliance reports.

The duties that reach businesses of every size

The Customer Service Standard is the broad layer. Ontario businesses and non-profits providing goods, services or facilities to the public must do so accessibly: communicate in a way that takes a person’s disability into account, allow assistive devices, welcome support persons and service animals, train staff who deal with the public, and maintain a feedback process that is itself accessible. Your website sits inside that duty in practice, because it is now the first act of customer service — the hours, the prices, the booking, the first question answered or unanswered.

The information and communications standard adds a second broad layer: organizations must, on request, provide publicly available information in accessible formats or with communication supports, in a timely manner and at no greater cost than the regular version, after consulting the person making the request. Think of the price list that exists only as a scanned PDF, or the announcement published only as an image: a request for that material in a usable format is not a special favour but a duty, and publishing web versions of key documents is the simplest way to meet it. Taken together, the honest answer to “does any of this apply to my ten-person business?” is yes — just not the specific WCAG website clause.

To what standard: WCAG, and what Level AA means in practice

The technical standard named in the regulation is WCAG — the Web Content Accessibility Guidelines maintained by the W3C, whose WCAG standards and guidelines page is the reference for the whole family of versions. Ontario names WCAG 2.0 at Level AA. The guidelines rest on four principles, shortened to POUR: content must be perceivable, operable, understandable and robust. Every specific requirement — a success criterion — carries a level: A is the minimum floor, AA is the level laws most often adopt, and AAA is a higher set the guidelines themselves do not recommend as a blanket requirement for whole sites.

In plain terms, Level AA asks for ordinary, testable things: text that contrasts enough for people with low vision to read, everything operable by keyboard alone with a visible focus indicator, text alternatives for images that carry information, captions for videos that carry information, headings and form labels that describe what follows, forms that explain their errors, and pages that resize without breaking when a visitor zooms in. Two cautions follow. The regulation names version 2.0, while the guidelines have since moved through 2.1 and 2.2; building new work to 2.1 AA is common good practice and covers the older set, but describe your position accurately. And automated scanning tools check only part of the criteria — a clean scan is a good sign, not proof of conformance, because software cannot judge whether alt text is meaningful.

What counts as your website — and what usually gets missed

Owners picture the marketing pages. Auditors picture everything a visitor meets under your name — booking and checkout flows, portals, career pages, chat widgets, embedded maps and video players, and the documents the site hands out: PDF menus, price lists, intake forms and policy files. Third-party tools do not take the duty away: if the booking widget is the only way to book, its barriers are your customer’s problem and, at the sizes where the web rule applies, your compliance problem too. Ask vendors for their conformance reports before you sign.

The most-missed items are consistent: PDFs first, then images of text, videos without captions, form fields labelled only by placeholder text, and menus that trap keyboard users. A quick self-check finds your exposure: try to book or enquire using only Tab and Enter.

Deadlines, reports and enforcement — the honest version

Most AODA website deadlines are in the past: the WCAG website requirement for larger private and non-profit organizations took effect at the start of 2021, so for organizations over the threshold the rule already applies and the work is remediation and upkeep. The province can require audits, issue compliance orders and levy administrative penalties, with amounts depending on the contravention and history — do not let anyone sell you a specific fine figure as your personal risk. For most businesses the realistic first cost is not a fine: it is the customer who could not book and the tender that asked for conformance you could not show. Above the standards sits the Ontario Human Rights Code, which prohibits discrimination in services at every size.

A sensible order of work for a small Ontario business

Under the web-rule threshold, a proportionate programme looks like this. First, fix the journeys that make or lose money — contact form, booking, checkout — tested by keyboard and screen reader. Second, adopt the habits that stop new barriers: real alt text as images are uploaded, headings in order, documents published as web pages where possible, captions on new videos. Third, publish a clear feedback route and honour accessible-format requests. Fourth, when you redesign, write WCAG AA into the brief, because building accessibly costs a fraction of retrofitting.

At or over 50 employees, treat it as a formal project: commission a manual audit against WCAG AA, remediate templates before individual pages, retest, document what was done, and fold the result into your compliance reporting. Our companion article on website accessibility cost in Canada covers what that remediation typically costs and why quotes vary — read it alongside this requirements summary, because audit findings, not the sales call, set the number. Where a site is being built anyway, our services page sets out what each build includes and our pricing page lists the published figures — a Business Site is US$799 and Website Care is US$69 a month, taxes extra, with CAD invoices available on request. See also our article on what a small law firm’s website must do to earn trust.

常见问题

Do Ontario website accessibility requirements apply to a business with fewer than 50 employees?

The WCAG Level AA website duty applies to organizations with 50 or more employees in Ontario, plus public-sector and designated organizations. Smaller businesses still carry other AODA duties — accessible customer service and information in accessible formats on request — and the Ontario Human Rights Code applies at every size.

Which version and level of WCAG does Ontario require?

The regulation names WCAG 2.0 at Level AA, excluding the criteria for live captions and for audio description of pre-recorded video, and subject to exceptions where a requirement is not practicable. Many organizations build new work to WCAG 2.1 AA as good practice, but 2.0 AA is the level written into Ontario law.

Does the rule cover PDFs, booking tools and other third-party content?

It covers web content the organization controls, including content it directs or pays others to provide — in practice, downloadable documents, booking and checkout flows, portals and embedded tools. A vendor’s barrier becomes your customer’s barrier, so ask suppliers for conformance information before you buy.

What happens if an organization does not comply?

The province can require information and audits, issue compliance orders and impose administrative penalties, with amounts depending on the contravention and history. In practice, many businesses feel the commercial consequences first: lost customers and failed procurement requirements.

We are under the threshold — where should we start?

Start with the journeys that earn money: make sure the contact form, booking or checkout and key information work by keyboard and with a screen reader, publish important documents as web pages where you can, add real alt text and captions as new content appears, and provide a clear way to request information in another format.

Requirements first, then scope, then budget

The order of operations is the whole lesson: establish which duties are actually yours, measure your site against the named standard, and only then talk about fixes and money. If you would like your site checked against the requirements in plain language, 获取免费报价 and tell us how many people your Ontario organization employs and what your site is built on.

Need help with your project?

Get a free quote for your website, ecommerce, or SEO project.

获取免费报价

发表评论

您的邮箱地址不会被公开。 必填项已用 * 标注

滚动至顶部