Compliance guide

Document accessibility in Canada: the December 2025 Accessible Canada Regulations and Ontario's AODA

Canada's amended Accessible Canada Regulations set December 2027 and 2028 dates for web pages, apps, and non-web documents against CAN/ASC-EN 301 549:2024. Who is covered, the exemptions, and how Ontario's AODA (WCAG 2.0 AA) applies to documents.

Updated September 2, 2026. Reviewed by the DocAccessible team under our editorial policy.

Canada has two accessibility regimes that reach documents: a federal one under the Accessible Canada Act, which acquired concrete technical requirements and dates only in December 2025, and provincial ones, of which Ontario's is the oldest and most specific. This guide records both as they stand in September 2026, with the federal dates that make 2027 and 2028 planning years for every federally regulated organisation.

The Accessible Canada Act and the 2025 amendments

The Accessible Canada Act (2019) applies to the federal government and federally regulated private-sector organisations: banks, telecommunications and broadcasting companies, interprovincial and international transportation, and Crown corporations, among others. The original Accessible Canada Regulations (SOR/2021-241) dealt with accessibility plans, feedback processes, and progress reports rather than technical standards. The Regulations Amending the Accessible Canada Regulations (SOR/2025-255), registered on December 5, 2025 and published in the Canada Gazette, Part II, on December 17, 2025, add the technical layer: regulated entities must ensure that newly created or updated web pages, mobile applications, and non-web documents conform, "to the extent feasible", to the national standard CAN/ASC-EN 301 549, Accessibility requirements for ICT products and services, incorporated by reference on an ambulatory basis so that later editions apply automatically. Accessibility Standards Canada adopted EN 301 549 V3.2.1 as CAN/ASC-EN 301 549:2024, so today's document requirements are clause 10 of the European standard and correspond to WCAG 2.1 Level AA; see EN 301 549 clause 10.

Who is covered and when

Compliance dates under SOR/2025-255, counted from the December 5, 2025 registration date, as set out in the Canada Gazette.
EntityWeb pagesMobile applicationsNon-web documents
Federal public sector (departments, agencies, Crown corporations, Parliamentary entities, RCMP, Canadian Armed Forces)December 5, 2027December 5, 2028 (new apps; existing apps need conformity assessments by then)December 5, 2028
Private sector, 500 or more employees (three-year average)December 5, 2028December 5, 2028December 5, 2028
Private sector, 100 to 499 employeesDecember 5, 2028Not requiredNot required
Private sector, 99 or fewer employeesExemptExemptExempt

Broadcasting and telecommunications entities and transportation service providers are excluded from these provisions (transportation providers keep employee-facing duties under their own accessible transportation regulations), and First Nations band councils are exempt until December 31, 2033. The Gazette notice explains the staged approach as giving the public sector two years for web pages and everyone else three, and confining mobile and document requirements to the largest entities.

"Newly created or updated" and "to the extent feasible"

The requirements attach to content created or updated after the applicable date, not to everything ever published. For documents, the Gazette explains that "any change to a digital document's content" is an update, while republishing an unchanged document generally is not. "To the extent feasible" is defined through factors: the availability of conforming technology, obstacles to implementation, and "the regulated entity's degree of control over the web page, mobile application or non-web document, including under any agreement with a third party". Where full conformity is not feasible and a barrier results, the entity must provide alternative means of accessing the key information or performing the tasks. Three categories are exempted outright: heritage content (reproductions kept primarily for historical, artistic, or aesthetic interest), user-generated content such as consultation submissions, and documents employees share in internal collaborative environments. Maps, technical drawings, and images must conform only to the extent feasible, without a duty to provide alternative access.

What a federally regulated organisation should do

  1. Fix the publishing pipeline before December 2027 so that every new or updated web page and, for the largest entities, every new or updated document conforms; the export matrix and the statements at scale guide cover the two places documents come from.
  2. Inventory existing documents to know which will be "updated" and therefore captured; the free website PDF scanner lists public PDFs and where they are linked.
  3. Document feasibility decisions and the alternative means offered, because the regulation ties the obligation to them.
  4. Publish bilingually with correct language tagging; the language tagging guide covers French and English sections in one file.
  5. Keep accessibility plans, feedback processes, and progress reports current, since those obligations continue.

Ontario: the AODA and documents

Ontario's Integrated Accessibility Standards Regulation (O. Reg. 191/11) under the Accessibility for Ontarians with Disabilities Act has required, since January 1, 2021, that designated public sector organisations and businesses or non-profits with 50 or more employees make all public websites conform to WCAG 2.0 Level AA, except for success criteria 1.2.4 (live captions) and 1.2.5 (pre-recorded audio descriptions). The requirement applies to websites and to web content published on a website after January 1, 2012, and the organisation that controls the site, directly or through a contract, is responsible. Ontario's guidance addresses documents directly: where it is not practicable to make content conform, the organisation may post it but must explain why the information is unconvertible and, on request, provide a summary of the unconvertible content; and when a person requests an accessible format such as large print or braille, the organisation must work with them to meet their needs. In practice a PDF published on an Ontario public site since 2012 is web content that should meet WCAG 2.0 AA, and the WCAG 2.2 AA document guide covers everything 2.0 AA asks plus the later additions.

Other provinces

Manitoba, Nova Scotia, British Columbia, and others have accessibility legislation at various stages, and Quebec's government standards apply to provincial bodies. None is as specific about documents as Ontario's regulation or the new federal rules, and an organisation operating across Canada will usually meet all of them by building to the federal standard. The laws by jurisdiction table places Canada's regimes alongside the U.S., UK, and EU ones.

Frequently asked questions

When do Canadian federal organizations have to make documents accessible?

Under the Regulations Amending the Accessible Canada Regulations registered December 5, 2025, the federal public sector must ensure new or updated web pages conform to CAN/ASC-EN 301 549:2024 from December 5, 2027, and new or updated non-web documents and mobile applications from December 5, 2028. Federally regulated private-sector entities with 500 or more employees have the December 5, 2028 date for web pages, apps, and documents; those with 100 to 499 employees have December 5, 2028 for web pages only; smaller businesses are exempt.

What standard does CAN/ASC-EN 301 549:2024 require for PDFs?

CAN/ASC-EN 301 549:2024 is Accessibility Standards Canada's adoption of the European standard EN 301 549 V3.2.1. Its clause 10 applies WCAG 2.1 Level A and AA success criteria to non-web documents such as PDFs: text alternatives, structure and reading order, contrast, keyboard access, a document title, focus order, link purpose, document language and language of parts, form labels and errors, and name-role-value for fields.

Does the AODA require PDFs to be accessible?

Yes for organisations it covers. Since January 1, 2021, designated public sector organisations and businesses or non-profits with 50 or more employees in Ontario must make public websites and web content published after January 1, 2012 conform to WCAG 2.0 Level AA, except criteria 1.2.4 and 1.2.5. Where conformance is not practicable, the organisation must explain why the content is unconvertible and provide a summary on request, and it must work with anyone who requests an accessible format.

Sources

The statements above rest on the primary sources below. Where a source is a law or standard, the version and date named in the text are the ones checked on the review date. This guide is general information, not legal advice.

  1. Canada Gazette, Part II, Volume 159, Number 26 (December 17, 2025): Regulations Amending the Accessible Canada Regulations (SOR/2025-255) . Covered entities, the standard incorporated by reference, the staged dates, the definitions of update and feasibility, and the exemptions.
  2. Justice Laws Website: Accessible Canada Regulations (SOR/2021-241)
  3. Accessibility Standards Canada: CAN/ASC-EN 301 549:2024, Accessibility requirements for ICT products and services (PDF)
  4. Ontario.ca: How to make websites accessible . Who must comply, WCAG 2.0 AA and the two excluded criteria, the January 1, 2012 content date, and the unconvertible-content and accessible-format duties.
  5. Ontario e-Laws: O. Reg. 191/11, Integrated Accessibility Standards

Keep reading