AODA Guide

Guide · researched Nov 5, 2026

Overlays and AODA: what accessibility widgets actually do

Bottom line: Never treat an overlay alone as AODA or WCAG compliance. Lead with manual testing and code/content fixes. Present overlays only as optional supplements.

What AODA expects for websites (high level)

Ontario’s government guidance states that designated public-sector organizations, and businesses/non-profits with 50+ employees, must make public websites accessible — rules in force since January 1, 2021 — referencing WCAG 2.0 Level AA (with limited exceptions). The organization that controls the site is responsible. See: How to make websites accessible (ontario.ca).

Organizations under 50 employees may still have other AODA duties (for example accessible formats on request) even when the website section does not apply the same way. Confirm your category on official pages — this site does not decide compliance for you.

Compliance reporting is a separate obligation for many orgs (filing schedules differ by sector). Business/non-profit cycles and website attestation questions should be confirmed on Ontario’s accessibility reporting resources before you file.

What an overlay typically is

An accessibility overlay (sometimes called a widget) injects a script that can offer UI adjustments — font size, contrast, pause animations — and may attempt automated “fixes.” That can help some users some of the time.

Overlays do not automatically make a site WCAG-conformant. They usually do not fix PDFs, weak heading structure authored in your CMS, or inaccessible third-party embeds. They also do not replace AODA organizational requirements such as training, feedback processes, or multi-year accessibility plans where those apply.

Why marketing claims need skepticism

A practical buyer path

  1. Scan key templates with free tools (e.g. axe, WAVE, Lighthouse) and save results.
  2. Do at least one human keyboard-only and screen-reader pass on contact/checkout flows.
  3. Map which AODA organizational requirements apply to your org type — separately from page-level WCAG checks.
  4. Ask any overlay vendor for a written statement of what they do not cover.
  5. Only then compare widget SKUs and prices — and still budget for remediation.

Sources

Last researched: November 5, 2026 (America/Toronto). Not legal advice. Re-check ontario.ca for current obligations and filing dates.