A bilingual public portal should be designed, not just translated.
Citizen-facing portals need to stay readable, accessible, coherent in both languages, and maintainable by internal teams.
Useful artifacts
Examples of deliverables that can support a scoping, prototype, or pilot mandate.
Process map
Procurement controls
Public review
French-first
Structure, labels, error messages, and user journeys should feel natural in French before being adapted to English.
Accessibility built in
Contrast, keyboard use, headings, fields, errors, visible focus, and semantics should be handled from the design stage.
Maintainable content
Both languages need organization that prevents meaning drift, forgotten pages, and inconsistent messages.
Useful proof
Content inventory, FR/EN matrix, WCAG checklist, keyboard tests, and acceptance criteria.
Frequently asked questions
Is a bilingual portal just a translation?
No. It also requires structure, labels, forms, emails, and error states that work in both languages.
Why does accessibility matter for SEO?
Clear structure, coherent headings, and readable content help both users and search engines understand the page.
Can an existing portal be modernized?
Yes. A content, accessibility, and journey audit can identify priority improvements before rebuilding.
Ready to scope a first mandate?
A short conversation is often enough to identify the right format: scoping note, prototype, pilot, or implementation mandate.