AODA and ACA document obligations
What Ontario's AODA and the federal Accessible Canada Act require for documents: who is covered, the WCAG standards, compliance reporting, and how the two laws interact.
By DocoMatic Team
Published September 14, 2026 · Updated September 14, 2026
Canadian document accessibility runs on two tracks: Ontario's AODA, with its WCAG-based web standard and compliance reporting, and the federal Accessible Canada Act, with published accessibility plans and feedback obligations for federally regulated bodies. This guide maps what each demands for documents, and what to do if both apply to you.
What does AODA require for documents on websites?
Ontario's Integrated Accessibility Standards Regulation requires designated organizations' public websites and their web content — including posted documents — to conform to WCAG 2.0 Level AA. The obligation attaches to sites and content published since the regulation's phase-in, and organizations file recurring compliance reports attesting to it.
- Who is designated: public sector and larger private organizations
- WCAG 2.0 AA as the IASR's named standard for web content
- Which documents the web-content obligation reaches
- The accessible-formats-on-request duty alongside the web standard
Who has to file AODA compliance reports, and when?
Obligated organizations file accessibility compliance reports with the province on a recurring cycle — government and public sector on one cadence, businesses and non-profits above the size threshold on another. The report is an attestation; filing inaccurately is its own problem, so the documents must actually comply (Ontario.ca: accessibility compliance reports).
- Reporting cycles by organization category
- What the report attests regarding web content
- Enforcement: audits, orders and penalties under AODA
What does the Accessible Canada Act require?
The ACA applies to federally regulated entities — banks, telecoms, transport, broadcasting and the federal government — and requires published accessibility plans, feedback mechanisms and progress reports. Documents figure twice: the plans themselves must be accessible, and the plan must address information and communication barriers, which posted documents are.
- Covered entities under the ACA
- Accessibility plans, feedback processes and progress reports
- Accessible formats of the plan on request, with set timelines
- Regulators: Accessibility Commissioner, CRTC, CTA
How do AODA and the ACA interact?
They stack. A federally regulated business operating in Ontario can owe ACA plans federally and AODA compliance provincially; a provincial public body owes AODA and may also face procurement and funding conditions. Other provinces add their own laws — Manitoba, Nova Scotia, British Columbia and Quebec each have regimes.
- Federal vs. provincial jurisdiction over the same organization
- Other provincial laws in brief
- Practical rule: build to the strictest standard you owe
What should a Canadian organization do about its documents?
The work looks like Title II preparation: inventory posted documents, remediate to WCAG (2.0 AA at minimum for AODA; 2.1 AA is the safer target), fix templates so new documents comply, and keep evidence aligned to the reporting cycle rather than scrambling before each filing.
- Inventory and triage of posted documents
- Remediating to WCAG with PDF/UA as the PDF profile
- Evidence keyed to AODA report dates and ACA progress reports
How does DocoMatic handle Canadian requirements?
DocoMatic remediates and verifies to WCAG 2.1 AA and PDF/UA, which satisfies AODA's WCAG 2.0 AA floor, and its reporting gives Canadian organizations the per-document evidence to stand behind an AODA attestation or an ACA progress report — in English and French.
- Standards coverage relative to AODA and ACA expectations
- Reporting aligned to compliance filings
- French-language documents and bilingual publishing