Skip to main content
Guide3 min read

The Two-Hour Rescue Plan for Text That’s Halfway to Invisible

By The bee2.io Engineering Team at bee2.io LLC

Fix light gray text on white with a two-hour accessibility playbook. Learn what to scan, which WCAG contrast ratios to use, and which fixes to ship first.
Fix light gray text on white with a two-hour accessibility playbook. Learn what to scan, which WCAG contrast ratios to use, and which fixes to ship first.

Somewhere on your website, a line of light gray text is trying to tell a customer why their payment failed. It has chosen to do this in the visual equivalent of a whisper from inside a coat closet.

Light gray text on white looks restrained in a design review. On a phone by a sunny window, it looks like the browser forgot to finish loading. And if you have low vision, the same text can be hard to read in a perfectly lit room. A published 2024 audit of one million homepages found detectable low-contrast text on 81% of them. That figure covers low contrast broadly, including the gray-on-white special your design system may be serving with every meal.

If your entire web team fits in a booth, give yourselves two hours. Spend 30 minutes finding failures, 60 minutes fixing the ones that matter most, and 30 minutes checking what you shipped. You can do the whole pass with a browser, a contrast checker, and whoever can change the CSS.

First 30 minutes. Follow the trouble.

Pick one common task, such as signing up or checking out, and run through it on a phone-sized screen. Submit an empty form, enter an invalid value, and look for the line that tells you how to recover. Error messages, field hints, prices, and renewal terms deserve early attention. The footer can survive another half hour without a wellness check.

Run an automated contrast scan on those screens, then manually inspect text over images, gradients, or translucent panels. Open any dialogs and trigger any error states before you check them. The browser’s developer tools can show the computed text color. If opacity or a layered background changes what actually appears, check the rendered colors behind the text.

For WCAG AA, normal text needs a contrast ratio of at least 4.5:1. Large text can use 3:1 once it reaches 24 CSS pixels at regular weight or about 18.67 CSS pixels in bold. On pure white, #aaa is about 2.32:1. It misses both thresholds, so promoting it to a heading just gives the problem a bigger office.

Next 60 minutes. Make the gray earn its rent.

Group the failures by the style or component that produces them. If the same muted text token colors the field hints and the order summary, one change can fix both. Check where else that token is used and on which backgrounds. If it also drives decorative borders, give readable secondary text its own token so your form fix doesn’t accidentally turn the whole site into graph paper.

On white, #767676 comes in at about 4.54:1. That’s a pass with barely enough room to slide a receipt under it. Try #666 at about 5.74:1 as a starting point, then test it against the backgrounds where it actually appears. You can keep the visual hierarchy with spacing, weight, and placement. A hint can look secondary and still tell someone what to type.

Last 30 minutes. Try to break your own fix.

Repeat the task with your changes in place. Recheck the actual text and background pairs on the screens you touched, including dark mode if the site offers it. Trigger the same errors and rescan. Take a quick look on a real phone if you have one handy. The contrast checker measures the ratio. The phone helps you notice that the now-legible error message got pushed under a sticky button, because apparently the button has tenure.

Leave the approved text and background pair in the component docs, and add one line to the review checklist asking which backgrounds changed text appears on. Give the remaining failures a short list ordered by what they keep people from doing. That’s enough for the next person to pick up the work without reopening the Great Gray Debate.

Open your own site, get one form field wrong, and check the contrast of the message that tells you how to fix it. If you only have five minutes, spend them there. That little sentence has a job to do.

Disclaimer: This article is for informational purposes only and does not constitute legal, professional, or compliance advice. SCOUTb2 is an automated scanning tool that helps identify common issues but does not guarantee full compliance with any standard or regulation.

accessibilitycolor contrastWCAGvisual design

Stop finding issues manually

SCOUTb2 scans your entire site for accessibility, performance, and SEO problems automatically.