Auditing Colour Contrast From an Imported Page in Figma

Run a contrast audit in Figma on an imported page: the WCAG ratios that apply, what the accessibility view checks, and what you still test by hand.

TUTORIALDESIGNERPublished

Audit the imported fills against four numbers

To audit contrast on an imported page, select each text layer, open the accessibility view in Figma's color picker, and compare the result with WCAG 2.2 level AA: 4.5:1 for text, 3:1 for large text and for icons and other graphics. The view only knows the layer you selected, so the audit is a layer-by-layer pass, not an instant report.

An imported page is a good subject for this. Text arrives as text layers with real fills, so you can measure the colours the page specified instead of sampling pixels from a screenshot. Prerequisites: a page already imported into Figma, and its import report open beside the canvas. As of November 2026, the steps below match Figma's help page for the color picker and the W3C's Understanding document for SC 1.4.3.

Read the import report before you measure

Start with the report, because it tells you which layers are not what the source page used. A font that was not installed gets substituted (Inter by default), and every swap is logged. A substituted font can have thinner or heavier strokes and a different size on screen, which matters here for two reasons.

First, the large-text threshold depends on size and weight. If a heading falls back to a different weight, a pair that passed at 3:1 as large text may now be ordinary text that needs 4.5:1. Second, WCAG notes that fonts with extraordinarily thin strokes are harder to read at lower contrast. Write down the substituted fonts and treat their layers as the first ones to recheck.

Keep in mind what you are auditing. It is the page as captured, with faithful, editable layers, not a pixel-exact clone. A passing result in Figma is evidence about the captured colours. It is not a verdict on the live site.

The thresholds worth memorising

The W3C's Understanding page for SC 1.4.3 Contrast (Minimum) sets the numbers you need:

ContentLevel AALevel AAA
Text and images of text4.5:17:1
Large-scale text3:14.5:1
Active UI components and graphical objects3:1not defined

The AAA column and the 3:1 row for components come from MDN's color contrast guide, which summarises the same criteria.

Large-scale text means at least 18pt, or 14pt bold. At 1pt = 1.333px that is about 24px and 18.5px. Contrast is the ratio (L1 + 0.05) / (L2 + 0.05) of the relative luminance of the lighter and darker colour, and it runs from 1:1 to 21:1.

Two details catch people out. First, the thresholds are not rounded: the W3C states that 4.499:1 does not meet 4.5:1. Mid-grey text shows how thin the margin is. The grey #767676 on white is 4.54:1 and passes. The grey #777777 on white is 4.48:1 and fails, although you cannot see the difference.

The exceptions are narrow. Inactive controls, pure decoration, text no one can see, and logotypes have no requirement. Brand guidelines are not an exemption: text with low contrast because of corporate identity is still held to the ratio.

Check a text layer with Figma's accessibility view

This step does most of the work. Following Figma's help page for the color picker:

  1. Select a text layer on the canvas.
  2. Click its fill swatch in the right sidebar to open the color picker.
  3. Open the accessibility view in the color modal.
  4. Read the ratio, from 1:1 to 21:1, and the AA and AAA indicators.
  5. Open the accessibility settings and set the category to Normal text or Large text if Auto picks the wrong one.

The selected layer's colour is always treated as the foreground. The categories are Auto (based on the selected layer), Large text, Normal text and Graphics, and AAA is available for text only. When a pair fails, a warning indicator appears next to AA or AAA, and clicking it moves the value to the nearest compliant colour.

Treat that correction as a suggestion. It gives you a number that passes, not a colour that fits the design. Pick the replacement yourself, then re-read the ratio.

What the view does not tell you

Figma's help page does not say how the background is chosen, and it does not describe opacity, gradients or images. So do not assume the answer on any of those. Test these cases by hand:

  • Semi-transparent text or backgrounds. Work out the blended colour on the real backdrop, then compute the ratio from that.
  • Gradients. Check the text against the lightest and darkest part of the gradient it sits on. The worst point decides.
  • Text over photos. The W3C lists background images that do not provide sufficient contrast as a failure (F83). A photo needs a measured worst case, not a glance.
  • Missing backgrounds. If a layer has a text colour but its container has no fill, WCAG assumes white. Check what actually sits behind it.

For a quick second opinion on any pair, Figma's web Color Contrast Checker takes a foreground and a background hex code and reports AA and AAA results.

States and placeholders

WCAG applies the criterion to placeholder text and to text that appears on hover or keyboard focus. Placeholder text is the usual offender: a light grey that reads as polite in a mockup and fails at 4.5:1.

An import captures the page in one state. Hover and focus styles that the source defines in CSS may not appear as separate layers, so a clean pass on the imported frame says nothing about them. Read the source stylesheet for :hover, :focus and ::placeholder colours, then build or recolour a frame for each and measure it. Placeholder text sits inside controls, so see how form controls arrive after import for what you are looking at in the file.

Pages with more than one colour scheme

A page with a dark theme has two sets of colours and needs two audits. Passing in light mode says nothing about dark mode, because the foreground and background both change. Capture each scheme separately, as covered in importing the dark-mode version of a page, and keep one list of ratios per scheme.

Icons, borders and chart marks

Text is only part of the audit. Success criterion 1.4.11 Non-text Contrast asks for 3:1 for user interface components and graphical objects. In practice that covers icons that carry meaning, the border of an input that is the only cue to where it sits, and the marks in a chart. Text characters used as symbols, such as an X for close, fall here as well, and so does a stylised logo that acts as a control.

In Figma's accessibility view, switch the category to Graphics for these layers. The 3:1 line applies; there is no AAA tier for graphics in the view.

Fix a failure once, not on every layer

When a colour fails, change it where it is defined. If the same grey appears on forty text layers, create a colour style or variable, point the layers at it, and then correct the single definition. Re-measure after the change, since a darker text colour can shift the pairing with a tinted background. For passing the file on to engineers afterwards, see design handoff for an imported page.

What to record and what to do next

A useful audit leaves a small table: layer or style name, foreground, background, measured ratio, the threshold it was held to, and pass or fail. Add a line for each case you tested by hand and how you tested it. The order that works: read the import report, learn the thresholds, check every text layer, cover states and colour schemes, then the non-text marks.

If you need the page in Figma first, UnHTML imports a page as editable layers and logs what it substituted or could not map. The contrast numbers are yours to measure, and they are only as good as the colours you captured.

Questions

What contrast ratio does body text need?
WCAG 2.2 level AA asks for at least 4.5:1 for text, and 3:1 for large-scale text (18pt, or 14pt bold, roughly 24px and 18.5px). The thresholds are not rounded, so 4.499:1 fails.
Does Figma check contrast for me?
Figma's color picker has an accessibility view that compares the selected layer, always treated as the foreground, against the AA and AAA thresholds. Its help page does not describe how it handles opacity, gradients or images, so check those by hand.
Do placeholder and hover text count?
Yes. WCAG says the criterion applies to placeholder text and to text shown on hover or keyboard focus. Disabled controls, decoration and logotypes are exempt.
Is a low-contrast brand colour acceptable for text?
No. WCAG exempts logotypes only; text with insufficient contrast because of brand guidelines is not exempted.