Language law
Bill 96 Compliance
French that matches the English in content, presentation and function — including the forms and checkout most sites leave in English.
Montreal, QC · Available Worldwide
I build bilingual websites that pass Quebec law — delivered in 10 days.
Bill 96 · Law 25 · Real Québécois French
Most bilingual sites fail on the parts nobody translates: forms, checkout, error messages. I build the French to the same standard as the English, because the law requires it and machine translation cannot do it.
01 — What I Build
Compliance is the job. The website is the deliverable.
Six things Quebec businesses keep needing, and most agencies quietly hand to a translation plugin.
Privacy law
Law 25 and Privacy
Consent at the point of collection, cookie handling, privacy and terms pages, and no third-party tracker firing before someone agrees.
Production web
Bilingual Web Builds
Real /fr and /en routes with hreflang and localized metadata, on one design system so the two languages never drift apart.
Real FR-CA
Québécois Localization
Written in Quebec French — not France French, and not machine output. Your customers hear the difference immediately.
Documented
Compliance Audits
A documented review of where a site actually stands, ranked by severity, with the requirement cited for every finding.
Studio design
Cinematic Web Design
Studio-grade design, delivered in days rather than months.
02 — Engagements
Four ways to work together.
Start with a free scan of the site you already have. Everything after that is fixed scope, fixed price, and a delivery date written into the contract.
01No cost, no commitment
Free Compliance Scan
Best for
Any Quebec business unsure whether its site meets Bill 96 and Law 25.
Same-day automated check
You receive
- French parity check
- Cookie and consent check
- Named findings with the exact page
Outcome You find out what is exposed before a customer or a competitor does.
Request a free scan 02Page by page
Primary diagnostic path
Full Compliance Audit
Best for
Owners who need the findings documented, prioritised, and defensible.
3–5 day manual review
You receive
- Bilingual audit report
- Findings ranked by severity, with the law cited
- Prioritised fix list
Outcome A documented position on where you stand — credited in full against a rebuild.
Request the audit 03The rebuild
Compliant Bilingual Build
Best for
Businesses whose current site cannot realistically be patched into compliance.
10 days typical, with a fixed date in the contract
You receive
- True FR/EN parity on every route, form and error state
- Law 25 privacy pages and point-of-collection consent
- Self-hosted fonts, security headers, performance pass
Outcome A site that passes Quebec law and loads faster than the one it replaced.
Plan the build 04Ongoing
Compliance Monitoring
Best for
Businesses that need to stay compliant while their content and the law both keep moving.
Monthly, cancel any time
You receive
- Quarterly re-audit
- Bilingual content updates
- Notice when the rules change
Outcome Compliance stays a solved problem instead of an annual scramble.
Discuss monitoring 03 — Where Sites Fail
The French is not the hard part. Where it stops is.
Most bilingual sites are a translated homepage sitting on top of an English application. The law looks at all of it.
FormsCheckoutError statesTransactional emailPDFs
04 — How I Build
Scan, audit, build, verify.
The same four steps every time, which is why the delivery date is known before we start.
ScanAuditCopy parityDesignBuildLegal pagesBilingual QALaunch
Scan what you already have
An automated pass over your live site: French parity, forms, checkout, consent, page speed. You get the findings whether or not you hire me.
Audit, then price it
Manual review of everything the scan flagged, ranked by severity with the law cited. What comes out is a fixed scope and a fixed date — not a range.
Build both languages together
French and English are written side by side, never translated afterward. Forms, error states and transactional email included, because that is exactly where compliance fails.
Verify before launch
Both languages checked route by route, privacy and consent pages live, security headers and performance confirmed. Then it ships.
05 — Proof
The site you are reading is the sample.
This page is bilingual, Law 25 compliant, tracker-free and audited before launch. It is the same build you would receive.
Enterprise support, retention and high-value queues — in French and English, every day.
Fonts self-hosted, nothing fires before consent. Check it yourself.
A fixed date written into the contract, not an estimate.
06 — Selected Work
What a compliant build actually contains.
Each one is framed the same way: the problem, what gets built, and what you end up holding.
01 / 03Compliant Build
Bilingual Web Infrastructure
Real /fr and /en routes on one design system, so the two languages cannot drift apart.
10 A bilingual site that holds up against Bill 96 and Law 25
System evidence
Route parityForm and error stateshreflang setupDeploy checklist
Problem
A site where the French exists on the homepage and disappears the moment someone tries to do anything.
System
Shared design system, hreflang and localized metadata, French written alongside the English rather than after it.
Output
Every route, form and error state present and equivalent in both languages.
Deliverable Set
Handover package: route map, parity checklist, deployment rules.
Metric Context
days from signed scope to launch
02 / 03Audit
Website Compliance Audit
A documented review of where a site stands, ranked by severity, with the requirement cited.
12 A written position on exactly what would fail, and what it costs to fix
System evidence
Severity rankingRequirement citedFix listFixed quote
Problem
Owners are told their site is “probably fine” by the people who built it.
System
Automated scan first, then manual review of build integrity, parity, privacy, accessibility, performance and headers.
Output
Severity-ranked findings with a prioritised fix list and a fixed price to resolve them.
Deliverable Set
Bilingual audit report, structured the same way every time.
Metric Context
review sections per audit
03 / 03Localization
Québécois Localization
Quebec French written by someone who speaks it, with parity checks at the field level.
100% French that reads as written, not as translated
System evidence
FR/EN parityField mappingQuebec FrenchReview workflow
Problem
Machine translation and France French both get caught — by customers first, and by the regulator second.
System
FR/EN field mapping, parity rules, a QA pass in both languages, and review before launch.
Output
Copy that holds its meaning and its tone across every page and component.
Deliverable Set
Handover package: field parity, component rules, review sign-off.
Metric Context
parity target across critical bilingual fields
07 — Builder Identity
Bilingual enough to write it. Technical enough to build it.
Enterprise telecom, seventeen years of customer-facing problem solving, and a builder’s approach to bilingual web.
Enterprise calm
Strategy, trust, and advisory presence
Builder energy
Hands-on build and delivery
Operator mode
System design turned into work
Cinematic technologist
The future-facing brand moment
08 — About
Built from seventeen years of serving Quebec customers in both languages.
Nearly two decades in Bell Canada’s telecom operations shaped how I build: clear systems that survive real-world pressure.
I spent those years switching between French and English all day, with real customers who noticed when the French was wrong. That is the part most web agencies cannot fake.
Nearly two decades in enterprise telecom operationsMontreal-based, serving Quebec and CanadaBill 96, Law 25, bilingual web, and Québécois localizationHands-on builder mindset from strategy to deployment
09 — Let’s Talk
Send me your site address.
I’ll run the scan and tell you exactly what would fail — whether or not you hire me.