Accessibility

[LilyAcorn]

One of the responses on reddit pointed out that the colour scheme isn't ideal for colourblind people:

as a colorblind, the set of colors that were chosen are really bad :(

Possible solutions:

• Change the colour scheme
• Add icons to the package list; ✓✗ and something else?
• Use a textured background for each state

[meshy]

Good plan, I'll do this as soon as I get the time.

[Tinche]

Speaking a a color-blind person (green/red/yellow, blue/purple), the reds and greens are totally fine. Green/orange is harder.

[sarahhodne]

At Travis CI we try to make sure that most of the red and green "build statuses" have an icon attached to them as well to help with this. I'd be interested to see what you come up with, though.

When we were investigating this, we found that it is possible to pick a red and green that don't look too bad for non-colour blind people, while still being discernible for colour blind people. However, they were still very close to eachother which may not be the best choice for using colors to easily get information (imagine if royal blue, cornflower blue and persian blue were used, not exactly easy to tell which is which at a glance).

[streeter]

I'm color blind (Protanopic), and found that tools like Color Oracle are helpful for people to see what I see. In this case, I can see the green and red used on the site, but it isn't idea. Trello has a color blind feature where they add patterns to the color labels as well. So just adding a pattern in addition to the color could be an easy way to go.

[mjtamlyn]

I'm going to put in another vote for 'that red and that green are perfectly distinguishable and I have colour vision issues' but I guess it's not necessarily about that as they're also signifying success or failure.

I would suggest that changing the colours or adding texture is irrelevant here, the only thing which will make things clearer for the small number of people affected would be to add icons (I.e. people with very severe colour issues or no colour vision).

[meshy]

Thanks everyone for their insight (hi @mjtamlyn!), and thanks to @Ian-Foote for the PR. If anyone has any further suggestions, or if I've missed something here that hasn't been improved, please open another issue :)