How to design accessible colour contrast that still looks good
Meet WCAG contrast ratios without making your design look harsh: tokens, secondary text, brand colours, images and testing.

Low-contrast text is one of the most common problems on modern websites. Light grey body copy on white, thin pale labels on coloured buttons, captions placed over busy photos. It looks refined in a design file on a bright, calibrated monitor. On a phone in sunlight, or for anyone with lower vision, it simply disappears.
Many designers avoid strict contrast rules because they fear the result will look harsh. It does not have to. With a clear understanding of the guidelines and a few practical techniques, you can design colour systems that pass accessibility checks and still feel calm and considered. Here is how.
Know the numbers that matter
The Web Content Accessibility Guidelines (WCAG) define contrast as a ratio between the lighter and darker colour, from 1:1 (no contrast) to 21:1 (black on white). For level AA, which most organisations aim for:
- Normal text needs at least 4.5:1.
- Large text (roughly 24px regular or 18.5px bold and above) needs at least 3:1.
- Interface components and meaningful graphics, such as input borders, icons and focus indicators, need at least 3:1 against what is next to them.
Level AAA asks for 7:1 for normal text. It is a good target for long-form reading, but AA is the common baseline.
Build contrast into your colour tokens
The easiest way to stay accessible is to solve contrast once, at the system level, instead of checking every screen. When you define your palette, create named pairs that are known to pass:
- Pick your background colours first: page, surface and one or two accent backgrounds.
- For each background, define a primary text colour, a secondary text colour and a border colour.
- Check each pair and only keep combinations that meet the ratio for their use.
- Name tokens by role, such as text/secondary, so nobody picks a random grey later.
In Figma or Framer, store these as variables or styles. The designer who comes after you, or the client editing the site, then picks from safe options by default.
Make secondary text darker than you think
Secondary text, such as captions, meta data and helper text, is where contrast usually fails. Designers lighten it to create hierarchy. Instead, create hierarchy with size, weight and spacing, and keep the colour readable.
A mid grey that passes 4.5:1 on white still looks clearly lighter than near-black body text. Combined with a smaller size, that is enough hierarchy. If the secondary text sits on a tinted surface, check it again, because tints reduce contrast quickly.
Handle brand colours honestly
Many brand colours, especially bright greens, yellows, oranges and light blues, fail as text or button backgrounds with white text. You do not need to change the brand. You need to use the colour in the right place:
- Use the bright brand colour for large shapes, backgrounds and illustrations where text sits in a darker or lighter colour that passes.
- Create a darker shade of the brand colour for text links and buttons with white labels.
- For buttons, try dark text on the bright brand colour. It often passes where white does not.
Clients usually accept a slightly deeper shade once they see that the original looks the same at a glance and is now readable.
Show this side by side in the presentation: the original colour with white text and its failing ratio, next to the adjusted version that passes. Seeing both makes the decision about readability rather than taste, and it gives the client a clear reason to share with their own team or brand owner.
Be careful with text on images
Text over photos is hard to keep accessible because contrast changes across the image and between breakpoints. Practical fixes:
- Place text over a calm area of the photo and check it at every breakpoint, because cropping changes what sits behind it.
- Add a subtle gradient or solid overlay behind the text.
- Put the text on a solid panel next to or on top of the image.
Check the contrast against the lightest part of the image behind the text, not the average.
Do not forget states and focus
Contrast also applies to interface states. Disabled buttons are exempt from the ratio, but they should still look clearly disabled. Hover and active states need to be distinguishable. Focus indicators, the outline keyboard users rely on, need to be visible against the background, and removing the browser's default outline without replacing it is one of the most common accessibility failures.
Also avoid using colour alone to communicate meaning. An error field should have an icon or message, not just a red border.
Test in real conditions
Use a contrast checker plugin in Figma or the accessibility tools in your browser's developer tools to check ratios. Then test the real thing:
- Look at the site on your phone outdoors or near a bright window.
- Lower your screen brightness and check secondary text.
- Use a colour blindness simulator for charts and status colours.
- Navigate the page with only the keyboard and watch the focus.
Conclusion
Accessible contrast is not a style; it is a constraint, and good design has always worked within constraints. Learn the key ratios, solve contrast in your colour tokens, use size and weight for hierarchy, give brand colours the right roles and test in real conditions. The result is a site that still looks refined and can actually be read by everyone who visits it.


