Free tool

WCAG color contrast checker

Check whether a text color and a background color meet the contrast ratios in the Web Content Accessibility Guidelines (WCAG) 2.1. The calculation runs in your browser. We do not upload your colors or store them on our server. After an accepted check, a share link keeps the colors in the URL fragment on your device.

Tool inputs and agreement

Enter hex colors (3 or 6 digits, with or without #) or use the color pickers. Then tick the box and choose “Check contrast”.

Colors to compare

The foreground: text, a link, an icon or a control border.

The color directly behind it.

Optional: link versus surrounding text

Leave empty unless you are checking a link that is not always underlined.

This tool runs in your browser. The colors you enter and the result stay on your device; this tool does not send them to ValleyFill or an AI provider. For Terms acceptance, we store only the acceptance time, tool path and Terms version in this tab’s session storage; that record is not sent to ValleyFill. Accessibility display preferences are stored separately in your browser. Normal page requests still reach our host, and our Privacy Policy describes server logs and anonymous visit counts. Don’t paste passwords or sensitive personal information. This is a free automated tool, not legal advice, certification or a guarantee of accessibility or compliance.

What the ratio means

WCAG defines contrast as a ratio of relative luminance, from 1:1 (the same color twice) to 21:1 (black on white). The formula is (L1 + 0.05) / (L2 + 0.05), using the sRGB relative-luminance definition published in WCAG 2.1. Hue is not a separate factor: the test is about light versus dark, which is what many people with low vision or color vision deficiency need. Source: Understanding Success Criterion 1.4.3 and the WCAG 2.1 contrast-ratio definition.

Thresholds this tool reports

WCAG says computed ratios should not be rounded when you compare them to a threshold: 4.499:1 does not meet 4.5:1. Source: Understanding 1.4.3.

How this relates to Title II

In April 2024 the U.S. Department of Justice amended its Title II regulation so that state and local government web content and mobile apps must meet WCAG 2.1 Level AA. The compliance dates, later extended by one year, are 26 April 2027 for public entities with a total population of 50,000 or more, and 26 April 2028 for those under 50,000 and for special district governments. Sources: ADA.gov fact sheet on the 2024 web rule and the Federal Register extension.

Because Title II points at Level AA, Success Criteria 1.4.3 and 1.4.11 are in that bar. Success Criterion 1.4.6 is Level AAA and is not required by an AA-only rule. This page is general information, not legal advice. Confirm your obligations with your counsel.

What this tool cannot do

It checks the colors you typed, not a live web page. Background images, transparency, gradients and font smoothing can all change what someone sees. Logos and purely decorative or inactive text have exceptions in 1.4.3. Meeting a ratio here is not a certification, an audit, or a statement that a site conforms to WCAG.

A free Title II Snapshot looks at basic signals on a public body’s own pages. A plain-language checker estimates reading level for text you paste.

More free tools