Bilingual UX Is Not Translation: Lessons for Companies Entering French Canadian Markets
Here’s a pattern we see often: a company decides to expand into Canada. Someone on the team points out that Quebec requires French. The team runs the product through a translation service, adds a language toggle in the footer, and calls it done.
Six months later, Quebec conversion rates lag every other region, support tickets from Montreal read as frustrated, and a promising enterprise deal stalls when the buyer’s procurement team asks why the French contract reads like it was written by software.
Quebec represents roughly 20 percent of Canada’s B2B software market and more than eight million consumers. It’s also the part of the Canadian market where a translation-only approach fails most visibly. Bilingual UX is a design discipline with legal requirements, linguistic nuance, and trust dynamics that translation alone can’t address. Here’s what we’ve learned helping companies get it right.
The legal floor: French is required, not optional
Before we get to design, it helps to understand the regulatory baseline, because in Quebec the baseline is set by law.
The Charter of the French Language, significantly strengthened by Bill 96, requires businesses operating in Quebec to serve customers in French. That includes websites, product interfaces, contracts, invoices, and customer support. French content must be available and displayed at least as prominently as any other language. A French toggle buried in a footer, defaulting every visitor to English, does not meet the spirit or increasingly the letter of the requirement. The Office québécois de la langue française (OQLF) handles complaints and enforcement, and Bill 96 expanded its powers along with the penalties for non-compliance.
Law 25, Quebec’s modernized privacy law, layers on requirements that live directly in your interface. Consent must be requested in clear, plain language, which in Quebec means clear, plain French. Privacy settings must default to the highest level of confidentiality. If personal data leaves Quebec, a privacy impact assessment is required first. Your consent flows, cookie banners, and privacy notices are all UX surfaces, and all of them need to work in French for francophone users.
The takeaway: compliance questions in Quebec are design questions. Legal review tells you what’s required. Design determines whether you meet it in a way users actually experience as respect rather than obligation.
Lesson 1: Architecture before language
The most common structural mistake is treating French as a layer applied on top of an English product. Language should be an architectural decision made early, because it touches routing, content management, search indexing, and every template in the system.
Decide how users arrive in the right language. Geolocation with a clear, easy override is a reasonable default. Respect browser language settings. Make the language switcher visible and persistent, and once a user chooses French, remember it everywhere, including transactional emails, receipts, and notifications. A user who browses your site in French and then receives an English confirmation email has just been told that French is the second-class experience.
Search matters here too. Francophone users in Quebec search in French. If your French pages are thin, machine-generated, or hidden behind scripts that crawlers handle poorly, you’re invisible to a fifth of the Canadian market at the exact moment they’re looking for you.
Lesson 2: French takes up more room
French text runs 15 to 25 percent longer than the equivalent English. Buttons, navigation labels, table headers, and mobile layouts designed to fit English will break in French. “Save” becomes “Enregistrer.” “Settings” becomes “Paramètres.” A tab bar that fits five English labels comfortably will truncate or wrap in French.
The fix is designing for expansion from the start: flexible components, generous touch targets, layouts tested with the longer language. When teams design in English and check French at the end, the French experience inherits every compromise. When they test both from the first prototype, the layout problems surface while they’re still cheap to fix.
Typography carries subtle signals as well. French uses accented capitals (École, not Ecole), non-breaking spaces before certain punctuation, and French quotation marks (« guillemets »). Getting these details right won’t be consciously noticed by most users. Getting them wrong will be, and it reads as carelessness.
Lesson 3: Formats, forms, and microcopy
The small conventions of an interface are where localization quality becomes visible daily.
Currency formats differ: English Canadian convention writes $99.99, while French Canadian convention writes 99,99 $ with the symbol after the amount and a comma as the decimal separator. Large numbers use spaces rather than commas: 1 234 567. Dates, capitalization rules, and address labels all shift. Your forms need French labels, French validation messages, and French error states, because an error message is precisely the moment a user is already frustrated, and receiving it in the wrong language compounds the problem.
Audit every string in the product, including the ones engineering tends to forget: 404 pages, password reset emails, tooltips, loading states, and system notifications. Users judge completeness by the edges.
Lesson 4: Consent and privacy flows deserve design attention
Because Law 25 requires plain-language consent and confidentiality by default, your consent UX in Quebec has to do two jobs at once: satisfy a stricter legal standard than most US teams have encountered, and do it in French that a real person finds clear.
Pattern-matching from US cookie banners won’t work. Pre-checked boxes, buried opt-outs, and dense legalese run against both the law and Quebec buyer expectations. We recommend designing the French consent flow as a first-class artifact: plain Quebec French, honest choices, defaults set to protect the user. Companies that do this well turn a compliance requirement into a trust signal, and in a market where buyers are documented as risk-averse and evidence-driven, trust signals compound.
Lesson 5: Research with the users you're designing for
Everything above can be built and still miss, because assumptions about francophone users made from an anglophone office are still assumptions. Run usability testing in French with Quebec participants. Recruit francophone users for interviews during discovery, not just validation. Test comprehension of your actual French copy, since a technically correct translation can still confuse if the terminology doesn’t match how your users talk about their work.
This is standard user research practice applied to a market that too many companies treat as a checkbox. The companies that win in Quebec treat francophone users as a primary audience with their own research stream.
A practical starting checklist
If you’re evaluating your own product’s readiness for Quebec, start here:
- Legal surfaces: Are contracts, invoices, privacy notices, and consent flows available in professionally written French, displayed at least as prominently as English?
- Language architecture: Does language preference persist across the product, emails, and support?
- Layout resilience: Has every screen been reviewed with French text lengths?
- Quebec French: Was your copy written or reviewed by a native Quebec French speaker?
- Formats: Do currency, dates, and numbers follow French Canadian conventions?
- Law 25 flows: Do consent and privacy defaults meet Quebec’s higher bar, in French?
- Research: Have francophone users tested the French experience?
If you answered no to more than two of these, a translation vendor won’t close the gap. You have a design problem, and it’s solvable.
Where to go from here
Quebec rewards companies that invest in the experience. The buyers are loyal, the market is large, and the competition thins out considerably once French fluency becomes the price of entry. The research on Canadian buying behavior is consistent: local credibility, compliance fluency, and evidence of respect for the market outperform aggressive outreach every time.
At LunarLab, we help companies design bilingual and localized product experiences that meet Quebec’s legal requirements and, more importantly, earn the trust of the users behind them. If your team is planning a Canadian expansion or rethinking an underperforming French experience, we’d be glad to talk through what we’ve seen work. Let’s talk!
