Color contrast checker
Enter a text color and a background color to get the WCAG contrast ratio and an instant pass or fail for AA and AAA, for normal text, large text and interface elements, with a live preview.
Contrast ratio
7.55:1
Large text (24 px)
Normal body text at 16 px. The quick brown fox jumps over the lazy dog.
Small print and captions at 13 px.
- AA · normal textneeds 4.5:1Pass
- AA · large textneeds 3:1Pass
- AAA · normal textneeds 7:1Pass
- AAA · large textneeds 4.5:1Pass
- AA · icons, borders, UI partsneeds 3:1Pass
Large text means at least 24 px (18 pt) regular or about 18.7 px (14 pt) bold. Ratios use the WCAG 2.2 formula.
How to use the color contrast checker tool
- 1
Enter two colors
Type HEX codes or use the color pickers for the text and the background.
- 2
Read the ratio
The ratio runs from 1:1 (no contrast) to 21:1 (black on white). Each WCAG level shows pass or fail.
- 3
Adjust until it passes
Darken or lighten one color and watch the ratio update. Swap them to check the reverse.
The WCAG thresholds
Level AA asks for 4.5:1 for normal text and 3:1 for large text (success criterion 1.4.3). Level AAA asks for 7:1 and 4.5:1 (1.4.6). Icons, input borders and other parts of the interface need 3:1 against what’s next to them (1.4.11).
What counts as large text
At least 18 point (24 CSS pixels), or 14 point (about 18.7 CSS pixels) in bold. Logos and purely decorative text have no contrast requirement.
How the ratio is calculated
Each color’s relative luminance is worked out with the WCAG 2.2 formula, then the ratio is (lighter + 0.05) ÷ (darker + 0.05). WCAG says not to round, so 4.49:1 fails AA; the ratio shown here is cut to two decimals, never rounded up.
Frequently asked questions
What contrast ratio do I need?+
For most websites and apps, aim for WCAG AA: 4.5:1 for body text, 3:1 for large text and for icons and input borders.
Does this cover WCAG 3 or APCA?+
No. This checks WCAG 2.2, the current standard that most accessibility laws and policies point to. APCA is a different method being explored in WCAG 3 drafts.
Do placeholder and disabled text need to pass?+
Placeholder text that carries information should meet 4.5:1. Disabled controls are exempt under WCAG, though readable is still better.
Is it free? Do I need an account?+
Yes, it’s free and there’s no signup, watermark or daily limit. An account is only needed if you want teammates or clients to comment on the file in edits.io.
Need feedback, not just a file?
Capture any public web page in full and collect pinned comments on it. Clients comment with a link, no account needed.
See website feedback in edits.io