Palette Contrast Heatmapper

Enter your brand hex codes and instantly generate a full WCAG 2.1 & APCA cross-reference accessibility matrix for your entire design system.

Define Color Palette Step 1
Compliance Settings Step 2

AA (4.5:1) is the legal minimum under ADA/EAA. Normal body text (under 18pt / 24px) must meet this ratio. Large text (≥18pt) only needs 3.0:1. Failing this leaves you open to accessibility lawsuits.

Deuteranopia affects ~8% of men. When active, all colors are mathematically shifted through the biological confusion matrix before the contrast ratios are recalculated. The heatmap will visually render in simulated colors too.

pairs
pass
fail
Accessibility Matrix Waiting for input…

Define your colors above and click Generate Matrix to build the heatmap.

What is a Palette Contrast Heatmap?

When you are building a UI design system, testing a single text-on-background pair is not enough. Modern digital products use complex, layered systems where disabled buttons, hover states, input borders, error badges, and modal overlays all interact dynamically with multiple background shades simultaneously.

A Contrast Heatmap Matrix automatically cross-references every color in your design system against every other color, calculating the relative luminance and WCAG contrast ratios for all N×N permutations at once. You can instantly see which pairs are safe, which are illegal, and which fall into the "large text only" grey zone.

The Matrix Advantage

A 5-color palette has 25 possible foreground-background permutations. An 8-color palette has 64. Testing these one-by-one in a standard contrast checker takes 45+ minutes. Our heatmap generates all combinations in under a second, highlights passes in green and failures in red, and gives you a single screenshot for your design system documentation.

Why Design Systems Need an Accessibility Matrix

Scalable design systems use tokenized color scales (e.g., Slate-50 through Slate-900). Without a matrix, you risk silently introducing accessibility failures when applying tokens to new UI components.

  • Dark Mode Inversions: A combination that passes in Light Mode (e.g., Slate-800 on Slate-100) does not mathematically guarantee it will also pass when inverted in Dark Mode (e.g., Slate-100 on Slate-800) due to how the legacy WCAG algorithm handles perceptual lightness asymmetry.
  • Non-Text Contrast (WCAG 1.4.11): Active UI elements — text input borders, graphical focus indicators, toggle switches — require a minimum 3.0:1 ratio against adjacent backgrounds. A matrix helps you pick safe border colors instantly.
  • Disabled State Design: The most common accessibility failure in modern web design is low-contrast disabled buttons. The matrix helps you find a gray token that reads as "inactive" while remaining legally distinguishable.

WCAG 2.1 vs APCA (WCAG 3.0): The Math Explained

The industry is currently in transition between the legacy WCAG 2.1 standard and the upcoming APCA algorithm slated for WCAG 3.0. Our tool provides live calculations for both standards.

WCAG 2.1 Formula (Relative Luminance)

The current legal standard calculates contrast using (L1 + 0.05) / (L2 + 0.05) where L1 and L2 are relative luminance values. The formula is symmetric — swapping text and background does not change the ratio.

Standard Text Size Min. Ratio
WCAG AA Normal (<18pt / <24px) 4.5:1
WCAG AA Large (≥18pt or ≥14pt bold) 3.0:1
WCAG AAA Normal (Maximum strictness) 7.0:1

APCA (Polarity-Sensitive Perceptual Contrast)

The legacy WCAG 2.1 formula produces false failures for light text on dark, colorful backgrounds because it scales luminance linearly. APCA fixes this by modelling human visual perception logarithmically.

Crucially, APCA is polarity-sensitive — white text on a blue background generates a mathematically different Lc (Lightness Contrast) score than blue text on a white background. When you select APCA in our tool, the matrix becomes asymmetrical to reflect this perceptual reality.

Designing for Color Vision Deficiency (CVD)

Approximately 8% of men and 0.5% of women have some form of Color Vision Deficiency. The most common type is Deuteranopia (red-green color blindness).

Our tool includes a unique CVD matrix simulator. When you activate Deuteranopia mode, every color in your palette is run through a biological spectral confusion matrix before the contrast ratios are recalculated. The heatmap also re-renders all cells using the simulated color values, so you can see exactly what your green success badge and red error text actually look like to a colorblind user — and whether those two specific hues still have sufficient contrast between them.

Frequently Asked Questions

Testing Strategy

Why should I test my entire color palette instead of just individual components?

Testing individual components (like a single button) is time-consuming and often leads to regressions when scaling a design system. By generating a full heatmap matrix of your brand's color tokens, you establish a global "safe zone" mapping. This allows developers and designers to instantly know which text colors are legally permitted on which background colors without having to manually test every new UI feature.

Algorithmic Standards

How does the APCA algorithm differ from WCAG 2.1?

WCAG 2.1 calculates contrast using linear relative luminance, which fails to accurately model how the human eye perceives light on dark backgrounds (often causing false failures for perfectly legible white text on dark colors). APCA (the draft standard for WCAG 3.0) calculates a perceptual Lightness Contrast (Lc) score based on spatial frequency, font weight, and polarity, making it vastly more accurate for modern Dark Mode interfaces.

Accessibility Rules

Do disabled buttons and UI borders need to meet WCAG contrast guidelines?

Disabled components are technically exempt from the WCAG 4.5:1 text contrast requirement. However, active UI boundaries—such as text input borders, focus indicators, and essential graphical icons—fall under the "Non-text Contrast" rule (WCAG 1.4.11). These interactive elements must maintain a minimum contrast ratio of 3.0:1 against adjacent colors.

Accessibility Concepts

What is Deuteranopia and how does it affect UI design?

Deuteranopia is the most common form of red-green color blindness, affecting millions globally. Users with Deuteranopia have difficulty distinguishing between red, green, and yellow hues, which often blur into a muddy brown. If your UI relies solely on green for "success" and red for "error", colorblind users may not be able to tell the difference. Always pair color shifts with distinct icons or helper text.

Data Privacy

Does this tool upload my proprietary brand colors to a server?

No. Our Palette Contrast Heatmapper is entirely client-side. All luminance math, APCA calculations, and Deuteranopia matrix simulations run locally inside your browser using JavaScript. Your proprietary design tokens and hex codes are never transmitted to our servers, ensuring total privacy.

Legal Compliance

What are the legal risks of failing ADA web compliance?

In the US, the Americans with Disabilities Act (ADA) has been repeatedly interpreted by courts to apply to digital storefronts and web platforms. Failing to meet WCAG 2.1 AA contrast requirements can open companies to significant liability and accessibility lawsuits. Ensuring your global color palette passes the matrix is the first step in mitigating legal risk.

Rate Palette Contrast Heatmapper

Help us improve by rating this tool.

4.8/5
1,048 reviews