I have no data about this. It seems plausible, but it feels unlikely according to my intuition. To me it seems more likely that their naive algorithm for contrast ratio (which is based on their formula for relative luminance) doesn't match human perception in some cases. Color perception is complicated.
https://www.w3.org/TR/2008/REC-WCAG20-20081211/#contrast-rat...
https://www.w3.org/TR/2008/REC-WCAG20-20081211/#relativelumi...
It would be better to come up with an estimate of plausible ranges of screen brightnesses and a plausible range of surrounding contexts, and then use a real color appearance model to decide on visual contrast at the extremes of those plausible scenarios.
But whoever designed the WCAG guideline was either not an expert in human vision or perhaps thought that would be too complicated to use a model which more closely approximated perceptual responses.
The WCAG guideline should be seen as nothing more than a loose suggestion, with lots of false negatives. That is, if it says something is illegible, then it should probably be changed. but if it says the contrast is okay, then that should be checked by a better model (or human inspection).
Both white-on-medium-blue and black-on-medium-blue buttons are inaccessible and should be avoided if possible.
In isolation, for me, the white on blue, has contrast bleed which makes the text fuzzy.
Again, in isolation, the black on blue is much sharper.
Together however, when presented side-by-side, the black on blue feels to be lower contrast. It's almost like my brain is using the black on blue to help compensate the weakness of the white on blue.
If you define brightness as (r+g+b)/3 you're doing it wrong. NTSC defines brightness something like .7g + .25r + .05b. (I forgot the exact numbers, but it's really extreme) JPEG assumes something a lot less extreme, but still >.55 green.
Source: I had to implement a saturation function for work and assumed brightness is (r+g+b)/3 and it looked like fucking garbage. In fact image/video compression is full of hacks like this. 4:2:0 is dominant in the video compression space for a reason. Human brains simply don't give a fuck about the color blue.
The entire point is that the designers eye can not possibly percieved things the same as every other person. To evaluate readability you should look not at the average rating from all users but the lowest average for each condition/group as they will be the ones who cant read it.
I had to stop reading at the defense of gray text - there's no excuse for that. Ever.
https://uxmovement.com/wp-content/uploads/2019/10/cca-button...
You might find it aesthetically inferior to black on yellow (or whatever) but there’s nothing inherently illegible about it.
To the grandparent poster chadlavi:
> This is so stupid it hurts. It doesn't pass contrast guidelines because bright things on bright things are hard to distinguish
You are misunderstanding the author’s claims, and then responding with mean-spirited insults. Try reading the whole article again more carefully, and with an open mind. If you are confused about something in specific a person who has studied color science a bit can try to clear up any questions you have.
The author is not suggesting that you should put white text on a middle-blue (or whatever) background, but merely pointing out that the WCAG heuristic for contrast is not in accord with human lightness perception.
The white-on-blue vs. black-on-blue is just a demonstrative example, showing that even though white-on-blue has higher contrast according to human perception, the WCAG heuristic instead rates the contrast of black-on-blue to be higher. This happens because the WCAG heuristic assumes human response to light intensity to be logarithmic, an inaccurate model which breaks down quite badly when you have dark text on a dark background.
In practice both white-on-medium-blue and black-on-medium-blue buttons have relatively low contrast and should be avoided where possible. With white text a darker background would be better. With black text a (much) lighter background would be better.
I mean, how scalable is that in the long run?
Every average obscures a bag of unknown causative factors that we have yet to tease apart.
As our medical knowledge increases and the number of conditions we can diagnose rise, the 'lowest average for each condition' monotonically decreases as a simple mathematical fact.
Without an automated solution to making things accessible to every condition, designers and implementors will be buried under a mound of individual cases.
Come to think of it, someone should have already done the work and color sets should be published somewhere.
This is so stupid it hurts. It doesn't pass contrast guidelines because bright things on bright things are hard to distinguish for low-vision individuals! It doesn't matter what you think looks better.
The correct solution for the designer is to use a darker orange or blue then put white text on it. Get correct contrast AND something that subjectively feels better. The correct answer for a designer is never to go "eh, I like my version better, I'll ignore these rules."