AODA Website Compliance in Ontario: Requirements and Checklist

Updated: 5 days ago
AODA website compliance concerns accessibility obligations under Ontario’s Accessibility for Ontarians with Disabilities Act and its regulations. It is also a practical usability issue: customers need to read information, use navigation and complete forms regardless of how they access the site.
The applicable obligations depend on the organization and content. This guide summarizes official website guidance and gives a starting workflow; it is not a legal determination that a particular site complies.

Who must meet Ontario’s public website requirements?
Ontario’s website accessibility guidance states that designated public sector organizations and businesses or non-profits with 50 or more employees are subject to the public website requirements.
The specified standard is WCAG 2.0 Level AA, with exceptions for live captions and pre-recorded audio descriptions. The guidance addresses public websites and web content posted after January 1, 2012.
Businesses and non-profits with fewer than 50 employees are not subject to these particular IASR website requirements. That is not a blanket exemption from every accessibility obligation. Confirm the requirements that apply to your organization rather than relying on employee count alone.
AODA and WCAG are different
AODA is Ontario legislation. WCAG is a set of technical accessibility guidelines from the World Wide Web Consortium. The W3C overview explains WCAG 2.0, 2.1 and 2.2.
For a new project, define both the legal baseline and the accessibility standard required by the contract. A newer WCAG version can be a project target without changing the version named in Ontario’s published website rule.
Start with the tasks people must complete
List important journeys: finding a service, reading a document, booking an appointment, submitting an enquiry or making a purchase. Review a representative page from each template and every important form.
A homepage-only scan cannot describe the accessibility of a checkout, downloadable document or booking interface. Give each journey an owner and include it in the project scope.
Run an initial accessibility review
The W3C Easy Checks resource provides an introductory review of issues such as page titles, headings, image alternatives, contrast, keyboard use and form labels. It explicitly says quick checks are not a comprehensive evaluation.
As an initial practical exercise:
Navigate the menu and form with a keyboard.
Check that you can tell which control has focus.
Confirm that fields have meaningful labels and errors are understandable.
Zoom the page and check whether information remains usable.
Review image alternatives in the context of the page.
Check captions and the accessibility of important documents.
Record the page, task, observed barrier and expected behaviour. “The form is inaccessible” is difficult to action; “keyboard focus cannot reach the submit button after selecting a service” gives a reviewer a reproducible problem.
Plan remediation and verification
Assign issues to content, design or development work. Fix a barrier in the shared template when that is where it originates, then test affected pages again.
Prioritize obstacles that prevent essential tasks. For example, a customer unable to submit an enquiry needs a functioning alternative while the form is repaired. Keep a record of the change and the verification method.
Automated tools can help locate issues, but do not treat a clean scan, accessibility widget or platform choice as a compliance certificate. Arrange a suitably scoped evaluation when a formal conformance assessment is required.
Keep accessibility in ongoing publishing
Create a short editorial process for new headings, images, videos, forms and documents. Include accessibility review when installing an app or changing an enquiry workflow.
A clear feedback route helps people report a barrier. Decide who receives that message and how the issue will be investigated; publishing a statement without a response process does not complete the task.
Review a complete task, not only a home page
Choose a task a visitor needs to complete, such as finding a service, reading a document or sending an enquiry. Follow that task through every relevant page and interaction. Include the navigation, form labels, validation messages, confirmation and any embedded booking or payment interface.
Record each obstacle in practical terms. “The submit button cannot be reached with the keyboard” is more useful to a developer than “the form fails accessibility.” Include the page, the steps, the observed behavior and the expected result. Avoid placing real customer information in screenshots used for testing.
W3C’s Easy Checks covers useful starting checks such as headings, image alternatives, keyboard access and forms. It also explains that these preliminary checks are not a complete evaluation. Use them to find and prioritize barriers, then arrange the appropriate deeper assessment.
Give each repair an owner and a way to verify it
Separate a content repair from a component repair. An unclear link label may be corrected in the article editor. A keyboard problem in a shared menu may require a change to the site component. An embedded third-party service may need a vendor response or an alternative way to complete the task.
After a repair, repeat the original steps. Check another page that uses the same component and test the relevant mobile layout. Keep the result with the issue record so the next person can understand what was checked. A scanner score alone does not explain whether a person can complete the business task.
Make accessibility part of routine publishing
Use a short publishing review for new articles: a descriptive title, logical section headings, readable paragraph spacing, meaningful image alternatives and links that identify their destination. Preserve useful captions and provide the important information as text when an image contains instructions or data.
For documents and videos, include them in the review rather than assuming the surrounding web page makes them accessible. Assign someone to review changes to forms, menus and templates before they are rolled out across the site. Repeated problems often originate in a shared component or a publishing habit.
Keep the legal scope and the improvement plan distinct
The legal obligations applying to a particular organization depend on its circumstances. Use the Ontario government sources linked in this guide and obtain qualified advice for an organization-specific interpretation. A practical improvement plan can still begin with the barriers preventing people from using the website.
Keep a record of the scope reviewed, the tools and manual checks used, the findings, completed repairs and remaining work. Avoid describing a limited review as a certification of the entire website. Clear records support a maintainable process and help the team respond to future changes.
Does a Wix website automatically comply?
Compliance depends on the implementation and content, including third-party features. Review the published site and the tasks visitors need to complete.
Is WCAG 2.2 the AODA website rule?
Ontario’s cited website guidance specifies WCAG 2.0 AA with stated exceptions. WCAG 2.2 may be a useful additional project target; distinguish it from the legal baseline.
For help scoping design and development work, contact CodeMasters. Describe the site, important visitor tasks and any audit findings already available.

