News for hackers. Stuff that matters.
Re:Accessible Palette: stop using HSL for color systems by refulgentis on Tuesday August 29, 2023 @06:16PM (#37314865)
That's the sales pitch for HCT, you get to claim you can normalize along C to get similar colorfulness, or normalize along T to get similar lightness (with the bonus of T getting you the WCAG/a11y compatability). And why is yours right? Because you used the latest and greatest color science for H (hue) and C (chroma / saturation) and great color science for T, matches WCAG.

This isn't quite as helpful as it might sound, i.e. it can't settle all debates, then design needs to become playing within the system: ex. lets say you land at you want mostly pastels. You could settle on lightness 90 -- get nice yellows, teals, but...no red!?!? It turns out light red is pink. And then on top of it, the yellows and teals colorfulness can get crazy high: lets say 80. But red can only get to 16, this breathy pink.

This can be extremely aggravating, ex. yellow. It just doesn't contrast with white, there's absolutely no way to get any a11y number to tell you that a nice bright yellow can be a button in light mode. But the system is empowering in that you know you can't do any better on the implementation, and you can trust the #s.

Re:Accessible Palette: stop using HSL for color systems by pohl on Tuesday August 29, 2023 @07:03PM (#37315339)
That sounds like the answer to my question is: that's what HCT is meant for, but no there aren't any such resources, because it’s supposed to be as simple as tweaking the numbers. Am I reading that right?

Also, I'm getting the impression that I'd have to be working in the Android ecosystem, maybe?

Re:Accessible Palette: stop using HSL for color systems by refulgentis on Tuesday August 29, 2023 @10:07PM (#37316792)
It's available in Typescript/C++/Java/Dart and I believe ObjC either already or soon.