Contrastly
A colour contrast checker for Tailwind CSS, Radix Colors, Open Color, shadcn/ui and custom palettes — WCAG checks, contextual previews and design-token import/export in one workflow.
Five previews — text, UI controls, focus indicators, icons and data graphics — each judged by the WCAG criteria that actually apply. “Liquid Colour Transfer” respects reduced-motion settings.

01The problem
Checking colour contrast while building interfaces often meant switching between palette documentation, colour values and a separate checker. Comparing several shades, testing different UI elements or reviewing design tokens made that fragmented workflow even more noticeable.
02Design
Contrastly brings colour selection, a live preview and the result into one view. Tailwind CSS, Radix Colors and Open Color appear as continuous shade strips so neighbouring steps can be compared at a glance; shadcn/ui theme roles and custom colours use individual swatches. Foreground and background colours can be selected, swapped or entered directly.
Five preview types—text, UI controls, focus indicators, meaningful icons and data graphics—show a pair in different contexts. The ratio, a threshold meter and the applicable WCAG results sit inside each preview card and update immediately as colours change. The criteria follow the type of content being checked rather than treating all elements as text.
03Custom palettes and design tokens
Custom palettes can be created, edited and saved in the browser. Existing colours can also be imported by pasting code or uploading a file: the importer supports DTCG, Tokens Studio and Style Dictionary JSON, CSS variables and other supported colour lists, resolves aliases and identifies values it cannot use. Palettes can be exported as DTCG JSON or CSS variables, keeping the workflow useful for real design systems as well as individual colour pairs.
04Interaction design
Liquid Colour Transfer adds a playful visual touch: a drop travels from the selected swatch into the preview, spreads like liquid and settles with a gentle wobble. Reduced-motion settings are respected, with the device preference taking priority over the in-app switch.
The foreground/background target stays accessible while browsing palettes, including on mobile. Keyboard interaction is supported, with optional single-key shortcuts that can be disabled.
05Accessibility and testing
The checker applies the relevant WCAG criteria to text, non-text UI elements and focus indicators, and does not show a made-up AAA result where no AAA criterion applies. The interface itself uses semantic HTML and accessible UI primitives, with screen reader feedback for changes.
Validation includes source-level accessibility rules, Playwright end-to-end tests and axe checks for key desktop and mobile states, keyboard and focus behaviour, announcements, input validation and contrast calculations, alongside manual VoiceOver testing.