Grey text on a white background is a habit, not a design style
Why pale type reads fine on the designer's monitor and fails outdoors
A customer told you last week she couldn't read your opening hours on her phone. She was standing outside your shuttered door at the wrong time. When you pulled up the site yourself, you finally saw it too: light grey text on a white background, barely there.
That grey looks fine on the screen that designed it. A calibrated monitor, indoors, at eye level, in a dim room. Everything reads fine in that room.
Take the same page outside into daylight, or onto a phone with the brightness turned down to save battery, and the same grey nearly disappears. The design didn't change. The lighting did. Pale type has very little margin for that kind of change.
A screenshot taken on the designer's desk will always look fine. It's worth checking the site on an actual phone, outdoors, before trusting that screenshot at all.
A cloudy day and a bright one give different results. Test on the brightest day available, since that's the visitor a pale page is most likely to lose entirely.
Keep a couple of screenshots from that outdoor test. They're a useful reference the next time anyone suggests going even lighter with the palette.
Contrast checkers a non-designer can actually operate
You don't need design training to check this yourself. A contrast checker takes two colors — the text color and the background behind it — and returns a ratio against the guideline for readable text.
Paste in the hex codes from your brand guide. Or pick the colors straight off a screenshot. Either way, the tool tells you plainly whether the pairing passes or falls short, in seconds, with no jargon involved.
Run this on the two or three color pairings used most across the site: body text on background, buttons, and any text sitting on a colored panel. That covers most of what actually gets read.
Type size, line length, and spacing on a phone screen
Contrast is half the readability question. Size and spacing are the other half. Body text under a certain size forces a visitor to zoom in on a phone, which breaks the layout around it.
A line of text stretching the full width of a wide screen is harder to track than one broken into a narrower column. Tight line spacing makes paragraphs blur together at a glance.
All three compound the same problem contrast does. Text that's technically present but genuinely hard to read is not much better than text that's missing.
A quick fix: read a paragraph of the actual site out loud, at arm's length, on a phone. If you lose your place mid-sentence, a visitor will too.
Color used as the only signal, and who misses it
A form field outlined in red to show an error. A chart with no labels beyond its colors. A sale price shown only in a different shade of the regular price. All of these rely on a visitor being able to distinguish that specific color shift.
Color blindness affects a meaningful share of visitors. Glare or a cheap screen affects plenty more, on top of that. Pair color with a second signal: text, an icon, an underline, a pattern.
The color can stay. It just can't be the only thing carrying the meaning. A red border with the word "required" beside it works for everyone the red border alone leaves out.
The same logic applies to a map pin, a status dot, or anything else where color alone is doing the explaining. Add a label. It takes a minute.
Brand palettes that need a second darker shade for text
Plenty of small business brand palettes were built for a logo, not for paragraphs of text. A soft blue, a blush pink, a warm tan — lovely as an accent, and a surprisingly poor choice for paragraphs of body copy.
The fix isn't abandoning the palette. It's adding one darker variant of the brand color, built specifically for text. The lighter original stays for backgrounds, borders, and accents, where contrast doesn't carry as much weight.
A lot of design software can generate that darker variant from the original in a couple of clicks, so the brand still reads as itself.
Keep the original color in the logo and the accents where it always lived. The new shade only needs to show up wherever text sits directly on top of it.
Headlines sitting on top of photographs and video
A white headline over a bright photo looks striking in the mockup. So does dark text over a busy background video. Both turn unreadable the moment the image underneath shifts — a cloud in the photo, a bright frame in the video loop.
A solid color panel behind the text keeps the headline legible no matter what's moving underneath it. So does a gradient overlay darkening just the area behind the words. Either fix takes an afternoon, not a redesign.
Check this one on the actual homepage, not a mockup. A video that loops through several frames can be readable at second one and unreadable at second four.
This is one piece of the larger accessibility picture — the build questions that sit underneath all of it are worth reading if you haven't already. Once the color and type are sorted, running the rest of the self-check covers what's left.
Moving backgrounds and video carry a related but separate set of problems, covered at captions, autoplay, and the motion that makes some visitors unwell. And if the person who chose the palette is still involved, knowing what to ask them about accessibility is worth doing before the next round of changes.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go