Measure the contrast ratio between two colours and see which WCAG criteria it passes for body text, large text and interface components. Runs locally.
7.53:1
Passes all 4 WCAG checks below.
Normal text at 13px. This is the size most body copy and most interface labels are set at, and the size the AA threshold of 4.5:1 exists for.
Large text at 18px bold
Heading at 24px
Non-text elements — icons, input borders, focus rings — need 3:1 against what is behind them, which this pair meets.
Passing these checks is not the same as being accessible. Contrast is one success criterion; keyboard access, focus order, labels and structure are separate, and this tool does not test them.
Contrast Checker runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
Contrast ratio is the single most common accessibility failure on the web, and the easiest to fix. Two colours produce a ratio between 1:1, where they are identical and nothing is readable, and 21:1, which is black on white. WCAG sets the bar at 4.5:1 for normal body text, 3:1 for large text, and 3:1 for interface components and meaningful graphics — those are the AA thresholds, and they are what accessibility regulations in most jurisdictions point at.
The arithmetic is specified rather than invented. Each channel is converted from its 0–255 value to a linear value, the three are weighted into a relative luminance, and the ratio is the lighter luminance plus 0.05 over the darker plus 0.05. The weighting is not equal: green contributes over seven tenths of perceived luminance and blue barely seven hundredths, which is why pure blue text on black fails badly while pure green on black passes comfortably.
"Large text" has a specific meaning in the guidelines: at least 18pt, or 14pt when bold — roughly 24px, or 18.66px bold, in CSS. It is a lower bar because larger letterforms have thicker strokes and survive lower contrast. Applying the large-text threshold to body copy is one of the most common ways an audit gets quietly failed.
Semi-transparent colours are composited against the background before measuring, because that is what the eye sees. A ratio computed from the raw value of a colour at 60% opacity describes a colour nobody is looking at.
A passing ratio is necessary and not sufficient. Contrast says nothing about whether focus is visible, whether a control can be reached from the keyboard, whether colour is the only thing carrying meaning, or whether text is legible at the size it actually ships. It is one success criterion among many, and it is the one worth checking first because it is pure arithmetic.
For AA, which is what most regulations reference: 4.5:1 for normal text, 3:1 for large text, and 3:1 for interface components and meaningful graphics. AAA asks for 7:1 and 4.5:1 respectively. Decorative graphics and disabled controls are exempt.
At least 18pt, or 14pt if bold — about 24px, or 18.66px bold, in CSS. Below that the normal-text threshold applies. Size is the rendered size, so a heading scaled down on mobile may cross back over the line.
By the WCAG formula. Each sRGB channel is linearised, combined into a relative luminance weighted 0.2126 red, 0.7152 green and 0.0722 blue, and the ratio is (lighter + 0.05) / (darker + 0.05). It is specified arithmetic, not a perceptual model.
Because blue contributes very little to perceived luminance — around seven hundredths against green's seven tenths. A saturated blue can look vivid and still sit close in luminance to its background, which is exactly what the ratio measures.
They are composited over the background first, then measured, because that is the colour a reader actually sees. Measuring the raw value of a colour at partial opacity would describe something that never appears on screen.
No — it clears one success criterion. Keyboard access, visible focus, heading structure, form labels, motion preferences and not relying on colour alone all still have to be right. Contrast is the first thing to check because it is the easiest to measure.
This tool implements the WCAG 2 ratio, which is what current conformance requirements and legislation refer to. APCA is a newer perceptual model being developed for WCAG 3, and until that is finalised the ratio here is the one you will be audited against.