Skip to content
← Back

Color Contrast Checker - WCAG Accessibility Test

Media
Runs locally · Not uploaded

Free online color contrast checker tool that tests foreground-background contrast ratio, validates WCAG AA/AAA standards, and auto-suggests accessible colors

Was this result helpful?

For local tools, open DevTools → Network and search your input — it should not appear in requests.

Next steps

Usage Guide

Check WCAG contrast for a foreground/background pair with four AA/AAA badges. Local only — no auto-fix-to-pass; adjust colors yourself and retest.

1. Check a pair

  1. Set foreground and background.
  2. Read the ratio.
  3. Inspect the four WCAG badges.

2. Thresholds

  • AA: 4.5:1 normal / 3:1 large.
  • AAA: 7:1 normal / 4.5:1 large.
  • Large text ≈ 18pt or 14pt bold — follow your policy.

3. When it fails

Darken/lighten text, add a scrim, or raise size to large-text rules. Sample the real pixels behind glyphs on gradients.

4. Must-check

  • Buttons, links, placeholders.
  • Chart series vs labels.
  • Design tokens for body and muted text.

5. Pair tools

  • Color converter.
  • Tailwind color finder.
  • Gradient generator, then re-check.

6. Limits

One pair at a time; use color-blindness simulation separately.

FAQ

No. Contrast is pure front-end luminance math — your foreground and background colors are computed on your machine and never uploaded to any server.

WCAG relative-luminance contrast: AA requires ≥4.5:1 for normal text and ≥3:1 for large text; AAA requires ≥7:1 and ≥4.5:1 respectively. The preview is only for eyeballing — the ratio and the four AA/AAA × normal/large badges are authoritative.

Roughly 18pt and up (or 14pt bold), with your own accessibility spec as the final word. Raising a size into the large-text bracket relaxes the threshold, but that's no excuse for small body copy.

There is no one-click fix. With a fixed brand color, adjust the text side's lightness first, or add a solid or semi-transparent scrim behind the text; on gradients and images, sample the actual pixels behind the glyphs; and test interactive states (hover/focus) as their own pair — a passing default state says nothing about the focus ring.

Buttons, links, placeholders, and disabled states (disabled must still be readable or clearly unusable); chart series colors and axis labels; secondary text and text on borders in design-token reviews; and error-message red on light-red backgrounds.

Not necessarily — passing guarantees a luminance difference, not distinguishability. Re-check important states with a color-blindness simulator and keep non-color cues like icons and copy; for palette conversion or finding the nearest Tailwind color, pair this with a color converter or a Tailwind color finder.

Related Tools

Related Articles