How do I get started with the color × color tool?

Updated

Go to colorcolor.in in your browser. That's the whole setup — color × color is a web tool for building accessible color systems for UIs, and it runs in the page with no install step described in the site's own materials. You'll want a browser window wide enough to work comfortably, and a rough idea of the UI you're designing for, because the tool's job is to produce a perceptually uniform palette you can carry into that design.

What color × color actually does

The site describes itself as "a tool to create accessible color systems for UIs," and it lets you work in either Okhsl or HSLuv color spaces to build perceptually uniform colors. That phrase — perceptually uniform — is the reason the tool exists. In a perceptually uniform space, equal numeric steps look like equal visual steps, so a ramp of ten shades reads as an even progression instead of bunching up in the shadows or blowing out in the highlights.

If you've ever hand-picked a "50–900" scale and found that the jump from 700 to 800 is barely visible while 100 to 200 is a cliff, that's the problem this class of tool is built to remove.

Before you start: what to have ready

You don't need an account or any files to open the tool. What helps is deciding these first, because they shape every choice afterward:

  • Your base or brand color. The single hue the system is built around.
  • How many steps you need. A common UI scale runs from a very light tint to a very dark shade; decide the count before you generate.
  • Where the system will be used. Text on backgrounds, borders, hover states, and disabled states all pull different requirements from the same ramp.
  • Your accessibility target. If you're aiming at WCAG contrast thresholds for text, say so up front — it changes which steps you can use for body copy versus decoration.

The basic flow

  1. Open colorcolor.in. The tool loads directly in the browser.
  2. Choose your color space — Okhsl or HSLuv. This is the first real decision, and it's covered in its own section below.
  3. Set your base color. Pick the hue your system centers on.
  4. Generate the ramp. The tool produces a set of steps that are evenly spaced perceptually, not just numerically.
  5. Check the steps against your use cases. Identify which steps work for text, which for surfaces, which for accents.
  6. Export or copy the values into your design file or codebase.

The order matters less than the loop: most people set a base color, look at the ramp, and adjust — the point of a perceptual space is that small adjustments behave predictably.

Okhsl or HSLuv — how to choose

Both are perceptually uniform spaces; they differ in their design goals and in how they handle the extremes of lightness and saturation.

Okhsl HSLuv
Design intent A more perceptually accurate take on the familiar HSL model Keeps HSL's saturation/lightness semantics while staying perceptually uniform
Familiarity Feels closer to how designers already think about HSL Also HSL-shaped, but with different gamut behavior
Practical difference Worth trying when you want ramps that stay vivid across the range Worth trying when you want predictable, evenly spaced steps that map cleanly onto HSL-style controls

If you have no strong preference, generate the same base color in both and compare the ramps side by side. The one whose mid-tones and extremes look evenly spaced to you, on the surfaces you'll actually ship, is the right one for that project. There's no universally correct answer — the choice depends on the palette and the UI.

Common sticking points

The ramp looks right but the text doesn't pass contrast. Perceptual uniformity makes steps even; it doesn't automatically make any given step accessible against any given background. Check the specific foreground/background pairs you'll use.

The colors look different in your design tool than in the browser. Color management settings differ between applications. Compare values in one place before committing.

You can't decide on a step count. Start with the number of distinct roles you actually have — background, surface, border, muted text, body text, strong text, accent — and let that drive the scale rather than picking a round number first.

You're not sure the space matters. It does, but mostly at the edges: the lightest and darkest steps are where non-uniform spaces fall apart, and those are exactly the steps UI systems lean on for backgrounds and dark-mode surfaces.

What to do next

Once you have a ramp you're happy with, the useful follow-up is to define roles rather than shades — assign each step a job (page background, card surface, primary text, and so on) so the system survives a rebrand or a dark-mode variant. If you're still deciding between the two spaces, the dedicated comparison of Okhsl and HSLuv is the next thing to read.