Ontario’s AODA website rule requires designated public sector organizations and businesses and non-profits with 50 or more employees to make the public websites and web content they control conform to WCAG 2.0 Level AA. The rule covers content published after January 1, 2012, including web-based applications, and has exceptions for live captions and pre-recorded audio descriptions. The January 1, 2021 deadline has passed; it is not a future grace period.
Who has to make a website accessible?
The website-conformance requirement applies to designated public sector organizations and to businesses and non-profits with 50 or more employees. Ontario encourages smaller organizations to make their websites accessible, but says organizations with fewer than 50 employees are not required to meet this particular website rule under the Integrated Accessibility Standards Regulation (IASR). See the Ontario website accessibility guidance.
As an Amazon Associate I earn from qualifying purchases.
Responsibility rests with the organization that controls the website and its content. Control can be direct or exercised through a contract that allows the organization to modify the site or content. Hiring a vendor does not by itself remove the organization’s responsibility when the contract gives it that control. The requirement also includes web-based applications, not just conventional web pages. The relevant rule is in Ontario Regulation 191/11, section 14.
Free tools Windows power users keep installed
One-click scans. No signup required.
What WCAG standard and level does Ontario require?
Covered websites and web content must conform to the World Wide Web Consortium’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA. The stated exceptions are success criterion 1.2.4, Captions (Live), and success criterion 1.2.5, Audio Descriptions (Pre-recorded). Ontario notes that in most cases Level A criteria must also be met before the required Level AA criteria can be met.
#1 Best Overall
This is the standard named in the Ontario regulation; do not assume that a different WCAG version automatically replaces it for this specific legal requirement. The regulation’s implementation schedule set January 1, 2021 as the deadline for covered organizations’ internet websites and web content to meet the requirement. That date is historical, and covered organizations should address current non-conformance rather than treat it as an upcoming deadline.
Which pages, content, and applications are in scope?
- Publication date: The rule applies to web content published after January 1, 2012.
- Control: It applies to sites and content the organization controls directly or through a contract that permits changes.
- Types of content: It includes public website content and web-based applications, as well as ordinary pages.
Ontario says internal intranets and extranets do not have to meet the public website WCAG 2.0 A/AA requirement. That does not eliminate the duty to respond to an individual’s accessibility needs: when someone asks for information in an accessible format, the organization must work with them to meet those needs. Ontario describes this distinction in its guidance on when public websites are not accessible.
Rank #2
Does a small business website need to comply?
For this website rule, an Ontario business or non-profit with fewer than 50 employees is not required to meet the IASR website accessibility requirements. It is still encouraged to make its website accessible. Do not confuse that threshold with accessibility reporting: businesses and non-profits with 20 or more employees have a separate reporting obligation. Public sector organizations are also covered under their own category, rather than by the business/non-profit employee threshold.
Are there exceptions if compliance is not practicable?
The regulation says the website requirements apply except where meeting them is not practicable. It allows relevant factors to be considered, including whether commercial software or tools are available and whether compliance would significantly affect implementation timelines planned or started before January 1, 2012. Ontario’s guidance describes circumstances in which the requirement may not apply.
This is a bounded, fact-specific exception, not a blanket exemption for older sites, vendor-managed sites, or organizations that find remediation difficult. Check the regulation and the organization’s actual circumstances before relying on it; record the basis for any decision.
How to assess and improve website accessibility
- Confirm coverage and control. Identify whether the organization is a designated public sector body or a business/non-profit with at least 50 employees. Determine which entity controls each relevant site, application, or content stream, including under vendor contracts.
- Inventory the scope. List public pages, web-based applications, and content published after January 1, 2012. Track content owners and any items whose publication date or control status needs confirmation.
- Assess against WCAG 2.0 Level AA. Review applicable success criteria, including the Level A criteria needed in most cases. Account for the regulation’s exceptions for live captions and pre-recorded audio descriptions.
- Use automated checks and manual review. Automated scans can help find some detectable issues, but human review is needed for matters that require judgment or interaction. Ontario’s government-service guidance recommends both manual and automated testing during beta; it does not establish that one scan or tool certifies legal compliance. See Making government services accessible.
- Track fixes and follow-up. Record the issue, affected pages or application, remediation decision, responsible owner, and follow-up check. Reassess changed content and functionality rather than treating an earlier scan as permanent proof.
- Check reporting separately. Determine whether the organization has a reporting duty and note the applicable cycle and deadline; the reporting threshold is not the same as the website-conformance threshold.
Website accessibility reporting deadlines are separate
As of October 4, 2026, Ontario says businesses and non-profits with 20 or more employees must file an accessibility compliance report every three years. Their next stated deadline is December 31, 2026. Designated public sector organizations report every two years; their December 31, 2025 deadline has passed, and Ontario says late filers should submit as soon as possible.
Rank #4
These reporting requirements do not change who is covered by the website-conformance rule or its historical 2021 deadline. Consult Ontario’s current pages for business and non-profit accessibility rules and public sector accessibility rules for reporting details.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsOr skip the browser setup
For documentation, issue tracking, or reviewing visual changes, ScreenshotNeo can capture a webpage through one API request. A screenshot is not an accessibility audit and does not establish WCAG conformance; use it as a visual aid alongside manual review and accessibility testing.
cURL example, saving a capture of the Ontario guidance page as WebP:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://www.ontario.ca/page/how-make-websites-accessible -o shot.webpSee the ScreenshotNeo API documentation for request options. ScreenshotNeo removes supported cookie/consent banners, newsletter popups, and chat widgets before capture; those cleanup steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server provides screenshot, page-info, and PDF tools for AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Frequently Asked Questions
Does buying an accessibility scanner make a website AODA-compliant?
No single scan is shown as proof of legal conformance. Use automated checks as one input, with manual review and documented remediation.
Does AODA require a particular commercial accessibility testing tool?
The cited Ontario guidance supports combining manual and automated testing but does not endorse a specific commercial tool.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
