(don't forget to "allow pasting" in [chrome] console first)
A lot more inconvenient for others to have to pick colors that satisfy all potential sight issues, which is primarily why I think it should be an OS solution rather than an individual creator's responsibility. It's not that I don't care about those with the sight issue, it's purely about who is responsible for creating a reasonable solution. And honestly, there's no way every creator is going to study accessibility and so it's just a never ending uphill battle. If you had a tool in your system already that could help, why wouldn't you use it?
Co-authored-by: Claude <claude@anthropic.com>
1) Avoid contrasting red/green and blue/yellow, as these are common colorblind pairs.
2) Pick shades that still look different when shown in grayscale.
3) All bar charts should have 0 at one end.
4) Please no 3-D pie charts.
To find good color palettes, check out https://colorbrewer2.org
I generally am against people who have expectations of how they want others to communicate. Be it colors, pronouns, whatever- you’re just setting yourself up for disappointment and it’s not out of malice so just move on or find your own way to deal with what people are putting out there.
https://www.vischeck.com/run.html
It twiddles colors in a physiologically-aware manner to improve legibility for colorblind observers:
https://github.com/wadelab/VischeckTinyeyes/blob/main/websit...