There is a quiet pattern in how Canadian organizations approach the Accessible Canada Act. The accessibility lead and the equity team get involved early. The legal department signs off on the plan. The communications team designs the public-facing version. The IT department handles digital format conversion. And somewhere late in the process, often with a few weeks left before publication, someone asks whether the French version is ready — and discovers that what they thought was a translation task is in fact a regulated bilingual obligation with its own compliance architecture.
This pattern is not the exception. It is the rule. The Accessible Canada Act, in force since 2019, is a major piece of disability-rights legislation; its provisions on accessibility plans, progress reports and feedback mechanisms apply to every federally regulated entity in the country, from the federal government and Crown corporations to banks, telecoms, broadcasters, airlines and interprovincial transportation. What the Act does not explicitly do — and where the trap lies — is spell out the bilingual rules. Those come from the Official Languages Act, which applies in parallel and which most accessibility plans subject to the ACA must respect. The interaction between the two frameworks creates obligations that look obvious in retrospect but are routinely missed in practice, and the cost of missing them is paid in regulator scrutiny, re-publication cycles, and accessibility plans that fail the very communities they were meant to serve.
This article is for accessibility leads, communications managers and compliance officers in federally regulated organizations. It walks through what the ACA actually requires in French, why the bilingual layer is consistently underestimated, and what a compliant translation looks like when the work is done properly.
What The ACA Requires Every Federally Regulated Organization To Publish
The Act establishes a cycle of obligations centred on three deliverables. The first is an accessibility plan — a public document, refreshed at least every three years, identifying barriers to accessibility within the organization’s operations, the measures being taken to remove them, and the consultation process used to develop the plan. The second is a feedback mechanism — a clearly publicised way for the public and for employees to provide feedback on accessibility barriers and on the accessibility plan itself, with a designated person responsible for receiving that feedback. The third is a progress report, published in each of the intervening years, describing what the organization has done to act on its plan and on the feedback received.
The seven priority areas the ACA targets are familiar to anyone working in accessibility: employment, the built environment, information and communication technologies, communication other than ICT, the procurement of goods and services, the design and delivery of programs and services, and transportation. Each area is supposed to be addressed in the plan with specific, measurable commitments.
What is less familiar — and where the bilingual question enters — is that the Act requires all three deliverables to be made available in the official languages applicable to the organization, and in accessible formats on request. For most federally regulated entities, “the official languages applicable” means both English and French, by default, at publication, without waiting for a request.
Why “available in French” Is Not a Translation Task
The instinct, when this requirement surfaces in project planning, is to treat the French version as an at-the-end deliverable: finish the English plan, send it to a translator, publish both versions on the same day. This is precisely the workflow that produces compliance problems.
The technical reason is that accessibility plans contain a register of specialised terminology — barrier, accommodation, assistive technology, sensory disability, cognitive disability, plain language, universal design — and these terms have established French equivalents in the Canadian federal lexicon. Obstacle, mesure d’adaptation, technologie d’assistance, handicap sensoriel, handicap cognitif, langage clair, conception universelle. Using the wrong equivalent — or, worse, using European French terminology in a federal Canadian document — does two things at once: it signals to francophone readers that the plan was not written with them in mind, and it undermines the plan’s legibility for the very communities it claims to serve. A francophone employee with a disability reading an accessibility plan that talks about aménagements raisonnables in a context where the federal standard is mesures d’adaptation is reading a document that was clearly translated, not produced. The disability community in francophone Canada notices this. So do reviewers at Accessibility Standards Canada and at the Office of the Accessibility Commissioner.
The strategic reason runs deeper. Accessibility plans are consultation documents. They are supposed to be developed with input from people with disabilities — including francophone people with disabilities — and the consultation process is itself part of what the plan must describe. If your French version arrives after consultation has already happened in English, the document records a consultation that francophone disability communities were structurally excluded from. The Act anticipates this: meaningful consultation includes meaningful access in both official languages, and the same logic applies to feedback mechanisms. A feedback form that exists only in English, or that exists in French only as a second-class option, defeats the Act’s purpose and creates exposure on both the accessibility and the language-rights side of the regulatory ledger.
The Four French-Language Requirements That Quietly Accumulate
When you take the ACA and the Official Languages Act together, the bilingual obligation breaks into four distinct workstreams that need to be planned, not improvised.
- The accessibility plan itself, in French. Not a summary translation, not a press release in French alongside an English plan, but the full plan — with the same level of detail, the same structure, the same consultation record, the same commitments. The French version is not a derivative; it is the same document in another language, with equal legal standing.
- The feedback mechanism, in French. This includes the public-facing description of how to provide feedback, the form or channel through which feedback is received, the contact information for the designated person, and the acknowledgement messaging sent to people who submit feedback. Each of these needs to work natively in French, not as an afterthought. For federally regulated organizations with operations in Quebec, the interaction with Quebec’s Charter of the French Language and Bill 96 adds a layer: French-language access to feedback channels is also a Charter expectation for Quebec-based employees and customers, on top of the ACA’s federal requirement.
- Accessible formats on request, in French. The Act requires accessibility plans and feedback mechanisms to be available in accessible formats — large print, braille, audio, electronic formats compatible with assistive technologies — on request. The French version must be available in the same range of accessible formats. A braille version of an English plan does not satisfy a francophone request for a braille version of the French plan. This sounds obvious; it is not always handled obviously.
- Progress reports, in French. Each annual progress report carries the same bilingual obligation as the main plan. Organizations that publish their first plan in both languages but treat the annual reports as English-first often discover, by year three of the cycle, that they have built a bilingual baseline and a unilingual update stream.
Where This Intersects With Bill 96 For Organizations Operating In Quebec
Many federally regulated organizations — banks, telecoms, transportation companies — have significant Quebec operations. For these organizations, the ACA’s bilingual requirements run in parallel to Quebec’s Charter of the French Language and Bill 96 obligations, which apply to employer-employee communications, customer-facing materials and any public-facing documentation in Quebec.
The two regimes do not contradict each other, but they do reinforce each other in ways that affect how translation should be planned. An accessibility plan published in French nationally also functions as a Quebec-facing document for an organization’s Quebec workforce and Quebec customer base. The French version therefore needs to read naturally to Quebec audiences — which means Quebec French translation produced by translators familiar with both the federal accessibility lexicon and Quebec linguistic conventions, not European French or generic francophone-international French. This is the single most important quality marker for the French version of a national accessibility plan, and the one most likely to be missed when the translation is outsourced to a generalist provider.
For Quebec-headquartered federally regulated entities, the flow is reversed but the principle is the same: the English version of the plan needs to read naturally to anglophone Canadian audiences, with terminology aligned to the federal accessibility lexicon. In both directions, the work is closer to bilingual co-authoring than to one-way translation.
Common Mistakes We See In The French Versions Of Accessibility Plans
A few patterns recur in the French accessibility plans we have reviewed for clients, and each one is worth flagging because they are easy to avoid if you know to look for them.
Inconsistent disability terminology across the document — the same condition described with different terms in different sections, suggesting that different translators worked on different parts without a shared glossary. Federal accessibility terminology is stable enough that consistency is a basic expectation; inconsistency reads as carelessness.
Mistranslated job titles and organizational role descriptions — particularly for the “designated person” responsible for receiving feedback, whose title appears in multiple sections and whose role needs to be described identically across them.
Anglicism creep in the French text — flexibilité used where the federal usage prefers souplesse, accommoder where adapter is the standard, barrière (literal) where obstacle (functional) is the term the ACA uses in French. These choices look minor on the page; they signal a translator unfamiliar with the federal Canadian register.
A consultation section that records the consultation process in English-speaking terms and is then translated, rather than recording the consultation as it actually unfolded across both linguistic communities. If you only consulted English-speaking disability organizations, the French version will read as a translated record of an English-only consultation — which is itself a compliance problem worth fixing before next year’s progress report.
Feedback acknowledgement messages, system emails and form labels that work in English but not in French. These are technical artefacts that often live in a different system from the published plan, and they are often forgotten in translation scoping. They should not be.
A Practical Takeaway For Accessibility Leads
If you are responsible for an accessibility plan, three operational decisions go a long way toward avoiding the trap.
Plan the French version into the project at scoping, not at publication. The translation should be commissioned when the English draft is stable, not after final approval — and the translator should have access to the consultation record and the source materials, not just the final document.
Choose a translation partner with experience in federal Canadian terminology and in Quebec linguistic conventions, not a generalist provider. The accessibility lexicon is specialised, the federal register is specific, and a French translation agency that handles regulated content regularly will know the conventions without needing to be taught.
Treat the French version as a working document across the plan’s three-year cycle, not as a one-shot translation. Progress reports, updated feedback mechanisms and refreshed accessibility plans should all flow through the same terminology base, with translation memory leverage that keeps language consistent and costs lower over time. This is the same operational discipline that organizations apply to their bilingual HR documentation under Bill 96, and the rationale is the same: regulated content benefits from continuity, not from being commissioned fresh each year.
The Accessible Canada Act was not designed to be a translation regime. But for the federally regulated organizations it covers, the bilingual layer is real, ongoing and consequential. The organizations that internalise this early — that build the French version into the workflow as a peer document, not as a derivative — produce accessibility plans that work for the disability communities they were meant to serve, on both sides of Canada’s linguistic divide. The organizations that do not eventually discover the gap, and almost always discover it at the worst possible moment in a regulatory cycle.
If you are scoping the French version of an accessibility plan, a progress report or a feedback mechanism, send a sample of your current English material to [email protected] for a quick review of where it stands. Free and with no commitment.
