8 issues tagged with this topic.
Roughly 8% of men and 0.5% of women have some form of color vision deficiency. Most palette guidelines respond by stripping color personality down to high-contrast gray-scale safe combinations. There is a better approach: designing with color role redundancy so that no piece of information relies on hue alone.
We just shipped a tool that takes any block of CSS, Tailwind config, or token JSON and returns: the named ColorArchive match for every color, near-duplicate clusters, every pairwise WCAG AA contrast failure, and specific swap-to-fix suggestions. Runs entirely in your browser.
Dark mode is not just a color inversion. Building a proper dark mode palette requires rethinking the entire color hierarchy — with different luminance relationships, contrast ratios, and chromatic intensity requirements than light mode.
The most common mistake in dark mode color systems is lifting light-mode colors onto dark backgrounds without adjustment. Colors that look rich and saturated on white appear washed out and gray on dark surfaces. The physics of simultaneous contrast explains why, and the fix is systematic rather than case-by-case.
WCAG contrast requirements do not mandate black text on white backgrounds. There is a wide range of color combinations that pass AA and AAA thresholds while delivering a distinctive visual identity. This issue explores how to find them systematically.
Why passing WCAG contrast ratios does not guarantee a readable palette, what the numbers cannot measure, and how to audit a color system for real-world accessibility beyond the 4.5:1 threshold.
Why accessible accents fail when they are chosen by compliance alone, how Orchid Bloom proves that expressive hues can pass contrast, and where the starter pack helps teams ship faster.
A note on WCAG contrast ratios, the /contrast tool, and why dark mode palette decisions matter more when accessibility is in scope.