Thunder Bay Developers

AODA and your website: what Ontario businesses actually have to do

Reading time: 6 minutes

Under Ontario Regulation 191/11, the Integrated Accessibility Standards under the Accessibility for Ontarians with Disabilities Act, designated public sector organizations and private or non-profit organizations with 50 or more employees in Ontario must make their public websites and web content conform to WCAG 2.0 Level AA, live captions and pre-recorded audio descriptions excepted. Since January 1, 2021 the requirement has covered all of their websites and web content that they control, for content published after January 1, 2012. Private and non-profit organizations with fewer than 50 employees are not required to meet the web standard but keep their general AODA obligations.

Applies to
Designated public sector organizations, and private or non-profit organizations with 50 or more employees in Ontario
Standard
WCAG 2.0 Level AA, since January 1, 2021, for web content published after January 1, 2012 on sites the organization controls
Note
General information, not legal advice. The regulation is published on ontario.ca.

Who the web standard applies to

The rule sits in Ontario Regulation 191/11, the Integrated Accessibility Standards, made under the Accessibility for Ontarians with Disabilities Act. Designated public sector organizations include municipalities, school boards, hospitals, colleges and universities. Private and non-profit organizations are caught at 50 or more employees in Ontario.

The threshold counts employees in Ontario, so a company based elsewhere with a large Ontario workforce is caught, and a Thunder Bay business with a dozen staff is not. If you are near the line, read the regulation itself on ontario.ca.

If you have fewer than 50 employees

Most businesses in Thunder Bay fall under the threshold, and the web standard does not apply to them. The AODA still does.

Every organization in Ontario with at least one employee has obligations under the customer service standard: a policy on how people with disabilities are served, welcoming service animals and support persons, and notice when an accessible service is disrupted. Customers can ask for information in an accessible format, and you must work with them on how to provide it.

Every organization must also train its staff on the requirements that apply to it; written policy documents, training records and compliance reports are required only above the employee counts the regulation sets out.

Beyond the law, an accessible site works for more customers, and it saves a rebuild if you grow past 50 employees or sell to a public body whose procurement asks about accessibility.

What WCAG 2.0 Level AA means on a small business site

WCAG is a long document, but on an ordinary business website most of it comes down to a handful of habits.

The regulation names version 2.0. The newer versions, 2.1 and 2.2, build on it, and the W3C states that content conforming to them also conforms to 2.0, so a site built to 2.1 or 2.2 Level AA meets 2.0 Level AA as well. Most checking tools now test the newer versions.

  • Contrast

    Normal text needs a contrast ratio of at least 4.5:1 against its background, and large text at least 3:1. Pale grey text on white is the usual failure.

  • Text alternatives

    Every image that carries information gets a written alternative, and decorative images are marked so that screen readers skip them.

  • Keyboard use

    Every link, button, menu and form can be reached and operated with the Tab and Enter keys, with a visible focus outline, and nothing traps the keyboard.

  • Forms

    Every field has a visible label, required fields are identified, and errors are described in words beside the field rather than by colour alone.

  • Captions

    Pre-recorded video carries captions. Live captions and pre-recorded audio description are the two items the AODA excepts.

  • Readable structure

    Each page has a title, headings in order, link text that says where it goes, and its language declared so that screen readers pronounce it correctly.

  • Resizing and motion

    The page still works when text is enlarged to 200 per cent, nothing flashes more than three times a second, and moving content can be paused.

How to check a site

Start with an automated checker: Lighthouse, built into Chrome, or WAVE from WebAIM, both free. They catch missing alternatives, low contrast and unlabelled fields, but not whether an alternative is meaningful or a page makes sense in order.

Finish by hand. Put the mouse aside and move through the home page and the contact form with the Tab key. Enlarge the text to 200 per cent and check that nothing overlaps or disappears. Turn on the screen reader already on your phone, VoiceOver on an iPhone or TalkBack on Android, and listen to the home page.

Then look past the pages. For organizations that must meet the standard, documents posted on the site, such as PDF forms, menus and price lists, count as web content too, and a scanned PDF is a picture to a screen reader.

What to ask a web designer

Put these in the brief, alongside the rest of our website checklist:

  • Which version and level of WCAG will the site be checked against, and will you show me the results?
  • Will testing include a keyboard pass and a screen reader, or only an automated tool?
  • Will the contact and booking forms have visible labels and written error messages?
  • Can I add alternative text, headings and captions myself when I update the site?
  • Which third-party parts, such as booking widgets or maps, have you checked?
  • Will the site carry an accessibility statement with a way for visitors to report a problem?

Keeping a site accessible after launch

A site is accessible on the day it is tested. Afterwards it depends on what is added.

A photograph uploaded without alternative text, a new page with headings chosen for their look, or a flyer posted as a scanned PDF can each undo the work. Build the habits into how content is added: alternative text is part of uploading a photo, and a heading is a heading and not bold text.

What to do next

Count your employees in Ontario. If you are at 50 or more, or a designated public sector organization, have the whole public site audited against WCAG 2.0 Level AA, fix the failures in order of how many visitors they affect, and keep the record.

If you are under the threshold, fix the five faults that matter most to customers: contrast, image alternatives, form labels, keyboard access and heading order. In either case, read the regulation on ontario.ca rather than relying on a summary, including this one.

This guide is general information, not legal advice. Obligations depend on how an organization is classified and on its number of employees in Ontario; ask a lawyer about your situation.

Questions

AODA questions, answered.

Does my small business website need to be AODA compliant?

If your organization has fewer than 50 employees in Ontario and is not a designated public sector organization, the AODA does not require your website to meet WCAG 2.0 Level AA. You still have general AODA obligations, such as the customer service standard and providing accessible formats on request. Organizations with 50 or more employees in Ontario must meet WCAG 2.0 Level AA for their public web content. This is general information, not legal advice.

What does WCAG 2.0 Level AA mean in plain words?

It is a published set of checks that make a website usable by people with disabilities. On a small business site it comes down to readable contrast, a written alternative for every meaningful image, forms with visible labels and written error messages, everything workable with a keyboard, captions on pre-recorded video, headings in order, and a page that still works when the text is enlarged.

Does the AODA web standard apply to PDFs and other documents on my site?

For organizations that must meet the standard, web content includes the documents published on the site, so a PDF form or menu is expected to be accessible too: real text rather than a scan, a reading order, tagged headings and described images. The simplest fix is often to publish the same information as an ordinary web page.

Start a project

Ask how your site measures up.

Send a few lines about your site and your organization, and we will tell you what an accessibility check would cover. The first consultation is free, by email, video call, or in person in Thunder Bay.