Minimum WCAG AA contrast for normal vs large text and Figma checks
This tests WCAG AA contrast thresholds and Figma operationalization. A strong answer states 4.5:1 for normal text and 3:1 for large text, then describes using Figma's native contrast panel or Stark to audit color pairs.
WHAT THIS TESTS: This tests two things: whether you have memorized the specific WCAG AA contrast thresholds, and whether you can translate that knowledge into an actionable design workflow in Figma. At a senior level, interviewers care less about raw memorization and more about operational rigor, meaning you do not just know the numbers but have a repeatable process for catching violations before they reach engineering.
A GOOD ANSWER COVERS: A good answer hits four things in order. First, state the exact ratios: normal text requires a minimum contrast ratio of 4.5 to 1 against its background, while large text requires 3 to 1. Second, define large text precisely: at least 18 point regular weight, or at least 14 point bold. Third, explain Figma's native capability: when you select a text layer and open the color picker or right sidebar, Figma can display contrast ratios against the underlying fill if the color styles are set up, though many teams supplement this with plugins. Fourth, name specific plugins and workflows, such as Stark or A11y, which let you select two layers and see their ratio instantly, or scan an entire frame to flag failures. Mention that you enforce this by making contrast checks a required step in design QA, not an afterthought.
COMMON WRONG ANSWERS: Common wrong answers include flipping the ratios, citing AAA requirements as AA, or stating that 4.5 to 1 applies to everything. Another red flag is saying you just eyeball it or use your monitor's brightness as a guide. Saying Figma has no tools for this is also incorrect; the built-in checker and plugin ecosystem are robust. Confusing contrast with color blindness accommodation is a subtle error that signals shallow familiarity.
LIKELY FOLLOW-UPS: Interviewers often follow up by asking how you handle contrast over images or gradients, where a single background color does not exist. They may also ask how you enforce this across a design system, prompting discussion of tokenized color pairs that are pre-validated. Another common pivot is asking for the AAA ratios, which are 7 to 1 for normal text and 4.5 to 1 for large text, or asking how you handle dark mode contrast.
ONE CONCRETE EXAMPLE: Imagine you are auditing a login screen. The headline uses 24 point semibold white text on a light gray card with a hex value of E5E5E5. You select the headline and the card background in Stark, which reports a 2.8 to 1 ratio. Because this is below the 3 to 1 threshold for large text, you darken the card to D4D4D4, which raises the ratio to 3.2 to 1, then document the new token in your design system so the error does not recur.
Read the original → w3.org
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.