Blog · Accessibility

Is your website accessible?

What the AODA and WCAG mean for your organization, and five things you can check today.

  • By Nick Latreille
  • 7 min read

If your organization is in Ontario, website accessibility may not be optional. And even where it isn't required by law, it decides whether a large share of your visitors can use your site at all. Here's what the rules say, what they ask for in practice, and five checks you can do in ten minutes.

Who the rules apply to

The Accessibility for Ontarians with Disabilities Act (AODA) sets accessibility standards for organizations in the province. For websites, the requirement covers public-sector organizations and businesses and nonprofits with 50 or more employees that control their own website. Covered organizations must make their websites and web content meet WCAG 2.0 Level AA. Web content means more than text: it includes images, forms and sounds on a page or web application.

There are a few narrow exceptions, such as maps and complex diagrams that can be provided in an accessible format on request, and cases where meeting the standard isn't practicable. If you're unsure whether your organization is covered, check with the Government of Ontario's AODA resources or a lawyer. This article is a practical guide, not legal advice.

What WCAG actually asks for

The Web Content Accessibility Guidelines (WCAG) are the international standard for accessible websites. They're organized around four ideas: content should be perceivable, operable, understandable and robust. In everyday terms, Level AA asks for things like:

  • Text alternatives. Meaningful images have alt text that describes what they show.
  • Readable contrast. Normal text needs a contrast ratio of at least 4.5:1 against its background, and large text at least 3:1.
  • Keyboard access. Every link, button and form works without a mouse, and you can always see where you are.
  • Captions. Prerecorded video has captions.
  • Clear structure. Real headings, labelled form fields and error messages that explain how to fix the problem.
  • More than colour. Information isn't conveyed by colour alone, such as a required field that's only marked in red.
  • Control over motion. Content that moves on its own can be paused, and nothing flashes in a way that could trigger seizures.

The AODA names WCAG 2.0, but the guidelines have moved on: WCAG 2.2 is the current version. Building to a newer version also covers the older one, which is why every NOBL site is built to WCAG 2.1 AA as a minimum.

Accessibility isn't a feature you add at the end. It's a set of decisions made on every page, from the first sketch.

Five things you can check today

  1. Put your mouse away. Press Tab to move through your homepage. Can you reach every link and button, and can you always see which one is selected?
  2. Zoom to 200%. Text should get bigger without overlapping or disappearing off the side of the screen.
  3. Check your images. Do important images have alt text that says what they show, rather than a file name like IMG_2041.jpg?
  4. Look at your lightest text. Pale grey text on white is the most common contrast failure. If it's hard to read on your phone outside, it's probably failing.
  5. Watch a video with the sound off. If you can't follow it, it needs captions.

Why it's worth doing even if you're not required to

Disability is common, and it isn't always visible: low vision, colour blindness, hearing loss, tremors, migraines, concussion, ADHD. Add temporary injuries, ageing eyes and anyone reading on a phone in bright sunlight, and accessible design simply means a website more people can use.

It also tends to make sites better for everyone. Clear headings, descriptive links and readable text help people skim, and give search engines a cleaner picture of what each page is about.

How NOBL handles it

Every Launch and Managed website is built to WCAG 2.1 AA: contrast checked for every colour pair, keyboard-tested, with real headings and labels, and motion that respects the "reduce motion" setting on your device. If your current site needs an accessibility review before a redesign, that's part of the planning in our Managed package.

Ready to stand out?

Start a project

nick@noblweb.ca · (613) 301-7171