Skip to main content Web Accessibility Color Checker - EqualWeb
Start Free TrialBook a meeting
Accessibility Testing ֲ· Color

Web Accessibility Color Checker

Low-contrast text is the most commonly detected accessibility issue on the web. See exactly what WCAG 2.2 requires for color and contrast - and check every page, domain and PDF with EqualWeb's testing tools.

Run a free check Start Free Trial

A web accessibility color checker verifies that text and interface colors meet WCAG contrast requirements - at least 4.5:1 for normal text under WCAG 2.2 SC 1.4.3. Low-contrast text is the most commonly detected accessibility issue on the web, found on 83.9% of the top 1,000,000 home pages in the WebAIM Million 2026 report. EqualWeb builds color contrast checking into all of its testing tools - the free Accessibility Checker, the Accessibility Crawler, the Accessibility Monitor and the PDF Checker - so contrast failures are detected automatically as part of every WCAG 2.2 scan.

WCAG color requirements

What does WCAG require for color and contrast?

WCAG 2.2 sets exact, measurable thresholds for color contrast. Success Criterion 1.4.3 Contrast (Minimum), Level AA, requires a contrast ratio of at least 4.5:1 between normal text and its background, and at least 3:1 for large text. Large text means at least 18 point (about 24 px) regular weight, or 14 point (about 18.5 px) bold. The same ratios apply to images of text, with exceptions for logotypes and purely decorative text.

At the stricter Level AAA, Success Criterion 1.4.6 Contrast (Enhanced) raises the bar to 7:1 for normal text and 4.5:1 for large text. Contrast is not only about text, either: Success Criterion 1.4.11 Non-text Contrast, Level AA, requires at least 3:1 between user interface components - buttons, form field borders, focus indicators - and adjacent colors, and the same 3:1 for the parts of graphics needed to understand the content.

Color accessibility also goes beyond contrast math. Success Criterion 1.4.1 Use of Color, Level A, says color cannot be the only visual means of conveying information. A link distinguished from body text only by its color, or a form error shown only in red, fails this criterion even when every contrast ratio passes.

  • SC 1.4.3 Contrast (Minimum), Level AA: at least 4.5:1 for normal text, 3:1 for large text
  • Large text: at least 18pt (about 24px), or 14pt (about 18.5px) if bold
  • SC 1.4.6 Contrast (Enhanced), Level AAA: at least 7:1 for normal text, 4.5:1 for large text
  • SC 1.4.11 Non-text Contrast, Level AA: at least 3:1 for UI components and meaningful graphics
  • SC 1.4.1 Use of Color, Level A: color is never the sole indicator of meaning
Check your colors

How do you check your website's colors with EqualWeb?

You do not need a separate color picker to audit a live website. Color contrast checking is built into every EqualWeb testing tool as part of a full WCAG 2.2 scan, so contrast is checked together with everything else WCAG requires - on the pages and documents you actually publish.

Start with the free Accessibility Checker: enter a URL and get a 0-100 accessibility score in seconds, with every low-contrast element flagged, mapped to the exact WCAG success criterion such as 1.4.3, and prioritized by severity. From there, the testing suite scales to whatever you need to cover - a whole domain, a site that changes daily, or a document library - and all results feed one EqualWeb dashboard.

  • Accessibility Checker - free instant scan of any single URL; flags text below the required contrast ratio, with the WCAG 2.2 criterion and severity for each issue
  • Accessibility Crawler - a cloud-based Chrome extension that scans your entire domain in real time, including password-protected pages, forms and media
  • Accessibility Monitor - continuous scheduled scanning with a live 0-100 compliance score, so new contrast issues introduced by design or content changes are caught; free 100-page scan to start
  • PDF Checker - audits PDF documents across 7 accessibility categories; contrast items the AI cannot fully verify are marked Needs Review so a human can confirm them
Accessibility CheckerAccessibility CrawlerAccessibility MonitorPDF Checker
Fix and accommodate

How do you fix color contrast issues once you find them?

Every flagged issue in an EqualWeb report comes with clear guidance on what to fix and the exact WCAG 2.2 success criterion, so designers and developers know precisely which color pairs to adjust and by how much.

For remediation, the Accessibility Widget's AI automatically fixes 80+ common WCAG 2.2 issues in real time through the browser, without touching your source code. Automation has limits, though: brand palette decisions often need human judgment, and some criteria cannot be verified automatically. When the goal is full WCAG, ADA and EAA compliance, EqualWeb's Managed Compliance service adds certified IAAP/CPWA experts who audit, remediate, monitor and certify your accessibility end to end.

The widget also accommodates visitors directly. Its accessibility menu includes 9 profiles and 13+ assistive tools, with two profiles built specifically for color and contrast: the Visually Impaired profile strengthens contrast, enlarges text and adds a magnifier, and the Color-blind profile adjusts palettes so meaning never relies on color alone. These user-side adjustments complement - they do not replace - meeting the WCAG contrast ratios in your own design.

Most common failures

What are the most common color accessibility failures?

Low-contrast text is the single most common accessibility failure on the web. The WebAIM Million 2026 report, which analyzes the top 1,000,000 home pages, found text below the WCAG 2 AA contrast thresholds on 83.9% of home pages - up from 79.1% in 2025, and the most commonly detected issue of all - with an average of 34 distinct low-contrast instances per page.

Most of those failures come from a handful of repeating patterns: light gray body text and placeholder text on white backgrounds, text placed over photos or gradients, links distinguished from surrounding text by color alone, and error states that rely only on red. Because these issues are usually introduced one design or content change at a time, continuous scanning with the Accessibility Monitor catches them far earlier than a one-off audit.

  • Light gray text and form placeholder text below the 4.5:1 minimum
  • Text over images or gradients without a sufficient contrast layer
  • Links identified only by color, with no underline or other cue (SC 1.4.1)
  • Form errors signaled only by turning a field red
  • Buttons, icons and focus indicators below the 3:1 non-text minimum (SC 1.4.11)
FAQ

Color accessibility - frequently asked questions

How do I check if my website colors are accessible?
Run a free instant check with EqualWeb's Accessibility Checker: enter your URL and it scans the page against WCAG 2.2, flagging every element below the required contrast ratio, mapped to the exact success criterion such as 1.4.3, alongside a 0-100 score. For broader coverage, the Accessibility Crawler scans entire domains and the Accessibility Monitor rescans continuously as your site changes.
What contrast ratio does WCAG require?
WCAG 2.2 Level AA requires at least 4.5:1 between normal text and its background, and at least 3:1 for large text, defined as 18pt or 14pt bold (SC 1.4.3). Non-text elements such as buttons, form borders and meaningful icons need at least 3:1 under SC 1.4.11. At the stricter Level AAA, SC 1.4.6 raises the text requirements to 7:1 for normal text and 4.5:1 for large text.
Does EqualWeb have a color contrast checker?
Yes - contrast checking is built into every EqualWeb testing tool rather than offered as a separate picker. The free Accessibility Checker flags low-contrast text on any URL in seconds, the Accessibility Crawler checks contrast across your whole domain including protected pages, the Accessibility Monitor rechecks it continuously, and the PDF Checker covers documents. Every failure is mapped to the exact WCAG 2.2 criterion with guidance on fixing it.
What is the most common color accessibility mistake?
Low-contrast text. The WebAIM Million 2026 report found text below WCAG 2 AA contrast thresholds on 83.9% of the top 1,000,000 home pages, making it the most commonly detected accessibility issue, with an average of 34 distinct instances per page. Typical causes are light gray text, placeholder text, and text over images. An automated scan such as EqualWeb's free Accessibility Checker finds these in seconds.
Can the EqualWeb widget fix color contrast problems?
Partly. The Accessibility Widget's AI remediation automatically fixes 80+ common WCAG 2.2 issues through the browser, and its menu gives visitors user-side color options: the Visually Impaired profile strengthens contrast and enlarges text, and the Color-blind profile adjusts palettes so meaning never relies on color alone. Brand-level color decisions and issues automation cannot verify still need human work, which certified IAAP/CPWA experts handle through EqualWeb's Managed Compliance service.
Does WCAG allow using color alone to show links or errors?
No. SC 1.4.1 Use of Color, Level A, requires that color is never the only visual means of conveying information. A link distinguished from body text only by color, or a form error indicated only by turning a field red, fails even when contrast ratios pass. Add a second cue such as an underline, icon or text label. EqualWeb's testing tools flag color-related failures as part of every WCAG 2.2 scan.
Check your colors

See every contrast issue on your site

Run a free instant check of any page - color contrast included - or scan your whole domain with the Crawler and Monitor.

Book a meeting Start Free Trial
Talk to a specialistBook a meeting