WCAG Contrast Checker
WCAG 2.1 AA/AAA contrast ratios. Pick foreground and background colors — results update instantly.
WCAG Contrast Checker
▶ Live Preview
▶ Copy as CSS
What is WCAG and why does contrast ratio matter?
WCAG (Web Content Accessibility Guidelines) is the international standard for digital accessibility, published by the W3C. The contrast ratio requirement exists because users with low vision, color blindness or poor display calibration may not be able to read text that lacks sufficient luminance contrast against its background. WCAG 2.1 defines contrast as the ratio of the relative luminance of the lighter color to the relative luminance of the darker color, expressed as a number between 1:1 (no contrast) and 21:1 (black on white). Conformance Level AA — required by most accessibility laws including the EU Web Accessibility Directive and the ADA — sets a minimum of 4.5:1 for normal text and 3:1 for large text (18pt+ or 14pt+ bold).
AA versus AAA: which level should you target?
WCAG AA (contrast ratio 4.5:1 for normal text, 3:1 for large text) is the legally required minimum for public-sector websites in most jurisdictions and the expected standard for commercial web products. WCAG AAA (7:1 for normal text, 4.5:1 for large text) is the enhanced level — recommended for text-heavy content where maximum readability is critical, such as body copy, legal documents and healthcare interfaces. The W3C notes that AAA conformance cannot always be achieved for all content, and it is not recommended as a blanket requirement for entire sites. A pragmatic approach is to target AA across the board and AAA for primary body copy and critical UI text.
Large text and bold text rules
WCAG defines large text as text at 18pt (24px) or larger, or 14pt (approximately 18.67px) or larger in bold. These thresholds exist because larger or bolder text is easier to read at lower contrast due to its greater stroke weight and visual prominence. Large text requires a contrast ratio of only 3:1 to pass AA, compared to 4.5:1 for normal text. This matters for interface design: a heading at 24px can use a lighter color than a body paragraph at 16px, giving you more design flexibility at the top of the typographic hierarchy.
Color contrast beyond text
WCAG 2.1 also defines contrast requirements for non-text elements under Success Criterion 1.4.11 (Non-text Contrast): UI components (buttons, form inputs, focus indicators) and meaningful graphical elements (charts, icons, diagrams) require a 3:1 ratio against adjacent colors. This is frequently overlooked in design systems. Common failures include: light grey placeholder text in inputs, low-contrast focus outlines, and icon-only buttons where the icon color has insufficient contrast against the background. The WCAG checker in this tool focuses on text contrast — use the live preview section to visually verify non-text elements.
Limitations of the contrast ratio model
The WCAG 2.1 contrast formula is based on relative luminance and has known limitations for certain color combinations. It can report a passing ratio for near-black colors that appear very similar to each other visually, and it does not account for hue — some color-blind users may struggle with red/green combinations even when the luminance contrast passes. WCAG 3.0 (in development) proposes the APCA (Advanced Perceptual Contrast Algorithm) as a more accurate model. For critical accessibility use cases, always supplement automated contrast checking with user testing across diverse visual profiles and devices.