Accessible Canada Act digital content duties for federal bodies

What to take away

• Accessible Canada Act digital content duties fall on federal bodies and federally regulated entities, and they cover published pages, apps, documents and social posts.
• Each covered entity must publish an accessibility plan, set up a feedback mechanism, and report on progress.
• Accessibility Standards Canada develops the standards that sit under the Act; WCAG-aligned content practices are how most teams meet the digital parts.
• Privacy law runs alongside accessibility law, so publishing accessible content still has to respect the Privacy Act.
• A checklist and a written process keep the work auditable between reporting cycles.

Which federally regulated entities carry Accessible Canada Act content duties

The Accessible Canada Act applies to organizations under federal jurisdiction. That includes departments and agencies of the Government of Canada, Crown corporations, and the federally regulated private sector.

In practice that means banks, telecom and broadcast carriers, air, rail and marine transport, and interprovincial trucking. It also covers the federal public service itself.

If you publish content for one of these bodies, the Act reaches your web pages, PDFs, forms, video, and app screens. It is not limited to the physical premises.

The scope is why teams in Ontario, Quebec, British Columbia, Alberta, the Prairies, Atlantic Canada and the Northern Territories all end up working from the same federal baseline. Provincial accessibility laws may add requirements, but they do not replace the federal ones.

For broadcasters and telecom carriers, published content also sits inside sector rules. The rules for broadcasting and telecommunications regulation shape what carriers must publish and how they handle customer communications, which overlaps with accessibility duties on the same pages.

Consumer-facing bodies carry a second layer. Anything published to consumers has to be accurate and not misleading, and the consumer affairs guidance from the federal government sets out where those obligations sit. That matters when an accessible page also makes a claim about a price, a plan or a service.

Content leads should map their own organization against the Act before writing anything. A short scoping exercise, run through a content governance framework, tells you which pages are in scope and who signs off.

Accessibility planning duties and what a published plan must contain

Accessibility planning duties require each covered entity to prepare and publish a plan. The plan describes how the organization will identify, remove and prevent barriers.

A plan is not a statement of intent. It has to name the barriers the organization has found, set out the actions it will take, and give a timeline.

Content teams usually own a large slice of the plan, because so many barriers are content barriers. Missing alt text, scanned PDFs, colour-only status cues and unlabelled form fields all belong in the plan.

A published plan should contain, at minimum:

1. A short description of the organization and the services in scope.
2. The barriers identified, grouped by area such as web content, documents, video and social media.
3. The actions planned for each barrier, with the owner's role named.
4. A timeline, including the date the plan was published and the next review point.
5. How the organization will report progress, and where that report will appear.
6. A contact route for feedback on the plan itself.

Work through those steps before you draft a single page. The drafting is the easy part; the scoping is where plans fail.

A plan that lists barriers without owners will not survive the first progress report. Give every action a role, not a person's name, so the plan does not need rewriting when staff move.

Publishing the plan is a content task with a deadline. Treat it like any other launch: draft, review, translate where required, publish, and log the publication date. Good content planning keeps the plan, the feedback route and the first progress report on one calendar.

Bilingual publication matters here. Federal bodies publish in English and French, and Quebec's Charter of the French Language adds its own rules for commercial content in that province. An accessible plan that is only in one language is not finished.

Feedback mechanisms and progress reporting under the ACA

Every covered entity must set up a feedback mechanism. It is how people report a barrier, request an alternate format, or challenge how the organization handled an earlier request.

A feedback mechanism needs more than an email address. It needs a named route, a response commitment, and a way to accept feedback in more than one channel.

Common channels include a web form, a phone line with human support, email, and mail. Each channel has to be accessible in itself, which is where many teams trip.

An inaccessible feedback form defeats the purpose. Label every field, avoid time limits that lock people out, and offer an alternate way to reach a person.

Track every piece of feedback in one place. A spreadsheet or a ticketing queue both work, provided you can count requests, response times and outcomes at reporting time.

Progress reporting follows the feedback cycle. The organization publishes a progress report describing what it has done against the plan, and it does so on a set cycle.

The report should state what changed, what is still open, and what the organization learned from feedback. Vague reports invite complaints and undermine the plan.

Keep the reporting language direct. Readers include people who have already hit a barrier, and they are checking whether anything improved.

Accessibility feedback often arrives alongside privacy questions, because people ask what happens to the personal information they submit. Handle both in the same workflow so a request does not stall between teams.

Measure the cycle. Our guide to french content marketing in canada helps you track response times, repeat complaints and the share of requests resolved within your stated commitment.

Accessibility Standards Canada and WCAG-aligned content practices

Accessibility Standards Canada develops standards that support the Act. Its work turns broad duties into specific, testable requirements that organizations can adopt.

Standards take time to develop and come into force on their own schedule. Until a standard applies to you, the practical target for digital content is WCAG-aligned content practices.

WCAG-aligned content practices are the working method for most content teams. They cover the four broad ideas: content must be perceivable, operable, understandable and sturdy.

For a content lead, that translates into a short list of habits:

• Every image has a text alternative that carries the same meaning, or is marked decorative.
• Every video has captions, and audio-only files have transcripts.
• Headings run in order, with one top-level heading per page.
• Link text describes the destination without relying on surrounding text.
• Colour is never the only way a status or error is shown.
• Documents are published as tagged, accessible files rather than scans.
• Forms have visible labels, clear errors and no unnecessary time limits.

Run that list against your templates, not just your pages. Fixing a template fixes every future page built from it.

Structure matters as much as markup. A clear heading hierarchy helps screen reader users and search engines, and it makes translation into French cleaner.

If your organization publishes across several sites, a headless CMS for content teams can push accessible components into every template. That reduces the chance of one site drifting out of line.

Test with real assistive technology, not only automated checkers. Automated tools catch missing alt text; they do not catch confusing link text or a heading that reads out of order.

How the Privacy Act context affects federal body content publication

The Privacy Act governs how federal institutions handle personal information. It applies to the same bodies that carry accessibility duties, so the two sets of rules meet on the same pages.

The Privacy Act covers federal institutions and sets out rules for collecting, using, disclosing and retaining personal information. That includes information people submit through an accessibility feedback form.

If your feedback form collects a name, an email address or details about a disability, you are handling personal information. Say why you need it, how long you keep it, and who sees it.

A short privacy notice next to the form does most of the work. Keep it simple and link to the fuller statement rather than repeating it.

The federal privacy picture is broader than one statute. The Office of the Privacy Commissioner of Canada publishes a summary of privacy laws in Canada that sets out how the federal and provincial laws fit together.

Private-sector organizations under federal jurisdiction generally fall under PIPEDA rather than the Privacy Act, and Quebec adds its own regime. Content leads should know which law applies before writing a privacy notice. The Privacy Commissioner's page on the Privacy Act explains the federal institution side in detail.

Guidance shifts, and privacy guidance shifts faster than most. The Commissioner's Privacy Commissioner blog is a useful place to watch for changes that affect forms, tracking and published notices.

Accessibility and privacy are not in tension. An accessible form and a privacy-respecting form are usually the same form: labelled, minimal, and clear about what happens next.

For commercial content, other federal rules sit alongside these. Anti-spam law, privacy law and Quebec's language rules all touch published marketing, which is why a single Canadian content marketing compliance reference is worth keeping on hand.

An ACA digital content duties checklist for federal bodies

Use this checklist as a working document. It covers the duties described above and gives you something to attach to a review.

• Confirm whether your organization is a federal body or a federally regulated entity under the Act.
• List every content type in scope: web pages, apps, PDFs, forms and video.
• Publish an accessibility plan that names barriers, actions, owners and timelines.
• Publish the plan in English and French, and check Quebec language requirements for commercial content.
• Stand up a feedback mechanism with at least two accessible channels and a stated response commitment.
• Log every feedback item with a date, a category and an outcome.
• Publish a progress report on the set cycle, stating what changed and what is still open.
• Audit templates against WCAG-aligned content practices and fix at the template level.
• Test with assistive technology and with people who use it.
• Add a simple privacy notice to every form that collects personal information.
• Assign a named role for accessibility content, a named role for privacy, and a review date.

Two traps are worth naming. The first is treating the plan as a one-off publication rather than a living document with a review date. The second is fixing pages one at a time instead of fixing the templates that generate them.

Both traps cost more later. A plan with owners and dates, plus templates that meet WCAG-aligned practice, keeps the next reporting cycle short.

Keep the evidence. Publication dates, feedback logs, test results and translation records are what make a progress report credible and what make an audit survivable.

Common questions

Does the Accessible Canada Act apply to my organization? It applies to federal bodies and to federally regulated entities such as banks, telecom and broadcast carriers, and transport operators. Provincial accessibility laws may add requirements but do not remove the federal ones.

What has to be in a published accessibility plan? The barriers identified, the actions planned, who owns each action, a timeline, and how progress will be reported. It should be published in both official languages.

Is a feedback email address enough? No. The mechanism should offer more than one accessible channel, state a response commitment, and let people request alternate formats.

How often does progress get reported? On the cycle set for your organization under the Act. The report should state what changed, what remains open, and what feedback showed.

Do WCAG-aligned practices satisfy the Act on their own? They cover the digital content side well, but the Act also requires planning, feedback and reporting. Standards from Accessibility Standards Canada may add specific requirements as they come into force.

How does privacy law interact with accessibility feedback? Feedback forms often collect personal information, so a plain notice and a retention rule are needed. Which statute applies depends on whether your organization is a federal institution or a private-sector entity.