AODA and WCAG Website Procurement Checklist for Ontario Businesses

Accessibility expectations belong in the project scope

A vague promise that a website will be accessible is difficult to test or maintain. Ontario organizations should confirm current legal obligations with qualified guidance and translate the intended accessibility standard into design, content, development, vendor, and acceptance requirements.

What to review

• Confirm which organization, content, and current AODA requirements apply.
• Set specific WCAG criteria and supported browsers, devices, and assistive workflows.
• Include documents, media, forms, third-party tools, authoring, and future updates in scope.
• Require issue evidence, remediation responsibilities, retesting, and known limitations.

A practical implementation plan

1. Define obligations and users

   Review current requirements and identify the customer and staff tasks the site must support.

2. Write testable acceptance

   Specify semantic, keyboard, contrast, zoom, forms, media, responsive, and screen-reader expectations.

3. Plan ongoing ownership

   Train content owners, audit releases, track defects, and maintain an accessible feedback path.

What to measure

Record automated and manual findings, severity, affected journeys, remediation, retesting, user feedback, and recurring content errors. This guide is general planning information, not legal certification.

Connect the insight to the customer journey

Ask providers to explain their testing method and evidence rather than accepting a badge or automated score as proof of complete compliance.

Review MSPixelPulse website services · Browse website project examples · Compare website starting points