AODA web design Ontario compliance for agencies

What to take away

The Accessibility for Ontarians with Disabilities Act, 2005 (AODA) applies to website operators with 50 or more employees in Ontario, covering private businesses, non-profits, and designated public sector bodies.

Agencies scope AODA web design Ontario compliance around that employee threshold. Ontario's AODA statute sets the general duty; the Integrated Accessibility Standards Regulation fills in website obligations.

The AODA website deadline and the standard

Section 14 of the Integrated Accessibility Standards Regulation (O. Reg. 191/11) is the website rule for Ontario. It applies to designated public sector organizations and to private and non-profit organizations with 50 or more employees.

Public websites and web content posted after January 1, 2012 had to conform to WCAG 2.0 Level AA by January 1, 2021. Two success criteria are excluded from that requirement: live captions (1.2.4) and audio description (1.2.5).

Who has jurisdiction in Ontario

The duty falls on an organization that provides goods, services, or facilities to the public or to Ontario residents and has at least 50 employees in Ontario. Smaller agencies can still face client-contract duties to deliver accessible work. Designers should confirm whether the client is a designated public sector organization or a business with 50 or more Ontario employees before scoping a site. The trigger is the employer's employee count, not the number of users or visitors.

AODA website requirements at a glance

For an agency, AODA website requirements Ontario mean testing every new page against WCAG 2.0 Level AA guidelines, not just the homepage.

Ontario web work under that compliance includes text alternatives for images and keyboard access for all functions. Color contrast of at least 4.5:1 is required for normal text. The Integrated Accessibility Standards Regulation does not reference the US Section 508 standard or the ADA.

Agencies that add web accessibility services often need to train designers on WCAG 2.0 Level AA before they accept an AODA-bound project.

What a compliant disclosure contains

A compliant disclosure is not a single badge or statement like "we are accessible". Under O. Reg. 191/11, designated public sector organizations and organizations with 50 or more employees must each keep an accessibility policy (section 3) and a multi-year accessibility plan (section 4) that sets out how the organization will meet its accessibility requirements.

Section 12 requires the same organizations to provide accessible formats and communication supports on request, after consulting the person who made the request, and to notify the public that those formats and supports are available. Designers can help by building an accessibility page that names the standard, explains how to request an accessible format, and lists known limitations. That page must give a direct contact for inaccessible content.

Records to keep

These records matter because AODA enforcement does not start with a technical audit of every page. Inspectors ask for the policy, the multi-year accessibility plan, the Accessibility Compliance Report, and evidence of staff training. A missing record can turn a minor accessibility gap into a larger compliance finding.

Keep records in a shared client-owned folder, not only in a designer's project file.

If you have a web design maintenance contract, log every accessibility fix as a separate change. This keeps the record clear when a client asks what was addressed in each month.

Filing the Accessibility Compliance Report

Organizations with 50 or more employees must file an Accessibility Compliance Report with the Accessibility Directorate of Ontario, the office that administers the AODA. The report asks the organization to confirm whether it has met its accessibility requirements and to explain any requirement it has not met.

The Directorate publishes the filing cycle. The most recent deadline for organizations with 50 or more employees was December 31, 2023. An agency can prepare the website and training evidence the client needs in order to answer the report.

What happens if you do not

If an organization does not comply, the Director under the AODA can issue an order to comply, impose administrative penalties, or refer the matter for prosecution. A designer is rarely the direct target of AODA enforcement. The client is the regulated entity, but a designer can be named in a dispute or a professional negligence claim if the website fails the promised WCAG 2.0 AA standard. One concrete consequence is a financial administrative penalty against the client, which can then recover damages through the contract if the designer promised compliance but did not deliver. This is the Ontario web accessibility law for designers in practice.

Under AODA, a website is not a one-time compliance object. It is a standing obligation that reopens with every content change and every embedded video.

Where the rules differ by place

The AODA is a provincial law. It does not extend to agencies in Alberta or British Columbia unless they serve Ontario clients. The federal government follows the Accessible Canada Act, which has different deadlines and standards for federal entities. For a Toronto shop serving a Vancouver client, only the client's legal obligations under BC law apply, unless the contract explicitly adopts AODA standards. Agencies that deliver AODA work in Ontario often need to schedule the same projects using GST HST for web designers to keep tax reporting consistent.

Many Ontario clients assume accessibility stops at launch. That assumption is wrong. Each new PDF uploaded to the site creates fresh obligations under the regulation. A designer who hands off a site without telling the client how to manage accessible content has not finished the job.

If you are running a new Ontario studio, Incorporate web design business Canada helps you decide where to register, which affects which accessibility rules you report under.

Common questions