01
Why does the app use OKLCH?
Because lightness in OKLCH matches what your eye actually perceives. Generating a palette in
it means a red and a yellow at the same lightness read as equally heavy, which is what makes
a set of tokens feel like one system. Colours that fall outside the display gamut are mapped
by reducing chroma, so the hue you chose is preserved.
02
What do the contrast grades mean?
They are WCAG 2.1 ratios. AAA is 7:1 or better, AA is 4.5:1, and AA Large is 3:1, which
applies to text at roughly 18pt and above or 14pt bold. Anything below that is marked Fail.
The exact ratio is shown beside every grade so you can see how much headroom you have.
03
A colour pair is flagged. What now?
The report tells you which of two things went wrong. If the deficiency caused it, the
colours differ mainly in hue, so change one in lightness instead. If they were always too
close, no simulation was needed to break them, and they need separating regardless.
04
Where do my presets live?
In your own iCloud account, synced privately across the devices you are signed in to. We
have no server and no account, so we never see them. If presets are not appearing on a
second device, check that iCloud Drive is on for both.
05
Can I change the exported names or format?
The export uses the token names shown in the palette, so they stay consistent across CSS,
SwiftUI and Android XML. CSS can be written in OKLCH or HSL, and light and dark can be
exported together as one theme. If you need a format we don't cover yet, tell us, as that is
usually how a new one gets added.
06
The app isn't in my language
It ships in English, German, Spanish, French, Italian, Japanese, Korean, Brazilian
Portuguese and Simplified Chinese, following your device language. Generated code comments
stay in English deliberately, since exported code usually ends up in a shared repository.