The 5 best colour contrast checkers (2026)
Nitpique, the WebAIM Contrast Checker, Chrome DevTools, WAVE and axe DevTools compared: which check one pair and which check a whole page, which see hover and focus states, and which suggest a colour that passes.
By Swapnil Gupta · · 8 min read
Contrast checkers come in two kinds. Some check one pair of colours you give them, which is right while choosing a palette. Others check a page, which is right once there is a page: they find the pairs you did not think to test. The best workflow uses one of each.
Here are five worth knowing, what each one checks, and where each is the right choice. For the rules they all test against, see how to check colour contrast on a live website.
We make Nitpique, so it is first on this list. Every other tool here is one we would recommend for the job we name, and we say where each one does better than ours.
At a glance#
| Tool | Checks a whole page | Checks hover and focus states | Suggests a passing colour | Free |
|---|---|---|---|---|
| Nitpique | Yes | Yes | Yes | Yes |
| WebAIM Contrast Checker | No | No | Partly | Yes |
| Chrome DevTools | Partly | Partly | Yes | Yes |
| WAVE | Yes | No | No | Yes |
| axe DevTools | Yes | No | No | Partly |
How we picked#
Every tool here tests against WCAG's contrast minimums and is used widely in practice. We compared what each can see (a pair, an element, or a whole page), whether it reaches the states a design file leaves out, and how much it helps you fix a failure, not only find it. Facts about each tool were checked against its own pages in November 2026.
1. Nitpique#
- Type
- Browser extension
- Price
- Free, no account
- Runs in
- Chrome, Edge, Brave, Arc and Firefox
- Best for
- Finding and fixing every failure on a real page
Nitpique checks the selection or the whole visible page and lists failures worst first, against WCAG 2.2, with APCA alongside as a second opinion (it is not a WCAG requirement). It also checks controls in their hover, focus and disabled states, where many failures hide, and for each failure its Fix button copies the nearest colour that passes. A colour-blindness simulation and an accessibility score sit in the same panel.
Where it wins
- Whole page and every control state in one pass
- Copies the nearest passing colour for each failure
- WCAG 2.2, plus APCA as a second opinion
Where it falls short
- Contrast of icons and borders, and of text over photos, are still coming
- Checks one page at a time, not a whole site
2. WebAIM Contrast Checker#
- Type
- Web page
- Price
- Free
- Runs in
- Any browser
- Best for
- Choosing a palette, before there is a page
Source: webaim.org · checked November 2026
The reference tool most people learn on. Enter a text and a background colour and it gives the ratio, with a pass or fail for normal text, large text and graphics at AA and AAA. Lighten and darken buttons step a colour until it passes. It knows nothing about your page, which is both its limit and why it is quick.
Where it wins
- Instant, exact and trusted
- Nothing to install
Where it falls short
- One pair at a time, typed in by hand
- Cannot see transparency or states
3. Chrome DevTools#
- Type
- Built into the browser
- Price
- Free
- Runs in
- Chrome and every Chromium browser
- Best for
- Checking and fixing one element precisely
Source: developer.chrome.com · checked November 2026
Click the colour swatch beside any color in the Styles pane and the picker shows the element's contrast, draws the AA and AAA lines on the colour area, and offers a passing colour. The CSS Overview panel lists low-contrast text across the page, and Lighthouse includes a contrast audit. States are reachable too, by forcing them with :hov, one element at a time.
Where it wins
- Exact, with the real rendered colours
- Suggests a passing colour in the picker
Where it falls short
- Page-wide checks see only the state on screen
- States must be forced by hand, element by element
4. WAVE#
- Type
- Browser extension and web service
- Price
- Free extension; the API is paid
- Runs in
- Chrome, Edge and Firefox
- Best for
- A broad accessibility review with contrast in it
Source: wave.webaim.org · checked November 2026
WAVE, also from WebAIM, marks accessibility issues on the page itself: missing alternative text, structure, labels, and contrast errors, which it lists in their own tab. It is a whole-page review rather than a contrast tool, which makes it a good second pass once the colours are fixed.
Where it wins
- Contrast alongside every other automated check
- Issues drawn on the page, easy to show others
Where it falls short
- Sees only the state on screen
- Leaves finding a passing colour to you
5. axe DevTools#
- Type
- Browser extension
- Price
- Free extension; Pro plans for guided tests and teams
- Runs in
- Chrome, Edge and Firefox
- Best for
- Teams that also test in code
Source: deque.com · checked November 2026
Deque's extension runs axe-core, the open-source rules engine many automated accessibility tests are built on, from a DevTools tab. A scan lists contrast failures with every other issue it finds, and because the same engine runs in test suites, what it reports in the browser matches what fails in CI.
Where it wins
- The same rules as automated tests in your pipeline
- Few false positives, by design
Where it falls short
- Sees only the state on screen
- Guided and team features are in the paid plans
Which one should you use?#
- Choosing colours for a palette: the WebAIM Contrast Checker.
- Checking a page before it ships: Nitpique, for every text and control state and a passing colour for each failure.
- One element, while coding: the DevTools colour picker.
- A wider accessibility review: WAVE or axe DevTools, with axe when the same rules should run in your tests.
No automated checker catches everything: text over photos, colour that carries meaning on its own, and focus that is visible but hard to see still need a person to look. A tool finds the failures quickly so that time goes to those.