In my experience, “colorblindness” is generally understood to include a range 
of color vision “anomalies.” I have the most common form, deuteranomaly. Green 
does not look as bright as other colors to me, and I have a hard time 
distinguishing greenish colors from reddish colors when they are desaturated 
(like greenish-brown versus reddish-brown), or when looking at fine points or 
lines rather than large areas of color. I can still easily distinguish bright 
green from bright red, even in a small area, but it’s very difficult to 
distinguish a small amber LED from a green one.

It’s best to avoid using color to communicate essential information with no 
backup mechanism; to use something like the contrast ratio formulas from WCAG 
2.2 to ensure adjacent colors contrast sufficiently in luminance and not only 
in hue; and to particularly avoid contrasting colors that are both reddish or 
greenish when possible, since these are the most troublesome for the largest 
number of people.

On Tue, May 23, 2023, at 1:08 AM, Jens-Ulrik Petersen wrote:
> On Tue, May 23, 2023 at 12:47 PM Neal Gompa <ngomp...@gmail.com> wrote:
>> I actually would prefer that we color both, and make it obvious that
>> "root" is special. We should account for common color-blindness
>> issues, though.
>
> Sure, I think I agree: perhaps purple for root?
>
> I am all for "color blind testing" (though I am not completely sure 
> that "color-blind" is the right term here
> though I am not an a11y expert - I thought color blind is more about 
> differentiating different colors like green and red,
> but if you mean visual impairment/contrast/readability then I 
> completely agree).
> I think in the end it will come down also to wider user testing since 
> there are so many different terminals
> and color palettes around.
>
> Anyway that's why I proposed green since it seems to have reasonable 
> contrast for both light and dark terminals (unlike blue/cyan/yellow 
> often).
> I assume that may also be why Ubuntu and Nixos went with green.
>
> Jens
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to