AODA website accessibility: scope, WCAG and a practical review checklist

Identify whether the public-website requirement applies

Ontario identifies designated public-sector organizations and businesses/non-profits with 50 or more employees as subject to the public-website accessibility requirement. Direct or contractual control over the website is relevant.

Ontario’s guidance addresses websites and content published after January 1, 2012. Internal websites and certain other scope questions require separate checking. Do not label every password-protected customer service, outsourced website or third-party product exempt without examining the facts.

Use the actual Ontario standard, not an invented deadline

Ontario’s public-website guidance describes WCAG 2.0 Level AA, with specified exceptions for live captions and prerecorded audio descriptions. These are existing requirements, not a new general website deadline created by the December 2026 reporting date.

Newer accessibility standards may be relevant as good practice or under other commitments and laws, but do not silently substitute a newer WCAG version when describing the specific AODA rule. Keep the legal requirement, recommended improvements and contractual requirements distinguishable.

Combine technical checks with human testing

Automated tools can identify some technical issues. They do not establish complete conformance. Plan appropriate keyboard, screen-reader, zoom, contrast, form-error, document and user-journey testing with people who understand accessibility.

The readiness tool asks whether a scoped assessment and remediation evidence are available. It does not fetch private systems, certify a URL or claim that installing a widget fixes the website. A provider’s assurance should be checked against the scope and evidence of the work actually done.

• Identify the websites, applications and relevant documents.
• Confirm control and the applicable content scope.
• Arrange automated and manual review as appropriate.
• Prioritize and remediate identified barriers.
• Retest changes and keep meaningful evidence.

Exceptions are not automatic passes

Ontario gives specific guidance about older content, conversion limitations and control over external products. A claimed exception should be documented and reviewed against that guidance. The tool keeps uncertainty visible rather than treating it as ready.

Other accessible-format and human-rights duties may remain relevant even where a particular website-conformance requirement does not apply. For example, a smaller organization should not assume that it can ignore an individual’s request for an accessible way to obtain essential information.

Official sources and scope

• Ontario: public-website requirements
• Ontario: scope and exceptions
• IASR: information and communications standards

General information, not legal advice or a compliance certificate. Check coverage, governing requirements and actual implementation. A report-preparation pack is not an official filing. Individual circumstances and specialist standards may require qualified advice.