Why Colour Contrast is Important for Digital Accessibility
Understand who colour contrast helps, what WCAG requires and how to check your colours, page elements and wider digital experience.

Good colour contrast helps people read your content, recognise controls and understand what to do next. When the text colour is too similar to its background or when a selected button or link is hard to see, a simple task can become difficult to complete. Checking contrast is a practical way to remove those barriers. It belongs in everyday design and content decisions, from choosing a brand palette to publishing pages and making updates. This guide explains the requirements and helps you choose the right check for the job.
Colour contrast is the difference in brightness between a colour and its background. A contrast ratio expresses that difference as a number. Black against white has a ratio of 21:1, while identical colours have a ratio of 1:1. For text, it’s necessary to compare the text colour with the background behind them. For controls and graphics, consider the visual information people need to identify them. A colour that works for a large heading may not work for smaller body text.
People with low vision are normally the ones who get directly affected by insufficient colour contrast. Text or controls that looks clear to one person may be faint or indistinguishable to somebody with reduced vision or contrast sensitivity. People with colour vision deficiency may also find particular colour combinations difficult to distinguish. This is especially important when a design relies on differences between colours to communicate meaning. For example, when green is used to show something positive, and red to something negative, users with low vision may find it difficult to understand what you’re communicating, especially if colour is the only way your format chosen to present this message. Contrast sensitivity can also change as people age. A colour combination that appears clear to a younger designer may be considerably harder for an older user to see. The benefits are not limited to people with permanent disabilities. Content with good colour contrast can help users:
Because people see content in different ways, colour contrast can change the user experience. A person with low vision or reduced contrast sensitivity, for example, may struggle to read text that appears clear to someone else. Better contrast can also help when a screen is affected by glare or bright sunlight. Readable instructions and recognisable controls make it easier for people to understand information and complete tasks. Differences in colour vision can create another consideration: people may not distinguish the colours used to signal success, errors or chart categories. Sufficient contrast helps, but information should also use other ways to communicate meaning, such as words, symbols or patterns.
WCAG sets different text contrast thresholds for Levels AA and AAA. However, it’s important to know that these requirements apply in both WCAG 2.1 and WCAG 2.2.
|
Text type |
AA minimum |
AAA minimum |
|
Normal text |
4.5:1 |
Faint text: Light grey text, prices and instructions can disappear against a pale background. Check smaller and supporting text as carefully as headings. Text over images or gradients: The background can change behind the text, making some areas harder to read. A sampled pair may pass while another area fails. Check the area with the lowest contrast, not just one part of the image. You may also want to add a solid background behind text. Unclear controls and states: Faint input borders, selected tabs and focus indicators can make actions hard to identify. Review each meaningful state, including hover, focus and error states. Colour used alone: A red border is not a complete error message. Add text that explains the problem. Use labels, patterns or symbols alongside colour in charts and dashboards. Placeholder text replacing labels: A placeholder that disappears during typing may be difficult to read. Use a visible form label that stays in place and is properly linked to the field.
You may be choosing colours before a page exists, examining a particular element or looking for broader issues on your homepage. Each task needs a different starting point.
Free Colour Contrast Checker: Choose a text and background colour and compare their contrast ratio against WCAG requirements. Use it when building a palette or checking a specific colour combination. Try the Free Colour Contrast Checker
Free Contrast Checker Browser Extension: Inspect individual page elements while reviewing an existing page. Use it to support a focused review of the elements you select.
Explore the Free Contrast Checker Browser Extension
Build on a free check with tools in the Nexus Inclusion platform that help your team investigate issues, prioritise improvements and review changes over time.
A great way to start is prioritising the combinations where people need to read and act:
body text
links
button labels
forms If the contrast is too low for any of the colours, try a darker text or lighter background. For light text on a dark background, try the opposite. You can often keep the character of your palette while improving its functional shades. It’s important that you keep record of approved combinations in your design system, including the text sizes and states they support. Use decorative brand colours where appropriate, but don’t rely on colour alone to show important information. Fixing a shared component can also help keep many pages consistent.
New images, campaign colours and component changes can create new contrast issues even after an initial review. That’s why you should include contrast checks in design approval and publishing, then use monitoring to catch changes later. Make sure someone reviews the findings and check that the fixes work. Inclusion develops through these everyday decisions. Clearer text, recognisable controls and understandable feedback help more people use the experience your team has created.
Find answers about contrast ratios, brand colours and choosing the right check.
WCAG AA requires at least 4.5:1 for normal text and 3:1 for large text. AAA raises those thresholds to 7:1 and 4.5:1 respectively. The appropriate result depends on the text size and use.
No. Visual information used to identify controls, their states and meaningful graphics generally needs at least 3:1 against adjacent colours at Level AA, with exceptions. Check these elements separately from their text
Often, yes. Try different shades and pairings, and define which combinations work for body text, headings and controls. A colour that fails for small text may be suitable for another use.
No. A colour-pair check only assesses the pair you enter. A page or website also needs other accessibility checks, including manual review of interactions and meaning.
People may not distinguish between colours or notice a change in colour. Add words, symbols, patterns or another visible wayto show the information so it remains understandable.
Choose a text and background colour, check the contrast ratio and take a practical step towards content that more people can read.
Understand the guidelines behind accessibility checks and how they relate to your digital content.
Get a starting view of automatically detectable accessibility issues on your homepage and plan your next steps.
Explore tools that support reviews of content, page structure and other elements of a more inclusive digital experience.