←back to thread

261 points david927 | 4 comments | | HN request time: 0.62s | source

What are you working on? Any new ideas that you're thinking about?
1. seanwilson ◴[] No.43154604[source]
A tool for building WCAG accessible Tailwind-like color palettes for UI/web design. :)

https://www.inclusivecolors.com/

> Instead of only working with a handful of colors, you can create a whole palette of swatches at the same time so you can see if they look good together.

> Precise control of every shades/tints in each swatch rather than being limited by autogenerated colors.

> See which color pairs contrast as you edit so you can create a palette with built-in WCAG accessibility. This way you can plan in advance which foreground colors (for headings, body text, form fields and so on) should contrast on which background colors, so you can avoid running into surprise low contrast issues later when designing.

replies(2): >>43156710 #>>43168311 #
2. seanwilson ◴[] No.43156710[source]
Responding to some feedback I got: I need to add better UI feedback for this, but you can drag whole hue/saturation/lightness curves if you click/drag between points on the curves.

Feel free to message me if you've got any tricky or tedious problems to do with creating color palettes that extra tooling like this might help with! I have more feature ideas but I want to understand more what others need.

I'm planning to write some articles for giving a more intuitive sense about WCAG color contrast rules and picking accessible colors too. From working with designers, I find many give up here because it takes a while to get your head around and it's often not obvious how to fix designs with failing contrast.

3. jmpavlec ◴[] No.43168311[source]
Tried it out on mobile and thought the site had broken the back button. Turned out to just be a history entry for every click/drag (which grows quite quickly). I found that quite off-putting but maybe that's a bit like an "undo" in this context...?

Either way, I didn't appreciate the 100+ entries in my history.

replies(1): >>43168383 #
4. seanwilson ◴[] No.43168383[source]
Oops, that should be it fixed. Desktop version has more features by the way, the mobile version is more of a preview.