AccessLens

How to fix: “Elements must meet minimum color contrast ratio thresholds”

Low-contrast text, explained in plain English, with the exact fix and code you can copy.

Scanner rule:
color-contrast
Standard:
WCAG 1.4.3 Contrast (Minimum) (Level AA)

What this error means

Every piece of text needs enough difference in brightness between the letters and the background behind them. WCAG measures that difference as a ratio from 1:1 (no difference) to 21:1 (black on white). Normal-size text must reach at least 4.5:1. Large text, meaning roughly 24px or bigger, or about 18.7px and bold, only needs 3:1. The same 3:1 rule applies to meaningful user-interface parts such as input borders.

Low-contrast text is the most common accessibility failure on the web: the WebAIM Million 2026 report found it on 83.9% of home pages. Source: WebAIM Million

Who it affects

People with low vision, color-vision differences and age-related vision changes, and also anyone reading a phone screen in bright sunlight. It is one of the few accessibility problems that affects almost everyone at some point.

Where it usually hides

  • Light gray body text or captions (#999 on white is only 2.85:1, which fails)
  • Placeholder text inside form fields
  • Text laid over photos or sliders, where the contrast changes as the image changes
  • White text on a brand color that looked fine in the logo but is too light for small type
  • Footer links, small print and 'sale' badges

How to fix it

  1. Right-click the flagged text in Chrome, choose Inspect, and click the color square next to 'color' in the Styles panel. Chrome shows the contrast ratio and a line marking the passing range.
  2. Darken the text, or lighten the background, until the ratio reaches 4.5:1 (or 3:1 for large text). Changing the text color is usually the smaller visual change.
  3. If your brand color is the problem, keep it for large headings and buttons, and use a darker shade of the same color for small text.
  4. For text over images, add a solid or semi-transparent overlay behind the text, or move the text onto a plain panel.
  5. Check hover and focus states too. A link that passes at rest but turns pale on hover still fails.

Before and after

Before

<style>
  .caption { color: #999999; background: #ffffff; } /* 2.85:1, fails */
</style>

Light gray on white looks tidy but fails.

After

<style>
  .caption { color: #767676; background: #ffffff; } /* 4.54:1, passes */
</style>

#767676 is the lightest gray that still passes 4.5:1 on white. Darker is safer.

On your website platform

WordPress, Shopify, Wix and Squarespace

Look for the color or typography settings in your theme or site-styles panel (in WordPress, Appearance, then Customize, or the Site Editor). Change the text and background colors there so the fix applies everywhere, instead of editing one block at a time.

Common mistakes

  • Fixing one page while the same light color is set in the theme, so it comes back everywhere else.
  • Assuming the logo or decorative text must pass. Logos and purely decorative text are exempt, but real content is not.
  • Checking only against white. Check the actual background, including gradients and hover states.

How to check your fix

  • Re-run a scan and confirm the contrast issue is gone.
  • Use the contrast checker in Chrome DevTools, or the free WebAIM Contrast Checker, to confirm the ratio on the real colors.
  • View the page on your phone outdoors, or turn the screen brightness down, as a quick reality check.

Is this on your site?

Run a free scan and see every page and element affected. No account needed.

Questions people ask

What contrast ratio do I need to pass WCAG?

4.5:1 for normal text and 3:1 for large text, at WCAG level AA. Level AA is the standard courts and settlements most often point to.

Does placeholder text have to meet the contrast ratio?

Yes. Placeholder text is real text that people need to read, so it falls under the same 4.5:1 rule. The browser's default placeholder gray often fails.

Are logos and disabled buttons exempt?

Logos and brand names are exempt, and so are disabled controls. Anything else a visitor is expected to read is not.

Keep reading

Automated scans catch only part of what WCAG covers, and fixing a scan result is not a legal guarantee of compliance. Last reviewed November 16, 2026.