Lorixen.
EN

Brand colors that fail contrast: fixing without a rebrand

Short answer: If your brand colors fail contrast checks, you rarely need a new brand. Keep the colors for what they do well (backgrounds, large headings, accents and logos) and use darker or lighter shades of them for body text, links and buttons. The common targets are a contrast ratio of at least 4.5:1 for normal text, 3:1 for large text and for interface parts such as button borders and icons. Chrome DevTools can find failing text and suggest a passing color.

Many brands are built around a light, cheerful color (a sunny yellow, a mint green, a soft coral) that looks great on a logo and poor as white text on a button. Below are the usual symptoms, why they happen and how to fix each without abandoning the brand.

The numbers to work with

MDN's accessibility guide on color contrast summarizes the WCAG recommendations:

  • Body text: minimum ratio 4.5:1 (AA), enhanced 7:1 (AAA)
  • Large text (MDN describes this as 120–150% larger than body text): 3:1 (AA), 4.5:1 (AAA)
  • Active user interface components and graphical objects such as icons and graphs: 3:1

MDN notes these ratios don't apply to "incidental" text such as inactive controls, logotypes or purely decorative text, and that good contrast benefits all users, particularly people with certain types of color blindness and other conditions that make low contrast hard to see.

How to find the problems

Chrome DevTools has built-in tools: the CSS Overview panel, the Issues tab or a Lighthouse report can list low-contrast text, and when you inspect an element, the color picker shows the contrast ratio and whether it meets AA or AAA, with a "Use suggested color" button that applies a passing shade. DevTools can also emulate vision deficiencies so you can see roughly how your pages look to people with different kinds of color vision.

Check the homepage, a service or product page, your forms and your footer. Footers and form placeholders are frequent offenders.

Symptom → cause → fix

White text on your brand color buttons is hard to read

Cause: the brand color is too light for white text (common with yellows, light greens, oranges and light blues).

Fix options:

  • Use a darker shade of the brand color for buttons. Many brand palettes can be extended with a "dark" variant that keeps the same hue.
  • Switch the button text to a very dark color instead of white. Dark text on a yellow button often passes easily.
  • Keep the light brand color for large decorative areas, where contrast rules for body text don't apply.

Body text is mid-grey on white

Cause: a design trend for "soft" grey text.

Fix: darken the grey until it reaches at least 4.5:1. The change is often barely noticeable visually but makes a real difference to readability, especially on phones outdoors.

Links blend into the surrounding text

Cause: the link color is a light brand color, and links aren't underlined.

Fix: use a darker shade for links in body text and keep the underline (or another non-color cue), so links don't rely on color alone.

Text over photos is unreadable in places

Cause: headline text on a hero image where parts of the photo are light.

Fix: add a dark overlay or gradient behind the text, place text on a solid panel, or choose images with calm areas where text sits. Check the worst part of the image, not the average.

Placeholder text in forms is too faint

Cause: default or styled placeholder text in light grey, sometimes used instead of labels.

Fix: use real, visible labels above fields, and keep placeholder text for examples only, with readable contrast.

Buttons and form fields have barely visible borders

Cause: pale grey borders on white backgrounds.

Fix: the 3:1 guideline for interface components applies to the visual edges people need to identify controls. Darken borders, or use a filled background for inputs and buttons.

Error messages are red text only

Cause: a light red that fails contrast, and color as the only signal.

Fix: use a darker red, add an icon and a clear message, so the error is understood without relying on color.

Disabled buttons look identical to active ones (or vanish)

Cause: disabled states styled inconsistently.

Fix: inactive controls are exempt from the ratio, but they should still look clearly different from active ones, and active ones must meet the guideline.

Turning this into a palette

Rather than fixing colors one by one, update your design tokens or theme settings:

  1. Primary brand color: keep for logo, large headings, backgrounds and illustrations.
  2. Primary dark: a darker shade for buttons, links and small text on white.
  3. Primary light: a pale tint for subtle backgrounds behind dark text.
  4. Text colors: one for body text that passes comfortably, one for secondary text that still passes.
  5. Feedback colors: success, warning and error shades that pass with their text.

Write down which color is allowed for which use, so new pages don't drift back.

Checking regularly

Run a Lighthouse or DevTools check after redesigns, new landing pages or theme updates. Contrast often breaks quietly when someone adds a new banner or a seasonal color scheme.

FAQ

What contrast ratio does my website need?

The commonly used guideline is at least 4.5:1 for normal body text, 3:1 for large text and 3:1 for interface components and icons, with higher ratios for enhanced (AAA) contrast.

Do logos have to meet contrast ratios?

MDN notes the ratios don't apply to logotypes. It's still sensible to make sure your logo is visible on the backgrounds you use.

Can I keep my light brand color at all?

Yes. Use it for large areas, decorative elements and headings large enough to pass, and introduce a darker shade for text and buttons.

Will darker colors make my site look dull?

Not necessarily. Careful shades of the same hue usually keep the brand feel, and readability tends to make a site feel more polished.

Love your brand colors but keep getting contrast warnings? Send us your palette and we'll suggest accessible shades that still feel like you.

Sources

WhatsAppLet’s talk