4 ms·
It was fixed by replacing the HDMI cable. Unfortunately that only fixed it on that single computer. The correct fix would have been to use a different color.
by onion2k 8y ago
It was fixed by replacing the HDMI cable.
Unfortunately that only fixed it on that single computer. The correct fix would have been to use a different color.
- robocat 8y agoI agree. I admit I am still unsure how to decide what is an acceptable colour difference in the face of both human issues and technological complications.
- onion2k 8y agoThere are tools out there - https://webaim.org/resources/contrastchecker/ https://webaim.org/resources/contrastchecker/ Google actually added a new 'AAA' contrast checker to Chrome 73 in the devtools ('AA' was already there). https://www.youtube.com/watch?v=uddZX9ZK6wY https://www.youtube.com/watch?v=uddZX9ZK6wY
- robocat 8y agoI just tested that on pure red, and iOS button blue, on a white background. They both fail the AAA contrast test (on WebAIM and Google devtools). The majority of apps and websites would fail the AAA test in heaps of places (unless they have a "high-contrast mode"). #F00 on #FFF: fail on AAA (pure red on white: contrast 4). #07F on #FFF: fail on AAA ("iOS" button blue on white: contrast 4.13).
- onion2k 8y agoYes. 'Pure' colors tend to be bright, so white text doesn't contrast well enough. As a rule, designers don't use the pure color. I suspect lots of sites get accessibility wrong because developers prioritize using nice round numbers (eg F00 rather than D00) instead of accessible colors.