Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Color.review?
Color.review is a browser-based tool for checking and exploring color contrast against the WCAG accessibility standard. You enter a foreground and background color, and it tells you the resulting contrast ratio and whether that pairing passes the relevant thresholds.
Its focus is practical readability rather than palette inspiration. The site's own explanation notes that our eyes perceive contrast differently depending on hue — blue text on white reads more easily than yellow — so a ratio check matters even when a combination "looks fine" to the designer.
What it checks
- Text contrast: WCAG 2.1 AA requires 4.5 for body text, and AAA requires 7.
- Large text: AA requires 3, AAA requires 4.5. Large text is defined as 14pt bold (about 18.66px) or larger, or 18pt (about 24px) or larger.
- Interface elements: inactive buttons and sliders need at least 3.
It also offers a random color option and a white background shortcut, and each check produces a shareable direct link, so you can hand a specific pairing to a colleague or drop it into a bug report.
Who it's for
Designers, front-end developers and content editors who need a quick pass/fail answer while choosing text, button and link colors. A typical scenario: you're styling a call-to-action button and want to confirm the label stays legible for someone with low vision or color blindness before shipping.
Trade-off to know
A single ratio is a narrow test. It won't tell you whether a whole palette is distinguishable for people with color vision deficiency, whether contrast holds on hover and focus states, or how colors behave in dark mode. Treat it as one check in a broader accessibility review, not a substitute for testing with real users and assistive technology.
Next step
Open Color.review, paste in your two hex values, and compare the reported ratio against the AA or AAA threshold for your text size. If you're deciding between "good enough" and "as accessible as possible," AA is the common baseline; AAA is the stricter target for body copy where you can afford it.
How do I check if my text and background colors meet WCAG contrast standards?
Use a WCAG contrast checker to compare the text color against its background. Color.review is built for exactly this: you enter a foreground and background color and it reports the contrast ratio alongside the WCAG 2.1 thresholds. It also lets you change the background, pick a random color, and use a white starting point, which makes it quick to test variations.
What the numbers mean
WCAG 2.1 has two conformance levels, and the target depends on the type of text:
| Content | AA (minimum) | AAA (stricter) |
|---|---|---|
| Body text | 4.5 | 7 |
| Large text / headlines | 3 | 4.5 |
| Inactive interface elements (buttons, sliders) | 3 | — |
Large text is defined as 14 point bold or larger (roughly 18.66px) or 18 point or larger (roughly 24px). So a large headline can pass at a lower ratio than a paragraph in the same color.
A practical workflow
- Sample the actual colors from your design, not the ones you intended — screenshots and browser color pickers both work.
- Enter the text color and background color in the checker.
- Read the ratio and compare it to the table above for that text's size and weight.
- If it fails, adjust lightness rather than hue first. Darkening a light text color or lightening a dark background usually moves the ratio fastest while preserving the palette's character.
- Re-check after any change, including hover states, disabled states and text over images.
Why hue matters, not just lightness
Contrast is about relative luminance, and our eyes do not treat all hues equally. As the page notes, blue text on white is easier to read than yellow at the same nominal brightness. That is a useful intuition when you are choosing a brand color for body copy: a saturated yellow or cyan that looks vivid in a logo often cannot carry paragraphs, while a deep blue or near-black can.
A concrete scenario
Suppose your brand blue is #4A90D9 on white. It may look fine to you but fall short of 4.5 for body text. You have three reasonable options: darken the blue until it passes, keep the blue for headlines where the 3 threshold applies, or use it only for large decorative elements and switch body copy to a darker neutral. Testing each variant in the checker takes seconds and tells you which compromise your design can afford.
The next step is to test your most common text-on-background pairs — body copy, links, buttons and captions — and note which ones fail. Fixing those few combinations covers most of what real readers will encounter.
What is the difference between WCAG AA and AAA contrast requirements?
WCAG sets two levels of contrast compliance, and the difference is simply how strict the minimum ratio is. AA is the baseline most teams target; AAA is a stricter tier that fewer designs meet, especially with brand colors.
| Content type | AA minimum | AAA minimum |
|---|---|---|
| Body text | 4.5:1 | 7:1 |
| Large text (roughly 18pt, or 14pt bold) | 3:1 | 4.5:1 |
| Inactive interface elements (buttons, sliders) | 3:1 | — |
These figures come from the WCAG 2.1 standard, which is what Color.review applies when it checks a color pair. The site's own explanation notes that contrast is perceived differently depending on hue — blue text on white reads more easily than yellow at the same nominal ratio — and that roughly 217 million people live with some form of visual impairment, which is the practical reason the thresholds exist.
Choosing between them: treat AA as the default for general web content, since it is the level most accessibility policies and audits reference. Reserve AAA for contexts where reading accuracy matters most — long-form documentation, financial or medical information, government services — or where you control the palette and can afford the tighter constraints. A common compromise is AA for body copy and AAA for the few critical text elements, rather than forcing the whole palette to 7:1.
A quick way to decide: if a color pair fails AA, fix it. If it passes AA but fails AAA, ask whether the text is something users must read correctly under poor conditions. If yes, darken or lighten until it clears 7:1; if it is decorative or secondary, AA is usually enough.
How can I design accessible colors for people with color blindness?
Start with contrast, not with color names. Color blindness changes which hues look similar, but the bigger readability problem is usually insufficient lightness difference between foreground and background. Color.review's page evidence makes this point directly: "We experience contrast differently in different colors," and blue text on white is easier to read than yellow because of how our eyes work.
Practical workflow
- Pick your base colors first. Choose a background and a text or UI color that already feel right for the brand or mood.
- Check the contrast ratio. For digital work, aim for WCAG 2.1 AA at minimum. Color.review's evidence states AA requires 4.5 for text, and 3 for headlines and large text. Large text is defined there as 14 point bold or larger, or 18 point or larger.
- Aim higher where you can. AAA requires 7 for text and 4.5 for headlines and large text. The page evidence shows an example current contrast of 12, which exceeds both AA and AAA for text.
- Check non-text elements too. Buttons, sliders and other inactive interface elements need at least 3 contrast, according to the same page evidence.
- Test with a simulation or grayscale view. Color blindness is not one condition, so don't rely on a single filter. Convert your design to grayscale and see whether the important distinctions survive.
- Don't rely on color alone. If a link, error state or chart series is only distinguished by hue, add a label, icon, underline or pattern.
Where color blindness specifically bites
- Red/green pairs for success and error states are the classic trap. Use icons and text labels alongside the colors.
- Charts and maps with many similar hues. Vary lightness and add direct labels.
- Links inside body text. If the link color is close in lightness to the body text, it becomes hard to spot even for people with typical vision.
- Focus and hover states. These are often low-contrast by default and need deliberate attention.
A quick decision rule
If you can only do one thing, increase the lightness difference between foreground and background. If you can do two, add a non-color cue for anything interactive or status-related. Color.review is a straightforward place to check a specific pair: Color.review. For the underlying standard, see the W3C WCAG guidance.
A useful next step: take your current primary button and body text, check both against their backgrounds, and adjust the lighter or darker color until the ratio clears 4.5 for text and 3 for UI elements.
What contrast ratio is required for large text or headlines?
For large text or headlines, WCAG 2.1 requires a minimum contrast ratio of 3:1 at the AA level and 4.5:1 at the stricter AAA level.
"Large text" here means text that is at least 14 point (roughly 18.66px) and bold, or at least 18 point (roughly 24px) regardless of weight. The same 3:1 threshold applies to non-text interface elements that aren't currently active, such as buttons and sliders.
A practical next step: if you're checking a heading, confirm both its size/weight and its ratio before signing off. A 20px bold headline clears the "large text" definition, so 3:1 is enough for AA — but a 16px regular-weight headline does not, and needs the full 4.5:1. You can test a specific foreground/background pair with a dedicated contrast checker such as Color.review, which applies the WCAG 2.1 AA and AAA thresholds directly.
How do I use Color.review to find accessible color combinations for my project?
Open Color.review and use its contrast checker as a pass/fail test for any foreground/background pair you are considering. The site's own explanation describes the workflow clearly: you set a text color and a background, and it reports the current contrast ratio against the WCAG 2.1 thresholds it uses. Its page evidence gives the concrete numbers to aim for, and includes a white background and a random-color option to speed up testing.
H3 What the numbers mean in practice
The thresholds quoted on the site are the decision rules you apply to each pair:
| Content type | WCAG AA minimum | WCAG AAA minimum |
|---|---|---|
| Body text | 4.5 | 7 |
| Headlines and large text | 3 | 4.5 |
| Inactive interface elements (buttons, sliders) | 3 | — |
"Large text" is defined there as 14pt bold (roughly 18.66px) or larger, or 18pt (roughly 24px) or larger. The page's worked example shows a current contrast of 12, which comfortably clears even AAA for body text — useful as a reference point for what "very safe" looks like.
H3 A practical loop
- Pick your brand or preferred color first, then test it rather than starting from a compliant pair.
- Enter the text color and background color, and read the ratio.
- If body text falls below 4.5, darken the text or lighten the background until it passes — small shifts often move the ratio a lot with mid-tone colors.
- Re-check the same pair for non-text UI: buttons, borders and sliders need at least 3.
- Test the pair again at your real sizes, since a color that fails for 16px body copy may be fine for a 24px heading.
The site's own note explains why this matters beyond rule-following: we perceive contrast differently depending on hue, so blue text on white reads more easily than yellow at the same nominal lightness. It also cites an estimated 217 million people living with a visual impairment. That is the audience argument for checking rather than eyeballing.
H3 Where it fits and where it doesn't
Color.review suits quick, single-pair checks during design or development — choosing link colors, button states, or a text-on-card combination. It is a checker, not a full design system: it won't generate a whole accessible palette for you, and passing contrast does not guarantee a palette looks good or that color alone isn't carrying meaning (add icons or labels for status colors).
If you need to audit a whole page rather than one pair, a browser-based accessibility audit tool is the better next step; if you need formal conformance documentation, work from the WCAG standard the site references directly.
A concrete scenario: you have a brand yellow and want white text on it. Test it — yellow-on-white is exactly the case the site flags as hard to read. If it fails, keep the yellow as a background accent and switch the text to a dark neutral, then verify that pair clears 4.5 before shipping.
User reviews (0)