011 min
Why low Contrast goes unnoticed
A designer picks light grey for secondary labels because it looks calm on their own monitor. A support agent opens the same screen on a laptop near a window and cannot make out the labels at all. Nobody changed the design. The viewing conditions changed, and the difference between the grey and its background was too small to survive them.
Contrast failures often go unreported for this reason. The designer sees a clean page. The reader sees a blank space where a label should be. Because the reader rarely complains, the failure goes unreported and stays in the product.
Contrast is the property that prevents this. When it is high enough, a label stays readable on a dim screen, in bright light, for a tired reader, and for a reader with low vision. When it is too low, the same label disappears for some people while staying fine for the person who made it.
022 min
How Contrast is measured
Contrast starts with a physical quantity called luminance, which is how much light a surface sends to the eye. Human vision responds more to relative differences than to absolute luminance. A grey label is therefore not dark or light on its own. It is dark or light compared with what is behind it.
WCAG 2.2, the W3C standard for web accessibility, turns this into a number in two steps. First it computes the relative luminance of each colour. For screens, WCAG 2.2 defines the relative luminance of a colour in the sRGB colour space as L = 0.2126 R + 0.7152 G + 0.0722 * B. Here R, G and B are the red, green and blue values, rescaled to a linear 0-to-1 range. The weights differ because the eye responds most to green light and least to blue.
Second, it compares the two luminances. The contrast ratio is (L1 + 0.05) / (L2 + 0.05), where L1 is the relative luminance of the lighter colour and L2 is the relative luminance of the darker colour. The 0.05 term stops the ratio from becoming huge when one colour is near black. Ratios run from 1:1 for two identical colours to 21:1 for black on white.
contrast ratio = (L1 + 0.05) / (L2 + 0.05)
A worked number
Take mid-grey text on a white background. Calculated with the WCAG formula, text in #767676 on white gives 4.54:1. Text in #777777, one step lighter in each channel, gives 4.48:1. The two greys look the same to most people, but the first passes the 4.5:1 threshold for regular text and the second fails. WCAG does not round: a pair that computes to 4.499:1 fails the 4.5:1 threshold.
Why hue is not enough
Contrast of luminance is different from contrast of colour. Pure red (#ff0000) on white gives 3.998:1, which fails for regular text. Pure blue (#0000ff) on white gives 8.59:1, which passes the stricter 7:1 level. The two colours look equally vivid, but they differ greatly in luminance. A pair of colours that differ only in hue, such as a red and a green of similar luminance, has a ratio near 1:1 and is hard to separate for many readers with colour vision deficiency.
032 min
Contrast ratios WCAG requires
WCAG 2.2 sets different minimum ratios for different jobs. The table lists the ones designers use most.
| Success criterion | Level | What it covers | Minimum ratio |
|---|---|---|---|
| 1.4.3 Contrast (Minimum) | AA | Regular text and images of text | 4.5:1 |
| 1.4.3 Contrast (Minimum) | AA | Large text | 3:1 |
| 1.4.6 Contrast (Enhanced) | AAA | Regular text | 7:1 |
| 1.4.6 Contrast (Enhanced) | AAA | Large text | 4.5:1 |
| 1.4.11 Non-text Contrast | AA | Controls, their states, and graphics needed to understand content | 3:1 |
Level AA is the usual legal and procurement target. Level AAA is a stricter option that most products meet only for some content. Large text is 18 point, or 14 point if bold. Large letters are easier to see, so they need a lower ratio.
Criterion 1.4.3 asks for at least 4.5:1 for regular text and at least 3:1 for large text. Criterion 1.4.6 raises the figures to 7:1 and 4.5:1. Criterion 1.4.11 applies a 3:1 minimum to the visual information needed to identify a control and its states, such as the border of a text field, and to parts of graphics needed to understand them.
Some things have no requirement. Inactive controls are exempt, as is text that is pure decoration and text that is part of a logo or brand name.
041 min
Contrast beyond colour
Luminance ratio is the part of contrast that can be measured with a formula. Designers also use contrast in a wider sense: any difference that makes one element separate from another. A page can create it with several properties at once.
| Property that differs | Example | What it does |
|---|---|---|
| Luminance | Dark text on a light surface | Makes text readable |
| Size | A 32 px heading over 16 px body text | Shows what to read first |
| Weight | A bold label next to regular values | Separates labels from content |
| Shape | A rounded button among square cards | Marks something as interactive |
| Space | A wide margin around one block | Isolates it from its neighbours |
| Hue | One accent colour on a neutral page | Draws the eye to one place |
These differences work together to build a visual hierarchy, the order in which a reader notices things. The logic is the same as in the Von Restorff effect: the item that differs from its neighbours stands out.
The reverse also holds. If every element has high contrast against its neighbours, none of them stands out. A screen with five bold red buttons gives the reader no signal about which one to press.
052 min
Where the Contrast numbers come from
Contrast as a design principle has no single originator. It is practitioner convention, built on older vision science, and designers used it long before any standard put a number on it. The measurable part is more recent and has a clear source: the WCAG success criteria.
The W3C chose its thresholds from research on contrast sensitivity, the ability to see small differences in lightness. The 3:1 figure comes from an American national standard (ANSI) for the minimum acceptable contrast for observers with normal vision. The Understanding document for criterion 1.4.3 then applies a correction for reduced vision. The 4.5:1 ratio is used in that criterion to account for the loss in contrast that results from moderately low visual acuity, congenital or acquired color deficiencies, or the loss of contrast sensitivity that typically accompanies aging.
The same document links each level to a vision profile. Level AA corresponds to roughly 20/40 vision, which it describes as the typical visual acuity of people at about age 80. The contrast ratio of 7:1 was chosen for level AAA because it compensated for the loss in contrast sensitivity usually experienced by users with vision loss equivalent to approximately 20/80 vision.
So the numbers are not arbitrary. They are a model of a reader with reduced vision, applied to colour pairs. That model is also the source of the standard's limits, which a later section covers.
062 min
How Contrast shows up in real interfaces
An interface that applies it: GOV.UK
The GOV.UK Design System shows contrast applied to a hard case, the keyboard focus indicator. The focus indicator is the highlight that shows which control is active when someone navigates without a mouse. A single colour would fail on some backgrounds, because a light highlight vanishes on a light page and a dark one vanishes on a dark page.
The system solves this with two colours. Links get a yellow background with a black bottom border when focused, and form inputs get a yellow outline with a thick black border. The design system says the yellow has high contrast with dark backgrounds and the thick black border has high contrast against light backgrounds. The pair meets WCAG 2.2 success criterion 1.4.11 on any background colour used on GOV.UK.
An interface that violates it: the average home page
The best-documented failure is not one product but the web as a whole. WebAIM, a web accessibility organisation at Utah State University, scans the home pages of the top one million websites each year. In its 2026 report, low contrast text, below the WCAG 2 AA thresholds, was found on 83.9% of home pages, an increase from 79.1% in 2025. It was the most commonly detected accessibility issue in the sample.
Low contrast is common because it is easy to produce. Brand palettes include pale tints, designers use light grey for secondary text, and placeholder and caption styles inherit a colour chosen for another purpose. None of these choices looks wrong on the designer's screen.
What the two cases show
The GOV.UK case treats contrast as a requirement that every background must satisfy, and tests the design against it. The home pages in the WebAIM sample treat it as a matter of taste, and the result is a failure rate above four in five.
072 min
Applying Contrast
Five moves cover most of what a team can do in a week.
Measure every text and control colour pair against its real background.
Use any WCAG contrast checker on the final colour values, not on the brand palette in isolation. A pair that passes on white can fail on a tinted card.
Test every state, not only the default.
Hover, focus, selected and error states each need their own check. A control whose border is 3:1 at rest and 1.5:1 when focused has gone backwards.
Keep every text level above the minimum.
Primary, secondary and tertiary text are usually separated by lightness. Set the lightest step at 4.5:1 or higher, then separate the levels with size and weight, as in information hierarchy, instead of by fading the colour further.
Pair colour with a second signal.
Show an error with an icon and a message as well as red, so the meaning survives a low-contrast or colour-blind view.
Measure text over images and gradients at the worst point.
Gradients can reduce the apparent contrast between areas, and make it more difficult to test. Check the lightest part of the background behind the text, or put the text on a solid panel.
Stop when the page loses its order. If every label, caption and hint is raised to the maximum, the page has high contrast everywhere and no emphasis anywhere. Use the minimum for supporting text and spend the extra contrast on the element that matters most.
081 min
Contrast and accessibility
Contrast is one of the few design properties with numeric pass-or-fail criteria in the accessibility standard. Three success criteria matter: 1.4.3 Contrast (Minimum), 1.4.6 Contrast (Enhanced) and 1.4.11 Non-text Contrast. The table in the section on thresholds lists their ratios.
The people affected are broader than the group usually called visually impaired. Some people cannot see elements with low contrast. That includes readers with low vision, readers with colour deficiencies, older readers whose contrast sensitivity has declined, and anyone using a phone in direct sun or a screen turned down to save battery.
Non-text contrast is the criterion teams miss most often. Low-contrast controls are more difficult to perceive, and a reader may miss them completely. A text field with a pale grey border on a white page is invisible to some people even when its label passes at 4.5:1. The border needs 3:1 against the page, because it is the visual information that identifies the control. The wider topic is covered under accessibility.
091 min
How to spot Contrast going wrong
Contrast fails in four ways, and each has a recognisable tell.
- Passing ratio, poor reading. The pair meets 4.5:1, but the font is thin or small. Tell: users zoom in on that text, or ask support what a label says.
- Contrast used everywhere. Every element is at maximum strength, so none stands out. Tell: eye-tracking or click maps show attention spread evenly across the page.
- A weak control at rest. Buttons and fields blend into the page until hovered. Tell: users scroll past a form without noticing the fields, and session recordings show hovering to find what is clickable.
- Unstable backgrounds. Text sits on a photo, a gradient or a video, so the ratio changes from point to point. Tell: the text reads in the design file and fails in production with a different image.
Meeting the minimum is a necessary check for legibility, not a sufficient one. Contrast does not replace type size, line spacing or line length, which the readability of a text depends on as well.
102 min
Where the Contrast ratio is contested
The WCAG 2 ratio is the standard, and it is also contested. The strongest critic is Andrew Somers, a W3C invited expert and the research lead for APCA, the Accessible Perceptual Contrast Algorithm. APCA is a proposed replacement that calculates contrast from perceived lightness difference and also takes font size and weight into account.
Somers makes two objections. The first is that one threshold cannot serve every case. In his words, no single figure such as 4.5:1 or 3:1 can be used as a blanket target for contrast between two colors, without considering the use case, size, thickness, etc. A thin 12 px label and a heavy 24 px heading differ in how much contrast they need, but the WCAG 2 ratio treats them alike except for the large-text cut-off.
The second objection concerns dark colours. Somers writes that WCAG 2.x far overstates contrast for dark colors to the point that 4.5:1 can be functionally unreadable when a color is near black. If he is right, a dark-mode palette can pass the check and still be hard to read.
The opposing position is practical. WCAG 2.2 is the version that law and procurement rules refer to, and its ratio is simple to calculate, test and audit. APCA is a proposal and does not replace it in the standard.
Where does this leave a practitioner? Treat the WCAG 2.2 ratio as a minimum that must be met, since that is what an audit checks. Then look at the design on real screens, in dark mode and in daylight, and raise the contrast of any thin or small text that passes on paper but strains the eye. An APCA value can serve as a second opinion, not as a replacement for the audit.
111 min
Contrast vs. nearby concepts
Contrast is often mixed up with the ideas that depend on it. The axis that separates them is what each one describes: contrast is a difference between two things, and the neighbours are outcomes it helps produce.
| Concept | What it describes | Relationship to contrast |
|---|---|---|
| This pageContrast | ||
| DesignFigure-ground | ||
| DesignVisual hierarchy | ||
| Not in the library yetReadability | ||
| Not in the library yetBrightness |
The most common mistake is to treat a passing contrast ratio as a finished design. It answers one question, whether two colours differ enough in luminance. It does not say whether the page has a clear order or whether the text is comfortable to read.
122 min
Contrast questions
What is contrast in UI design? Contrast in UI design is the difference between an element and what surrounds it, mainly in luminance, but also in size, weight, shape and space. It decides whether text can be read and whether controls are found.
What contrast ratio do I need for text? Regular text needs at least 4.5:1 to meet WCAG 2.2 level AA, and large text needs at least 3:1. Level AAA raises these to 7:1 and 4.5:1. Large means 18 point, or 14 point if bold.
What contrast do buttons and icons need? The visual information that identifies a control, such as its border, and the parts of an icon needed to understand it need at least 3:1 against adjacent colours. This is WCAG 2.2 success criterion 1.4.11.
Does a disabled button need to meet the ratio? No. WCAG 2.2 exempts inactive user interface components from the text and non-text requirements. Many teams still keep the label readable, so a user can tell what the control is.
Is black on white the best choice? Black on white gives the maximum ratio of 21:1, so it passes every WCAG 2.2 level. It is not the only good choice. A dark grey on white passes comfortably, and the APCA critics argue that very dark pairs need separate checks.
How do I check contrast? Enter the foreground and background values into any WCAG contrast checker and compare the ratio with the threshold for the element. Check each state, and test text on images at the lightest point behind the text.
?6 questions
Questions people ask
What is contrast in UI design?
What contrast ratio do I need for text?
Is black on white the best choice?
How do I check contrast?
▶3 videos
Watch
Understanding Contrast
What is exposure,contrast,highlight,shadow,saturation,vibrance? Basic color grading | part 1 theory
Framebyte
[BL Drama] Contrast 2026 Part 1 Explained in Hindi | Japanese BL Series
Series With Deep
§7 sources
Sources
Show all 7 sourcesHide sources
W3C, "Web Content Accessibility Guidelines (WCAG) 2.2", 2023: (definitions of contrast ratio and relative luminance, success criteria 1.4.3, 1.4.6 and 1.4.11)
W3C WAI, "Understanding Success Criterion 1.4.3: Contrast (Minimum)", WCAG 2.2:
W3C WAI, "Understanding Success Criterion 1.4.11: Non-text Contrast", WCAG 2.2:
GOV.UK Design System, "Focus states":
WebAIM, "The WebAIM Million", 2026 report:
Andrew Somers, "Why APCA as a New Contrast Method?", Myndex:
"Contrast (vision)", Wikipedia, background on luminance contrast: (vision)





