Colour Contrast for Designers: WCAG 2.2 Ratios, Testing and Palettes That Pass
Good colour contrast means text and interface parts stand out clearly from their background. WCAG 2.2 level AA asks for 4.5:1 for normal text, 3:1 for large text, and 3:1 for the parts of buttons, inputs and icons needed to use them.

Most brand palettes are chosen on a large, bright monitor, by someone with good eyesight, in a quiet room. Your customers read the same design on a cracked phone outdoors, with the brightness turned down to save battery, sometimes with low vision or colour blindness. Colour contrast is the bridge between what you designed and what they can actually read.
This guide gives you the exact WCAG 2.2 numbers, shows how to test them in a minute, and walks through brand palettes, dark mode, buttons and text on images. If you are building a full colour system, read it together with our guide on choosing brand colours and fonts and the wider website accessibility checklist.
Why colour contrast matters beyond compliance
Low colour contrast is not a niche problem. It affects people with low vision and colour vision deficiency, but also anyone using a phone in sunlight, an older screen, or a dim battery-saver mode. Pale grey text on white looks elegant in a mock-up and disappears on a train.
There is a business angle too. If a visitor cannot read your price, your delivery note or the label on your button, they leave. Accessibility rules are also spreading: the European Accessibility Act has applied to many consumer products and services since 28 June 2025, and it points to WCAG-based standards. If you sell to Europe, check the current official guidance for your type of business.
The good news is that colour contrast is one of the few accessibility topics that can be measured exactly with a number, so it is fixable in a single working session.
The WCAG 2.2 colour contrast ratios you need to remember
A contrast ratio compares the relative luminance of two colours on a scale from 1:1 (identical) to 21:1 (black on white). WCAG 2.2 level AA, the level most laws and clients ask for, sets these minimums:
| Element | Minimum ratio | WCAG criterion |
|---|---|---|
| Normal text and images of text | 4.5:1 | 1.4.3 |
| Large text | 3:1 | 1.4.3 |
| UI components and graphics needed to understand content | 3:1 | 1.4.11 |
| Enhanced text (level AAA) | 7:1, or 4.5:1 for large text | 1.4.6 |
Large text means at least 18 point (about 24 px) or at least 14 point bold (about 18.5 px). Anything smaller is normal text.
One detail designers often miss: the W3C states that computed ratios must not be rounded. A pair that measures 4.499:1 does not meet 4.5:1. The official explanations are on the W3C pages for Contrast (Minimum) and Non-text Contrast.
What is exempt from colour contrast rules
Not every pixel has to hit a ratio. The W3C lists these exceptions for text:
- Logotypes. Text that is part of a logo or brand name has no minimum. If the logo also works as a control, such as a home link, offer a clearer variant.
- Inactive components. Disabled buttons and fields are exempt.
- Pure decoration. Words that could be swapped without changing the purpose of the page.
- Text inside photos where it is incidental, such as a street sign in a picture.
Take care with the last one. Text placed over a photo as a headline is not incidental, so it must pass. Also remember that an exemption is a minimum legal position, not a design goal. A faint disabled button that looks like an error frustrates people, so keep disabled states readable enough to understand.
How to test colour contrast in under a minute
You do not need to calculate luminance by hand. Pick one of these routes:
- A contrast checker. Paste a foreground and background hex code into a tool such as the WebAIM contrast checker and read the ratio and pass or fail for each size.
- Browser DevTools. In Chrome or Edge, inspect an element and click its colour swatch. The picker shows the ratio and a line showing where AA is met.
- Design tool plugins. Figma has several contrast plugins that check frames in bulk, which is better than testing swatches one at a time.
- Automated audits. Lighthouse accessibility checks and similar scanners flag failing text on a live page.
Automated tools catch a lot but not everything. They cannot judge text over gradients, images or video, and they miss states you have not triggered, such as hover, focus and error. Always check those by hand. A good routine is to test every colour pair when you define the palette, then test pages again before launch. Our website launch checklist has a place for this step.
Not sure if your palette passes? Ragnar Studio's can test your brand colours and rebuild them into an accessible system. See brand identity design or ask on our contact page.
Brand palettes that pass: fixing colour contrast without losing identity
Brand colours are often mid-tones: a bright orange, a sky blue, a soft grey. Mid-tones are exactly where colour contrast fails against white. Here are real measured examples, so you can see how small changes decide the result:
| Foreground on background | Ratio | Normal text |
|---|---|---|
| #767676 grey on white | 4.54:1 | Pass |
| #777777 grey on white | 4.48:1 | Fail |
| #F26B21 orange on white | 3.04:1 | Fail (large text only) |
| #C2410C burnt orange on white | 5.18:1 | Pass |
| #F26B21 orange on #2D1B3D aubergine | 5.17:1 | Pass |
Notice the first two rows: a one-step difference in grey flips the result. This is why eyeballing is unreliable.
The fix for a brand colour that fails is rarely to drop it. Instead, build a small system:
- Keep the brand colour for large shapes, backgrounds and illustrations, where it needs no text ratio.
- Create a darker "text" version of the same hue for small text and links, like the burnt orange above.
- Pair accents with a dark neutral, as orange on deep aubergine works well.
- Record the approved pairs in your brand guidelines, so everyone uses them.
Buttons, form fields and icons: the 3:1 rule
Since WCAG 2.1, colour contrast covers interface parts, not just words. The rule, 1.4.11, says the visual information required to identify a control and its state needs at least 3:1 against adjacent colours.
Here is how that plays out on a normal website:
- Buttons. If the button label is clear text on a coloured fill, the fill itself does not need a border. The label must pass 4.5:1 against the fill. Orange fill with white text at 3.04:1 fails for normal-size labels, so use a darker fill or dark text.
- Input fields. A pale grey border on a white page is a classic failure. If the border is what shows where to type, it needs 3:1. Placeholder text is still text and needs 4.5:1.
- Icons that carry meaning. A search icon with no label needs 3:1. A decorative icon next to a label does not.
- Focus indicators. A visible focus ring should reach 3:1 against its surroundings, and keyboard users depend on it.
- Selected states. Tabs, toggles and checkboxes need a clear cue that is not only a subtle colour shift.
Check hover states too, so the control does not lose contrast when hovered. For more interface mistakes, see UI/UX design mistakes to avoid.
Do not rely on colour alone
Ratio is only half the story. WCAG 1.4.1 says colour must not be the only visual means of conveying information. Typical failures include red text for errors with no icon or message, green and red chart lines with no labels, and links in body text that differ from the surrounding text only by hue.
One W3C technique for links is a contrast of at least 3:1 between the link text and the surrounding body text. The simplest and safest answer is to keep links underlined in body copy.
For charts and status labels, add a second signal: a label, a pattern, a shape or an icon. This also helps people printing in black and white.
- Error: red border plus an icon plus the words "Enter a valid phone number".
- Success: green tick plus the text "Order placed".
- Chart: direct labels on lines instead of a colour-only legend.
Dark mode and colour contrast
Dark mode does not change the rules, but it changes where designs fail. Simply inverting a light palette often produces glaring pure white text on pure black, or muted greys that look fine and fail the test.
Measured examples on a near-black #121212 background: white gives 18.73:1, #B3B3B3 gives 8.93:1, #9E9E9E gives 6.99:1, and #6B7280 gives only 3.88:1, which fails for body text.
Practical guidance for dark themes:
- Choose an off-white text colour rather than pure white, to reduce glare, and confirm it still clears 4.5:1 easily.
- Lighten and slightly desaturate brand colours for dark surfaces. A saturated orange that works on white may vibrate on near-black.
- Re-test every pair. Borders, dividers and disabled text often fall below 3:1 once the surface changes.
- Test both themes before shipping, not just the default one.
Text on images, gradients and video
Hero banners and social creatives are where colour contrast breaks most often, because the background changes under the text. Text over an image must still pass the ratio, and tools tend to check only one point. Test the lightest and busiest area the text sits on.
Fixes that work, in order of preference:
- Put text on a solid panel or a block of brand colour next to the image.
- Add a scrim: a dark gradient or semi-transparent layer between photo and text. Check the ratio against the lightest part of the image behind the text.
- Choose or crop the photo so there is a calm area for text.
- Use real text, not text baked into the image, so it scales, translates and can be tested.
The same applies to Instagram and print work. Our notes on social media creative design and the bento grid design guide show layouts with solid text panels that pass easily.
A colour contrast workflow for your next project
Make colour contrast part of the process instead of a final rescue. A short workflow:
- Define tokens. Name your colours (text, muted text, link, border, surface, accent) and record the ratio of each approved pair.
- Set a house standard of at least AA, and consider higher for body text, since small type benefits from more than the minimum.
- Check states: default, hover, focus, active, disabled, error.
- Test on a real phone, outside, at low brightness.
- Re-test after content changes, such as new banners, because contrast is a property of pairs, not of palettes.
A note on future standards: WCAG 3 is being drafted with a different contrast method, but WCAG 2.2 is the standard you can currently meet and be measured against. Use the ratios in this guide, and check the W3C for updates. Pair this work with your typography choices, since thin fonts at small sizes can look fainter than their computed ratio suggests.
Frequently asked questions
What is a good colour contrast ratio?
For WCAG 2.2 level AA, aim for at least 4.5:1 for normal text, 3:1 for large text and 3:1 for interface components and meaningful graphics. Higher is better for small body text. Level AAA asks for 7:1 for normal text.
What counts as large text in WCAG?
Large text is at least 18 point (about 24 px) regular, or at least 14 point (about 18.5 px) bold. Large text can use the lower 3:1 ratio. Thin or unusual fonts may look fainter than their specified colour, so exceed the minimum where you can.
Does a logo need to meet colour contrast requirements?
No. WCAG exempts text that is part of a logo or brand name. The exemption does not cover other low-contrast text just because brand guidelines ask for it, and a logo that acts as a control should still be easy to see.
Do placeholder text and disabled buttons need to pass?
Placeholder text is real text, so it needs 4.5:1 against the field background. Disabled components are exempt, but making them readable enough to understand is still good practice.
Can I round a colour contrast ratio of 4.49 up to 4.5?
No. The W3C says the computed values should not be rounded, so 4.499:1 fails the 4.5:1 requirement. Darken or lighten one of the colours slightly until the ratio clears the threshold.
Which tools check colour contrast?
Use a contrast checker such as the WebAIM checker, the colour picker in Chrome or Edge DevTools, Figma plugins for design files, and Lighthouse for live pages. Always check hover, focus and error states manually and review text over images by eye.
Does dark mode have different colour contrast rules?
The WCAG ratios are the same in dark mode. The risk is that colours that pass on white can fail on dark backgrounds, or that muted greys fall under 4.5:1. Test every colour pair separately in each theme.
Can Ragnar Studio's help make my brand colours accessible?
Yes. We build brand identities and websites with tested colour pairs, and websites start from ₹5,999 / $139 for a 5-page site. Message us on WhatsApp at +91 92865 18510 or see pricing.
Colour contrast is measurable, learnable and usually fixed with small adjustments rather than a rebrand. Test every pair, keep a darker text version of each brand colour, and never depend on colour alone. If you want a palette reviewed or a site checked, Ragnar Studio's is a message away on WhatsApp or through the UI/UX design service.
Free quote
Tell us about your project
Fill this short form and send it on WhatsApp. We reply with questions or a quote. Nothing is charged on the website.
- Takes about two minutes
- Goes straight to Ragnar Studio's on WhatsApp
- Prefer email? Write to info@ragnarstudio.com
Services that help with this.
Brand identity design
Colour systems with tested, accessible pairs.
Explore →UI/UX design
Interfaces with clear states and readable type.
Explore →Website design and development
Accessible, fast websites for business.
Explore →Social media creatives
Posts with readable text over images.
Explore →More from the blog
Ready to start your project?
Tell us what you need. We reply on WhatsApp with questions, next steps and a quote.