Canada version. Written for Canadian design hiring: Ontario AODA web accessibility rules, bilingual English and French interfaces with room for longer French text, and federal Canada.ca patterns. US version
UX/UI Designer Interview Prep (Canada)
Prepare for UX and UI design interviews in Canada: AODA web rules in Ontario, bilingual English and French interfaces, text expansion and portfolio reviews.
The interactive tool loads here when JavaScript runs.
About this toolWhat is UI/UX Designer Interview Prep?
Two topics set Canadian design interviews apart from American ones: accessibility law that applies to private companies, and interfaces that have to work in both English and French. Panels in Toronto, Ottawa and Montreal ask about both, and a portfolio that shows a French version of a screen, or an accessibility fix that changed the layout, answers questions before they are asked.
In Ontario, the Accessibility for Ontarians with Disabilities Act (AODA) requires public websites to meet WCAG 2.0 Level AA if the organization is a designated public sector body or a business or non-profit with 50 or more employees. The compliance date was January 1, 2021, and two criteria are excepted: live captions (1.2.4) and pre-recorded audio descriptions (1.2.5). The Canada.ca design system says all public-facing Government of Canada content is available in both official languages, and it makes the language toggle mandatory on every page.
Use the tabs as normal: rehearse the frameworks, tick the skills your portfolio proves, run a timed challenge and test each case study against the review questions. This version adds the Canadian rules and a quick way to budget space for French labels.
- Four design process frameworks
- 32 core design skills with progress tracking
- Four design challenges with a 40 to 60 minute phased plan
- Portfolio case study structure and 24 review questions
- Inputs and progress saved in your browser
Updated
How to use UI/UX Designer Interview Prep
- Open each framework on the Design Frameworks tab with View Process.
- Tick the skills on the Core Skills tab that you can show in your portfolio; the header percentage tracks coverage.
- On Design Challenges, choose a prompt in Select Design Challenge and enter extra constraints in Additional Requirements, such as "first-time users, one-handed use".
- Click Generate Design Approach, set a timer for the total shown, and work through each phase on paper or in your design tool.
- Rehearse your case studies against the questions on the Portfolio Questions tab.
Worked examples
Space for French button labels
Input
"Search" (6 characters) and "Submit application" (18 characters)
Output
"Search": budget 12 to 18 characters, "Rechercher" is 10. "Submit application": budget about 32 to 36 characters, "Soumettre la demande" is 20.
The budgets come from the IBM expansion ranges (200 to 300% up to 10 characters, 180 to 200% for 11 to 20). Real translations often come in under the budget, but a layout that survives the budget will not truncate when a translator picks a longer phrase.
Contrast check on a dark navy header
Input
White text on #26374A, and on a teal #008080
Output
#26374A: 12.15:1; #008080: 4.77:1 (both pass AA for normal text)
WCAG AA, in both 2.0 and 2.2, needs 4.5:1 for normal-size text. The teal passes with little margin, so a lighter tint for a hover state would likely fail; check every state, not only the default.
A 45-minute bilingual design task
Input
Select Design Challenge: User Onboarding Flow. Additional Requirements: "English and French from the first screen; users in Quebec and Ontario"
Output
The five timed phases from the tool, with the requirements carried into the plan
Use the clarifying phase to settle where the language choice lives and whether it persists. Then design the core flow in French first; if it fits in French, it fits in English.
Background and insight
French copy is usually longer than English, and short strings grow the most. A W3C internationalization article reproduces IBM guidance for translation from English into European languages: strings of up to 10 characters can grow to 200 to 300% of their English length, strings of 11 to 20 characters to 180 to 200%, and text over 70 characters to about 130%. Buttons, tabs and table headers are the short strings, so they are where English-first layouts break.
The AODA standard is pinned to WCAG 2.0 AA, while the current W3C Recommendation is WCAG 2.2. Designing to 2.2 AA covers the Ontario rule and adds criteria that matter on phones, such as a 24 by 24 CSS pixel minimum target size. Saying that in an interview shows you know both the law and the current guidance.
Common use cases
Rehearsing whiteboard challenges
Run each of the four prompts against the timed plan until you consistently reach a finished core flow.
Preparing a portfolio presentation
Restructure each case study into context, process, decisions and results, and test it against the 24 questions.
Spotting skill gaps
Unticked skills in the Core Skills list show which areas your portfolio does not yet demonstrate.
Running design interviews
Use the challenges and portfolio questions as a consistent set for every candidate.
Tips and limitations
- Add one French screen to your portfolio, even a mock-up, and show how the layout coped with longer labels.
- Know the AODA thresholds: designated public sector organizations, and businesses or non-profits with 50 or more employees.
- Avoid icons or flags as the only language switch; the Canada.ca pattern uses the words "Français" and "English" (FR and EN on small screens).
- Format dates for Canadian readers: "November 6, 2026" in prose, and YYYY-MM-DD where a numeric date is unavoidable, since 06/11/2026 is read both ways in Canada.
- Check contrast for hover, focus and disabled states as well as the default.
Sources and further reading
- How to make websites accessible, Government of Ontario. Who must comply with the AODA web rule, WCAG 2.0 AA and its two exceptions.
- Language toggle, Canada.ca design system (Government of Canada). The mandatory English and French toggle and its labels.
- Text size in translation, W3C Internationalization. IBM expansion ranges by string length.
- Web Content Accessibility Guidelines (WCAG) 2.2, W3C
Frequently asked questions
Which websites have to be accessible under the AODA?
Public websites of designated public sector organizations, and of businesses and non-profits with 50 or more employees in Ontario. They must meet WCAG 2.0 Level AA, apart from live captions and pre-recorded audio descriptions, and the requirement applied from January 1, 2021 to sites and content published from 2012 onward.
Should I quote WCAG 2.0 or 2.2 in a Canadian design interview?
Both, in context. The Ontario rule names WCAG 2.0 AA, but WCAG 2.2 is the current W3C Recommendation and includes everything in 2.0 AA plus newer criteria such as target size and focus not obscured. Saying you design to 2.2 AA so you also meet the AODA is a clear answer.
How much longer is French text than English?
It depends on the length of the string. IBM guidance reproduced by the W3C gives 200 to 300% for English strings up to 10 characters, 180 to 200% for 11 to 20, and about 130% above 70 characters. Short labels are the risk, so test buttons, tabs and table headers in French.
Do Government of Canada sites need a language toggle?
Yes. The Canada.ca design system says the language toggle is mandatory on all pages, sits in the top-right corner and links to the same page in the other official language. It is for English and French only; links to other languages go in the page content.
What do Canadian design panels ask about bilingual products?
Expect questions on where the language choice is stored, how you handled longer French strings, who reviewed the translation, and whether content and design were tested with French-speaking users. Have one concrete example, even a small one.
How many case studies should a UX portfolio presentation include?
Two or three in depth for a 45 to 60 minute slot. In Canada, one that shows accessibility or bilingual work is worth including if you have it.
Is there an in-depth guide to UI/UX Designer Interview Prep?
Yes. “Engineering Manager, ML Engineer and Designer Interviews Explained” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.