Skip to content
Peter KagundaWeb Developer

AODA Compliant Web Design for Ontario Organizations

Accessible websites built and fixed to WCAG for Toronto and Ontario businesses, non-profits and agencies, with a clear audit, honest reporting and ongoing support.

AODA web design means building (or fixing) a website so it meets the accessibility rules that apply to organizations in Ontario under the Accessibility for Ontarians with Disabilities Act. In practice, that means conforming to the Web Content Accessibility Guidelines (WCAG) at Level AA. I'm Peter, a freelance web designer and developer who builds accessible WordPress, Shopify and custom websites, and audits and repairs existing ones, for businesses, non-profits and agencies in Toronto and across Ontario, including Mississauga, Ottawa, Hamilton and Durham Region towns such as Whitby and Oshawa.

In short: if your organization is in Ontario's public sector, or is a private business or non-profit with 50 or more employees, your public website and web content must meet WCAG 2.0 Level AA (with two exceptions for live captions and pre-recorded audio description). I design and build to WCAG 2.1/2.2 AA, which covers 2.0, and I can audit and fix an existing site.

Accessible website displayed on desktop, laptop and phone

What the AODA requires for websites

Website rules sit in the Information and Communications Standards of the Integrated Accessibility Standards Regulation (IASR, O. Reg. 191/11). The key points for most organizations are:

OrganizationWebsite requirementCompliance reporting
Ontario public sector (any size)WCAG 2.0 Level AAEvery two years
Private and non-profit, 50+ employees in OntarioWCAG 2.0 Level AA since 1 January 2021 (live captions and pre-recorded audio description excepted)Every three years
Private and non-profit, 20 to 49 employeesNo specific WCAG deadline, but general accessibility duties applyEvery three years
Private and non-profit, 1 to 19 employeesNo specific WCAG deadlineNot required

The rules apply to public-facing websites and web content you control, including PDFs and documents published on the site. Organizations that don't comply can face orders and administrative penalties, and the Act allows fines of up to $100,000 per day for corporations for offences. Ontario's own guide on how to make websites accessible is the official reference, and I'm a developer, not a lawyer, so for legal questions about your obligations please check with the Accessibility Directorate of Ontario or legal counsel.

Why build accessible even if you're under 50 employees

  • More customers: people with visual, hearing, motor or cognitive disabilities can actually use your site.
  • Better for everyone: clear headings, readable contrast and simple forms help people on small screens, in bright sunlight or in a hurry.
  • Better SEO: accessible structure, alt text and descriptive links also help search engines understand your pages.
  • Future-ready: if you grow past 50 employees, or win public-sector contracts, your site already meets the standard.

What AODA compliant web design looks like in practice

  • A logical heading structure (one H1, then H2s and H3s in order) and meaningful page titles
  • Colour contrast of at least 4.5:1 for normal text
  • Everything usable with a keyboard alone, with a visible focus indicator and a "skip to content" link
  • Descriptive alt text on informative images, and empty alt on decorative ones
  • Forms with visible labels, clear error messages and instructions that don't rely on colour
  • Captions for pre-recorded video and transcripts for audio
  • Menus, accordions, sliders and pop-ups that work with screen readers
  • Text that can be resized to 200% without breaking the layout
  • Accessible PDFs, or HTML alternatives

My AODA website services

1. Accessibility audit

I test key templates and pages with automated tools and, more importantly, by hand: keyboard-only navigation, a screen reader, zoom and contrast checks. Automated scanners only catch part of WCAG issues, so manual testing matters. You get a plain-English report listing each issue, the WCAG criterion it relates to, where it occurs and how to fix it.

2. Remediation

I fix the issues in your theme, templates and content: headings, contrast, focus styles, forms, menus, alt text and documents. I prioritise problems that block users completely, then work through the rest.

3. Accessible new builds and redesigns

For a new site or redesign, accessibility is part of the design from the first wireframe, which is far cheaper than fixing it later. I build on WordPress, Shopify or a custom stack.

4. Ongoing checks

New pages, plugins and uploads can break accessibility. A maintenance plan includes periodic checks so the site stays compliant.

5. White-label accessibility work for agencies

GTA agencies can hand me accessibility audits and fixes for client sites under their brand. See white-label web development.

A word on accessibility overlays

You'll see plug-in "overlay" widgets promising instant AODA or WCAG compliance with one line of code. They can't fix underlying problems in your code and content, and many disabled users find them get in the way. I don't rely on overlays; I fix the site itself.

How a project runs

  1. Send me your website address and a short note about your organization.
  2. I review a sample of pages and send a fixed quote for the audit, fixes or rebuild.
  3. I deliver the audit report, then fix issues on a staging copy so your live site isn't disrupted.
  4. We retest, publish the changes and, if you'd like, add an accessibility statement and feedback contact to your site.

I work remotely from Nairobi, seven to eight hours ahead of Toronto, so we meet in your morning and work continues after that. For more on the standard itself, read my website accessibility checklist, my website accessibility service page or my page for Toronto web design.

Frequently asked questions

Ontario's public sector organizations, and private businesses and non-profits with 50 or more employees in Ontario, must make public websites and web content meet WCAG 2.0 Level AA, except live captions and pre-recorded audio description.
The regulation names WCAG 2.0 Level AA. Building to WCAG 2.1 or 2.2 Level AA is good practice because the newer versions include everything in 2.0, plus extra criteria for mobile and low-vision users.
No. Overlay widgets can't fix the underlying code and content issues that WCAG covers, and they can interfere with screen readers. Real compliance comes from fixing the site itself.
It depends on the number of templates and the amount of content. For a typical small business site, an audit of the main templates usually takes a few days, and I confirm the timeline in a fixed quote.
Yes. I work remotely with organizations anywhere in Ontario and Canada, including Ottawa, Mississauga, Hamilton and Durham Region towns such as Whitby and Oshawa.

Want your website checked against AODA and WCAG?

Tell me what you need — I usually reply within one business day.

Start Your Project

Get a free quote