Websites & Design

AODA Website Compliance: Who Must Comply, What It Costs and the Overlay Trap

AODA website compliance explained: which Ontario organisations must meet WCAG 2.0 AA, the 31 Dec 2026 report deadline, what fixes cost and why overlays fail.

The short answer

AODA website compliance applies to Ontario's designated public sector organisations and to businesses and non-profits with 50 or more employees, whose public websites and web content published since 2012 have had to meet WCAG 2.0 Level AA since 1 January 2021. Organisations with 20 or more employees must also file an accessibility compliance report by 31 December 2026. Fixing a typical small business site costs a few thousand dollars in audit and remediation, and an accessibility overlay widget does not get you there. This is general information, not legal advice.

Who the AODA website rules actually cover

The Accessibility for Ontarians with Disabilities Act sets its web requirements in the Integrated Accessibility Standards Regulation. The Ontario government's guide How to make websites accessible (updated 21 September 2026) sets out the scope:

  • Who: designated public sector organisations, and businesses or non-profits with 50 or more employees.
  • What: public websites and web content, meaning text, images, forms and sounds on a web page or web application, published after 1 January 2012.
  • Standard: WCAG 2.0 Level AA, which includes all Level A criteria, with two exceptions: live captions (1.2.4) and pre-recorded audio descriptions (1.2.5).
  • Since when: 1 January 2021.
  • Control: the rules apply to any organisation that controls a website directly or through a contract. Hiring an agency does not move the obligation.
  • Not covered: intranets and extranets, though accessible formats must be provided on request.

Two points catch people out. First, "employees" means your Ontario headcount under the regulation, so a 60-person company with a 10-page brochure site is in scope while a 12-person consultancy with a complex portal is not. Second, the standard is WCAG 2.0 AA, not the newer 2.1 or 2.2. Our WCAG glossary entry explains the versions; the short version is that anything built to 2.2 AA also satisfies 2.0 AA, so build to the current standard. Law firm Gowling WLG notes that Ontario is expected to move to WCAG 2.2 by 2027.

Smaller organisations are not off the hook entirely. The Ontario Human Rights Code applies to every business, and an inaccessible website can be the subject of a complaint regardless of headcount. The AODA threshold is about the specific web standard, not about whether accessibility matters.

Deadlines, reports and penalties

Separately from the web standard, Ontario's accessibility compliance report page (updated 19 February 2026) requires businesses and non-profits with 20 or more employees to file a report every three years. The next deadline is 31 December 2026. The page warns that failing to file "could face enforcement measures which can include financial penalties." Gowling WLG's August 2026 briefing puts the statutory maximums at $100,000 per day for corporations and $50,000 per day for individual directors and officers. Most enforcement is far below those ceilings, but the report is a legal obligation, not an option.

The reporting rule and the web rule have different thresholds. A 30-person company must file the report, and will be asked whether its website meets WCAG 2.0 AA, but is not legally required to meet it. A 50-person company must do both.

Find out what it would cost to bring your website up to WCAG 2.0 AA before the 31 December 2026 report deadline

Tell the quote builder about your current site and whether you need a fix or a rebuild, and get a fixed-price range for accessible design and development compared with typical market prices.

Get My Free QuoteAbout 3 minutes · compared with typical market prices · no obligation
Decision tree showing which AODA web obligations apply by Ontario organisation type and employee count: public sector and organisations with fifty or more employees must meet WCAG 2.0 AA; twenty to forty-nine must file a compliance report; fewer than twenty have neither obligation but remain subject to the Human Rights Code. Which AODA web obligations apply to your organisation? Ontario organisation with a public website Designated public sector Business/non-profit 50+ employees Business/non-profit 20 to 49 employees Business/non-profit under 20 employees WCAG 2.0 AA since 1 Jan 2021 Report every 2 yrs last due 31 Dec 2025 WCAG 2.0 AA since 1 Jan 2021 Report every 3 yrs next due 31 Dec 2026 No WCAG mandate under the regulation Report every 3 yrs next due 31 Dec 2026 No WCAG mandate under the regulation No report required Human Rights Code still applies
Figure: AODA web standard and reporting obligations by organisation type and size, as of October 2026. (Sources: Ontario.ca, How to make websites accessible and Completing your accessibility compliance report. Flowmatix illustration.)

What most websites get wrong

You do not need a lawyer to guess where your site fails. The WebAIM Million, an automated evaluation of the home pages of the top one million websites, found in its 2026 edition that 95.9 percent had detectable WCAG 2 failures, averaging 56.1 errors per page. The most common were low-contrast text (83.9 percent of home pages), missing alternative text on images (53.1 percent), missing form labels (51 percent), empty links (46.3 percent), empty buttons (30.6 percent) and a missing document language (13.5 percent).

Those six items account for the bulk of detectable failures, and all of them are cheap to fix in a site you control. The expensive problems are structural: keyboard traps in custom menus, forms with no error messaging, videos without captions, PDFs that are scans of paper, and colour palettes chosen before anyone checked contrast. Those are design decisions, which is why accessibility is far cheaper to build in during a redesign than to retrofit. If a redesign is on the table anyway, our website redesign checklist includes the accessibility steps, and our redesign cost guide explains how the requirement affects price.

What AODA website compliance costs to fix

Costs depend on the size of the site and how it was built, so published figures are a guide, not a quote. An accessibility services firm's January 2026 pricing guide gives these US-dollar ranges for audits: automated scan only, US$0 to US$500; scan plus a summary review, US$500 to US$2,500; manual expert audit of a small site with up to about ten templates, US$2,500 to US$7,000; manual audit of a mid-size or complex site, US$7,000 to US$20,000. For remediation it suggests budgeting one to three times the audit fee for a site with typical issues, and more where the problems are structural. It also notes that free and low-cost automated scans "only catch roughly 30 to 40 percent of WCAG issues", so a scan alone is not an audit.

A more useful way to think about cost is by what drives it:

Cost driverCheaperMore expensive
TemplatesFew, consistent page typesMany bespoke layouts
ComponentsStandard menus, forms, buttonsCustom sliders, modals, maps, calculators
ContentText and imagesVideo, audio, PDFs, data tables
PlatformSite you control the code ofBuilder or theme that fights you
TestingAutomated plus a manual passTesting with assistive technology users
OngoingTrained staff adding content properlyRe-auditing after every content change

For a typical small business site with a handful of templates, the realistic path is a manual audit, a round of template fixes by a developer, a content pass for alt text, headings and contrast, and a short training session for whoever edits the site. Where the site is old or built on a platform you cannot change, a rebuild to an accessible standard is often the same cost as remediation and leaves you with a better site. Our web design and website redesign work is built and tested to WCAG from the first wireframe, which is how we keep the compliance line item small.

The overlay trap

You will be sold a widget. Overlay products promise AODA or WCAG compliance from a single line of JavaScript, often for a modest monthly fee. The Overlay Fact Sheet, signed by 1,048 accessibility practitioners, lawyers, assistive technology contributors and disabled users, is blunt: overlays can add basic features and apply some automated fixes, but they cannot reliably fix form labels, error handling, focus control or keyboard access, and "full compliance cannot be achieved with an overlay."

Regulators agree. In April 2025 the US Federal Trade Commission finalised an order requiring overlay vendor accessiBe to pay US$1 million and barring it "from representing that its automated products can make any website WCAG-compliant" without evidence. The order binds one company, but the lesson is general: automated tools find and fix a portion of issues, and a person still has to do the rest. Our article on AI and AODA accessibility goes deeper into what automation can and cannot do.

Key takeaways

  • WCAG 2.0 AA is mandatory for Ontario public sector bodies and for businesses and non-profits with 50 or more employees; organisations with 20 or more must file a compliance report by 31 December 2026.
  • Six common failures (contrast, alt text, form labels, empty links and buttons, document language) make up most detectable errors and are cheap to fix on a site you control.
  • Published 2026 guides put a manual audit of a small site at roughly US$2,500 to US$7,000 with remediation at one to three times that; a rebuild is often comparable and leaves you better off.
  • Overlay widgets do not deliver compliance; build and test to WCAG 2.2 AA instead, which also satisfies the 2.0 requirement.

Frequently asked questions

Does AODA apply to my small business website?

The WCAG 2.0 AA website requirement applies to Ontario businesses and non-profits with 50 or more employees and to designated public sector organisations. If you have 20 to 49 employees you must file an accessibility compliance report every three years, next due 31 December 2026, but the web standard is not mandated. Under 20 employees, neither applies, though the Human Rights Code still does.

Is WCAG 2.1 or 2.2 required under AODA?

No. The regulation names WCAG 2.0 Level AA, excluding live captions and pre-recorded audio descriptions. Because WCAG is backward compatible, a site that meets 2.2 AA also meets 2.0 AA, so building to the current standard is the sensible choice and prepares you for an expected move to 2.2.

Will an accessibility overlay make my website AODA compliant?

No. Overlays can add some features and automated fixes, but they cannot reliably repair form labels, keyboard access, focus order or error messaging, and more than a thousand accessibility professionals have signed a statement that full compliance cannot be achieved with one. In 2025 the US FTC fined one overlay vendor US$1 million over compliance claims.

Sources

  1. How to make websites accessible — Government of Ontario, updated 21 September 2026
  2. Completing your accessibility compliance report — Government of Ontario, updated 19 February 2026
  3. AODA Reporting Deadline 2026: What Ontario Employers Must Do — Gowling WLG, 25 August 2026
  4. The WebAIM Million: The 2026 report on the accessibility of the top 1,000,000 home pages — WebAIM, 2026
  5. How Much Does a Website Accessibility Audit Cost? Pricing Guide — eSEOspace, 2 January 2026
  6. Overlay Fact Sheet — overlayfactsheet.com
  7. FTC Approves Final Order Requiring accessiBe to pay $1 Million — US Federal Trade Commission, 22 April 2025

How Flowmatix can help

We put this into practice for businesses in Toronto and around the world through our Website Design & Development, website redesign, ui/ux design services. Want to know what it would take for your business? Get a personalised quote in about 3 minutes.

Have an idea?

Ready to see what your project costs?

Answer a few questions and get a personalised plan, a comparison with typical market prices, and a clear next step. No obligation, no sales pressure.

Contact us