Canada regulates digital accessibility through a mix of provincial and federal laws, and most of them point to the same place: the Web Content Accessibility Guidelines. If you publish PDFs that Canadians read — statements, forms, brochures, policies — those documents are part of what the law expects to be accessible. This article walks through Ontario's AODA, the federal Accessible Canada Act, and the way other provinces are heading in the same direction.
This is general information, not legal advice.
The AODA: Ontario's accessibility law
The Accessibility for Ontarians with Disabilities Act (AODA) is the most developed accessibility law in Canada. Passed in 2005, it set a goal of making Ontario fully accessible, and it works by issuing detailed standards that organizations must meet on a schedule.
The standard that matters most for documents is the Integrated Accessibility Standards Regulation (IASR). Under the IASR's information and communications requirements, covered organizations must make their web content conform to WCAG 2.0 Level AA. That obligation reaches the content you publish online — and a PDF on your website is web content.
A few things make the AODA distinctive:
- It applies to both public and private sector organizations in Ontario, not just government.
- Obligations are scaled by organization size, with broader requirements for larger employers and public bodies.
- It is proactive and schedule-driven: rather than waiting for a complaint, the law phased in deadlines over more than a decade, and it requires periodic accessibility compliance reports filed with the province.
Who the AODA covers
The AODA reaches a wide range of organizations that operate in Ontario:
- Public sector bodies — the Ontario government, agencies, municipalities, school boards, colleges, universities, hospitals.
- Large private and non-profit organizations (generally those with 50 or more employees).
- Small private and non-profit organizations (generally 1 to 49 employees), with a lighter set of obligations.
The web-content requirements were phased in over time, with public-sector and large organizations expected to meet WCAG 2.0 AA across their websites and web content by the later milestones in the rollout. If you operate in Ontario at any meaningful scale, the practical assumption is that your public-facing documents are in scope.
The Accessible Canada Act: the federal layer
The AODA is provincial, so it does not reach everything. The federal Accessible Canada Act (ACA), which came into force in 2019, covers federally regulated entities — the parts of the economy Ottawa regulates rather than the provinces.
That federal sphere includes:
- Federal government departments and agencies, plus Crown corporations.
- Banks and the broader federally regulated financial sector.
- Telecommunications and broadcasting.
- Interprovincial transportation — airlines, rail, and inter-provincial bus and trucking.
The ACA's goal is a barrier-free Canada by 2040, and it requires covered organizations to identify, remove, and prevent barriers — including barriers in information and communication technologies. In practice, federally regulated organizations align their digital content, including documents, with WCAG as the recognized technical benchmark. So a bank, an airline, or a telecom serving Canadians faces document-accessibility expectations under federal law, even though it sits outside any single province's regime.
Other provinces are following Ontario
Ontario was first, but it is no longer alone. Several other provinces have enacted or are building accessibility legislation modeled on the same idea — standards plus a phased timeline — and the technical destination is consistently WCAG conformance for digital content.
- Manitoba has the Accessibility for Manitobans Act, with standards rolling out across areas including information and communication.
- British Columbia passed the Accessible British Columbia Act, establishing a framework for accessibility standards.
- Nova Scotia has the Accessibility Act, working toward an accessible province on a defined timeline.
- Quebec addresses accessibility through its own legislation and government standards for public bodies.
The takeaway is not that the rules are identical — they are not — but that the direction of travel is the same across Canada: proactive standards that treat web content and documents as something everyone should be able to use, measured against WCAG.
Canadian PDF and document obligations at a glance
| Law | Jurisdiction | Technical standard | Who's covered |
|---|---|---|---|
| AODA (Integrated Accessibility Standards Regulation) | Ontario | WCAG 2.0 Level AA for web content | Ontario public sector + private/non-profit orgs, scaled by size |
| Accessible Canada Act (2019) | Federal | WCAG as the recognized benchmark | Federally regulated entities — banks, telecom, interprovincial transport, federal government |
| Accessibility for Manitobans Act | Manitoba | WCAG-aligned (phased standards) | Public and private sector, by size |
| Accessible British Columbia Act | British Columbia | WCAG-aligned (framework + standards) | Public sector first, expanding |
Note that the AODA references WCAG 2.0 AA, an earlier edition than the WCAG 2.1 AA baseline used by the U.S. ADA Title II rule and the EU's EN 301 549. The practical gap is small: building to WCAG 2.1 AA satisfies 2.0 AA and future-proofs you. If you want the European reference standard for comparison, see our explainer on EN 301 549.
What this means for your PDFs
Whichever Canadian law applies to you, the document-level work is the same, because the standard underneath is WCAG. To make a PDF conform, it needs:
- Tags that define the document's structure (headings, paragraphs, lists).
- A logical reading order so a screen reader announces content in the order a person would read it.
- Alt text on meaningful images, and properly marked decorative images.
- Accessible tables with identified header cells.
- Labeled form fields if the document is fillable.
- Document metadata such as a title and language.
A scanned image of a page meets none of these — to a screen reader it is a blank wall. That is the single most common failure across Canadian organizations, especially for forms, statements, and older archived documents.
The reassuring part is that accessibility serves real people: roughly 1 in 4 adults lives with a disability, and a properly tagged PDF is the difference between a document they can use independently and one they cannot open at all. It is also work you do once per document and then maintain, rather than a moving target.
For a side-by-side view of how Canada lines up against the United States, the EU, and the UK, see our PDF accessibility law comparison. And for the broader international picture — including the European Accessibility Act and the global shift toward WCAG — start with our pillar guide on the European Accessibility Act and global PDF accessibility laws.
Key takeaways
- Ontario's AODA requires WCAG 2.0 Level AA for web content under the Integrated Accessibility Standards Regulation, applies to public and private organizations, and is scaled by size.
- The federal Accessible Canada Act (2019) covers federally regulated entities — banks, telecom, interprovincial transport, and the federal government — and aligns digital content with WCAG.
- Manitoba, British Columbia, and other provinces are enacting similar standards-based laws, all pointing toward WCAG conformance.
- Canada's AODA references the older WCAG 2.0 AA, but building to WCAG 2.1 AA satisfies it and matches U.S. and EU baselines.
- Compliance comes down to the same PDF fundamentals everywhere: tags, reading order, alt text, accessible tables and forms, and metadata.
