AI and AODA Website Accessibility: What AI Can Fix, What It Can't, and Overlays

The short answer

Under Ontario's AODA, businesses and non-profits with 50 or more employees must make public websites meet WCAG 2.0 Level AA, and have had to since 1 January 2021. AI tools can speed up parts of that work, like drafting alt text or captions and finding errors, but they cannot make a site compliant on their own, and the US Federal Trade Commission fined one AI overlay vendor US$1 million for claiming otherwise. This is general information, not legal advice.

What AODA WCAG rules require of your website

The Accessibility for Ontarians with Disabilities Act (AODA) sets its website rules in the Integrated Accessibility Standards Regulation (O. Reg. 191/11). The Ontario government's guide How to make websites accessible (updated September 2026) summarises them:

• Who: designated public sector organisations, and businesses or non-profits with 50 or more employees.
• What: public websites and web content posted after 1 January 2012 must meet WCAG 2.0 Level AA.
• Exceptions: live captions (success criterion 1.2.4) and pre-recorded audio descriptions (1.2.5). Internal sites need not meet AA, but accessible formats must be provided on request.
• Who is responsible: the organisation that controls the site, directly or through a contract. Hiring an agency does not move the obligation.

Separately, businesses and non-profits with 20 or more employees must file an accessibility compliance report every three years. According to Ontario's reporting page, the next deadline is 31 December 2026, and failing to file can lead to enforcement, including financial penalties. Law firm Gowling WLG puts the maximum at $100,000 per day for corporations and $50,000 per day for individual directors and officers.

WCAG 2.0, 2.1 or 2.2?

AODA names WCAG 2.0. The current W3C Recommendation is WCAG 2.2, which adds nine success criteria to 2.1 (including larger target sizes and easier authentication) and removes one, 4.1.1 Parsing. W3C states that content conforming to WCAG 2.2 also conforms to 2.0 and 2.1. Building to 2.2 AA is therefore a sensible target: it meets the AODA bar and prepares you for clients, procurement rules and other jurisdictions that reference newer versions. See our WCAG glossary entry for a plain-language primer.

Where AI genuinely helps

Used by people who understand accessibility, AI tools save real time on the repetitive parts of the job:

• Alt text drafts. A model can describe an image; a person decides what the image is for on that page, which is what alt text should convey.
• Captions and transcripts. Speech-to-text gets you most of the way; a human corrects names, jargon and speaker labels.
• Plain-language rewrites of dense policy or service text.
• Finding problems at scale. Automated scanners flag missing labels, low contrast and empty links across hundreds of pages.
• Code suggestions for ARIA attributes, heading structure and form labels, reviewed by a developer.

Where AI falls short, and why overlays are risky

The W3C's Web Accessibility Initiative is clear in its guidance on selecting evaluation tools: tools "can not determine accessibility, they can only assist", and "Human judgement is required." Many WCAG criteria are about meaning and experience. Is the focus order logical? Does an error message tell the user how to fix the problem? Does the alt text serve the page? A model can guess. It cannot know.

Accessibility overlays are scripts, often marketed as AI-powered, that sit on top of a website and try to repair it in the browser. The problem is that they patch symptoms at run time while the underlying code stays broken, and their claims have outrun what they deliver. In April 2025 the FTC approved a final order requiring accessiBe to pay US$1 million. The FTC alleged the company's claims that its AI tool could make any website WCAG-compliant were false, misleading or unsubstantiated, and that it formatted third-party reviews to look independent. The January 2025 announcement sets out the terms: no claims that the automated product can make any website WCAG-compliant, or keep it compliant over time, without evidence, and no presenting paid or connected reviews as independent.

That case was brought under US law, but the lesson travels. AODA puts the obligation on the organisation that controls the website. A tool vendor's promise does not transfer it, and a widget that changes how a page looks for some users does not fix keyboard traps, unlabelled form fields or confusing error messages in the underlying code.

If a vendor promises one line of code will make you AODA-compliant, treat it as a red flag rather than a solution.

A sensible plan for an Ontario business

1. Check whether you are in scope: 50+ employees for the website rule, 20+ for the compliance report.
2. Run an automated scan of key templates and pages to find the obvious issues fast.
3. Test the important journeys manually with a keyboard and a screen reader: contact form, booking, checkout, account login.
4. Fix in the source. Templates and components first, so each fix carries across the site. If the codebase cannot support it, a website redesign may be cheaper than patching.
5. Use AI for volume, people for judgement. Let AI draft alt text and captions; have someone review every one that matters.
6. Bake it into maintenance. New content and plugins can break accessibility, so include checks in regular upkeep, as covered in what website maintenance involves.
7. File your compliance report before 31 December 2026 if you have 20 or more employees.

Key takeaways

• AODA requires WCAG 2.0 AA on public websites for organisations with 50+ employees; building to WCAG 2.2 AA covers it.
• Businesses with 20+ employees must file an accessibility compliance report by 31 December 2026.
• AI is useful for drafting and scanning, not for certifying compliance.
• Overlays that promise instant compliance have drawn regulatory action; fix the code instead.

Frequently asked questions

Does AODA apply to small businesses' websites?

The WCAG website requirement applies to businesses and non-profits with 50 or more employees, and to designated public sector organisations. Smaller organisations still have other AODA duties, and making a site accessible is good practice and good for customers regardless.

Can an AI accessibility overlay make my site AODA compliant?

No tool can guarantee that. W3C says tools can only assist in evaluating accessibility, and the FTC ordered one overlay vendor to pay US$1 million over claims that its AI product could make any website WCAG-compliant.

Which WCAG version does Ontario require?

The regulation requires WCAG 2.0 Level AA, with exceptions for live captions and pre-recorded audio descriptions. Because WCAG 2.2 content also conforms to 2.0, many organisations build to 2.2 AA.

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. Web Content Accessibility Guidelines (WCAG) 2.2 — W3C Recommendation, 12 December 2024
5. Selecting Web Accessibility Evaluation Tools — W3C Web Accessibility Initiative, updated 13 May 2024
6. FTC Order Requires Online Marketer to Pay $1 Million for Deceptive Claims that its AI Product Could Make Websites Compliant with Accessibility Guidelines — Federal Trade Commission, January 2025
7. FTC Approves Final Order Requiring accessiBe to pay $1 Million — 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.