Pantone test charts. You use them to check the colors of printed papers / paintwork et cetera.

What to Do When Your Brand Colors Fail Web Accessibility

A vivid brand color can be unreadable as text on white. What the contrast thresholds require, and five fixes that leave the brand intact.

Share this with the world

Web accessibility guidelines set a minimum contrast ratio between text and its background: 4.5 to 1 for normal text, 3 to 1 for large text. Many brand colors do not meet it, and it is the most common accessibility failure on the web — the February 2026 WebAIM Million study found low-contrast text on 83.9% of the million home pages it tested, up from 79.1% a year earlier, averaging 34 instances per page.

Here is how it usually surfaces. A business approves a logo, loves the color, and six months later the website goes live with that color used for headlines, links, and button labels. Then an accessibility scan runs, or a customer mentions the text is hard to read, and a palette that looked confident in a PDF becomes a list of errors. Nobody designed badly. The color was never tested against the one requirement that applies to screens and not to print.

What the contrast rule actually says

The standard is WCAG 2 — the Web Content Accessibility Guidelines — at Level AA, the level nearly every law, policy, and procurement document points to. Three numbers cover almost everything:

  • 4.5:1 for normal body text against its background.
  • 3:1 for large text, defined as 18 point and up, or 14 point and up when bold. On a screen that works out to roughly 24px, or about 18.5px bold.
  • 3:1 for meaningful non-text things: button borders, form field outlines, icons that carry information, the colored segments of a chart.

A ratio compares two colors; it is not a property of one. Your brand color is never “inaccessible” by itself — it passes or fails against a specific background, which is why the fix is usually a pairing change rather than a new palette.

Why so many brand palettes fail

Brand colors are chosen to be vivid and distinctive. Contrast math rewards something else: darkness or lightness relative to what sits behind it. Saturated mid-tones — the oranges, golds, teals, and limes that make a logo feel alive — land in the dead zone, too light for white backgrounds and too dark for black ones.

Run the numbers against white:

  • A bright brand orange (#FF6600) scores 2.94:1. It fails body text and it fails large text too.
  • A brand gold (#FFC72C) scores 1.56:1 — effectively invisible as text.
  • A teal (#00A3AD) scores 3.07:1. That passes for large headlines and for button borders, and fails for paragraphs.

Flip the background and the same orange hits 7.15:1 on black. The color did not change. The pairing did.

Gray text is the other repeat offender, and rarely a brand decision at all — it is a designer reaching for “softer.” The lightest neutral gray that still clears 4.5:1 on white is about #767676, at 4.54:1. Anything lighter fails, and lighter is everywhere.

Does my logo have to pass a contrast check?

No. WCAG carves out an explicit exception for logotypes: text that is part of a logo or brand name has no minimum contrast requirement. Your wordmark is safe as drawn, and you do not need to redraw it to satisfy a scanner.

The exception is narrow, and two things get read into it that are not there. Brand guidelines are not a defense: text that falls short because a style guide specifies a certain color is not exempt. The carve-out covers the logo itself, not everything wearing the logo’s colors. And when the logo is also a control — the clickable mark in your header — it behaves like a user interface component, which brings the 3:1 non-text requirement into play.

Five fixes that do not require a rebrand

In almost every case I have worked through, the brand survives intact and the website gets a more honest set of rules.

  1. Add a darkened web variant of the same hue. That failing #FF6600 orange, pushed to #C25400, scores 4.6:1 on white and still reads unmistakably as the brand orange. One extra swatch labeled “text and links” solves most of the problem.
  2. Use the brand color as a background, not as type. A saturated mid-tone usually passes beautifully with white or near-black text sitting on top of it. Filled buttons, section bands, and callout panels are where these colors earn their keep.
  3. Promote the color to display sizes only. If it clears 3:1 but not 4.5:1, it is legitimately available for headlines at 24px and up. Write the threshold down rather than leaving it to taste.
  4. Stop using brand colors for links in body copy. Underlines carry the signal perfectly well, and a near-black underlined link is both compliant and calmer.
  5. Define a text neutral separately. Most palettes designate no body-text color, so one gets improvised. Pick a dark neutral, confirm its ratio, and make it the site default.

When the deliverable is a color system and not only a logo — as it was for the identity redesign I did for New Mexico Interactive, the state’s electronic government services provider — the approved pairings belong in the guidelines. Which color on which background, at which size, for which purpose. Otherwise that judgment gets made months later by whoever is building the site, under deadline, without the palette in front of them.

Where contrast problems actually hide

Headlines and paragraphs get checked. These rarely do:

  • Placeholder text in forms — almost always too light, and it is often the only label a field has.
  • Text over photographs, where the ratio shifts as soon as the hero image is swapped.
  • Footers, where a dark brand background collects small legal and navigation text.
  • Hover and focus states, which pass at rest and fail on interaction.
  • Anything inside a plugin — booking widgets, donation forms, and search filters bring their own styles and do not know your palette.

How to check your own palette in ten minutes

You do not need to buy anything. Open WebAIM’s free contrast checker, enter two hex codes, and it reports the ratio with a pass or fail at each threshold. Do that for every combination your brand uses: each color on white, on black, on your dark neutral, and on your light background tint. The result is a small grid, and the grid is the deliverable — it tells a developer exactly what is permitted.

For an existing site, your browser’s developer tools show the contrast ratio in the color picker when you inspect text, and Chrome’s built-in Lighthouse audit flags low-contrast elements across a page. Automated scans catch the clear failures and miss text over images, so plan on a human pass too.

Is this legally required for a small business?

It depends who you are. The Department of Justice’s Title II rule gives state and local government bodies a hard requirement: WCAG 2.1 Level AA. An interim final rule in April 2026 extended the compliance dates a year, to April 26, 2027 for public entities serving 50,000 or more people and April 26, 2028 for smaller entities and special districts. If you do business with a city, a county, a school district, or the state, this is contractual, not aspirational.

For a private business, no federal regulation names a specific technical standard, but accessibility lawsuits against private websites routinely use WCAG 2 Level AA as the measure of whether a site is usable. Contrast is among the cheapest parts of that standard to satisfy and the most noticeable — to the roughly one in twelve men with some form of color vision deficiency, to anyone over 50, and to every person reading your site outdoors in full New Mexico sun.

Start with the grid, not the redesign

Before anyone proposes new colors, test the ones you have. Most palettes come out of that needing one darker variant and a written rule about sizes — an afternoon of work, not a rebrand. The colors keep doing their job on the truck, the sign, and the business card, and the website stops failing a test it was never designed to take.

Patrick Iverson is a brand strategist and web developer in Santa Fe who has run an independent practice in New Mexico since 2001, and who builds brand identities and color systems specified for screens as carefully as for print. If your palette has never been through a contrast check, it is worth an hour to find out where it stands.

Share this with the world
Patrick Iverson

Patrick Iverson

Brand strategist and custom WordPress developer, born and raised in Santa Fe. I've run an independent practice here since 2001, working with founders, marketing leads, and creative directors on rebrands, brand strategy, and websites built to last. I write here about the parts of that work clients rarely get to see.

Patrick is one of the most creative guys I have had the opportunity to work with. He seems to have an endless pool of ideas that are fun and fresh. Besides his talent, Patrick is also a good guy to work with. He is an asset to any person or company that decides to do business with him.

Brian Tercero, The Very Best of Santa Fe