WCAG 2.1 AAA Checker

WCAG 2.1 AAA

14.68:1

Pass (≥ 7:1)

Sample text here

You Might Also Need

WCAG 2.1 AAA Checker tests a color pair against the 7 to 1 enhanced contrast level, the stricter of the two thresholds WCAG 2.1 defines.

What is WCAG 2.1 AAA Checker?

WCAG 2.1 AAA Checker tests a pair of colors against 7 to 1, the enhanced contrast level that WCAG 2.1 defines above the ordinary AA minimum. It reports one ratio to two decimal places and one verdict, which makes it the fast way to find out whether a pair is anywhere near the stricter standard before you commit design time to it.

The AAA level is defined at two sizes, and both are above their AA counterparts:

  • Normal text needs 7 to 1, a substantial step up from the 4.5 to 1 that AA requires.
  • Large text needs 4.5 to 1, which is the same figure AA asks of body copy.

The verdict here is decided at 7 to 1 regardless of the size of the text, so the large-text allowance is not applied and a heading pair that clears AAA for large text will still report Fail.

The underlying figure is the WCAG 2.x contrast ratio. Each color is converted to sRGB, its channels are linearised, and the three linear values are weighted 0.2126 red, 0.7152 green and 0.0722 blue into relative luminance. The ratio is the lighter luminance plus 0.05 over the darker plus 0.05, rounded to two decimals before it is compared against the threshold. Reaching 7 to 1 usually means one color is very light and the other very dark, which is why AAA layouts tend to look high-contrast and spare rather than rich.

Read the result as the AAA contrast verdict for the pair, with the 7 to 1 contrast threshold as the single line being tested. The page does not report how much headroom a passing pair has, so one that scrapes the threshold and one far beyond it carry the same verdict, and the enhanced contrast ratio printed in the panel heading is where that difference becomes visible. If the figure sits close to the line, treat it as unproven and move a color further before relying on it.

What this single gate cannot tell you is as important as what it can.

  • Large text is judged at 7 to 1, not the 4.5 to 1 that AAA actually permits, so the check is stricter than the specification for headings.
  • It says nothing about AA. In practice anything that passes 7 to 1 also passes 4.5 to 1, but the page does not confirm that for other pairs in your palette.
  • Non-text contrast is excluded. Component boundaries and focus rings are not evaluated, and they carry their own 3 to 1 requirement.
  • No alpha, no gradients and no third surface behind the pair.
  • Font weight and rendered size are not inputs, so the verdict describes the colors and not the typography.

Reach for this page when AAA is a contractual or accessibility-policy requirement rather than a preference, such as public-sector work or a design system that ships an enhanced mode. If the resulting constraint flattens a palette you care about, the honest answer is usually to satisfy AAA in the reading surfaces and use AA elsewhere, rather than compromising the whole scheme.

How to use WCAG 2.1 AAA Checker

  1. Set the foreground color and the background color in the two swatch fields.
  2. Read the ratio shown in the panel heading, accurate to two decimal places.
  3. Check the Pass or Fail line, which compares that figure against 7 to 1.
  4. If it fails, adjust whichever color is easier to move and re-read the ratio, since small lightness changes move the figure sharply near the top of the scale.

When to use WCAG 2.1 AAA Checker vs related tools

Use the WCAG 2.1 AAA checker when a policy, contract or accessibility statement commits you to the enhanced level, most often for long-form reading text that has to hold up for everyone. Use the WCAG 2.1 AA checker when AA is the agreed bar, the WCAG 3.0 APCA checker when you are questioning whether a ratio gate reflects perceived contrast at all, and the palette accessibility checker when a whole palette rather than one pair has to be assessed.

Privacy & Security

This tool runs entirely in your browser — no data ever leaves your device. There is no server round-trip, no upload, no logging, and no account required. Your input is processed locally using client-side JavaScript and is never stored, transmitted, or accessible to anyone else. When you close the tab, everything disappears.

Frequently asked questions about WCAG 2.1 AAA Checker

© 2026 Racira Colors — Free browser tools for color workflows.