Metric Idea: Inclusion of Color Blind

[nicorikken]

Color blindness is remarkably common. At work I have seen awkward scenario's where graphs or slides are shown to stakeholders, only to find out they aren't able to distinguish the green and red lines due to their color blindness. I found this blogpost to give an elaborate overview of the issue and possible measures.

Some general advice for measures:

• Avoid relying on color for a visual distinction, whether they are icons or graphs. Lightness or patterns can be alternatives.
• If making distinction with color, use a color scheme that fits color blind.'
  • E.g. Jenkins uses blue/red to signal correct/false rather than the the troublesome green/red.

Ideas for metrics:

• Are the used visuals readable by color blind? (e.g. event announcement, event slides, documentation, resulting software)
• Is checking for color blindness embedded in the community? (e.g. decent color scheme provided and adoption is checked with changes) (the need of embedding is a generic remark for all metrics)

Larger scope: I can see this becoming part of a larger metrics like 'inclusion of visually impaired', whether blind, partially blind, or even dyslexic.

[ElizabethN]

@nicorikken we have added these considerations to our Event Accessibility Metric, and included a link to the blog post you mentioned, under the "references" section of the metric. Thanks again for bringing this up!

[germonprez]

Suggestion to create a new Project Accessibility metric that can include color blindness as addressed within a project. Similar to Event Accessibility.

[ElizabethN]

We moved this metric idea to the central spreadsheet and are tracking it there. Thanks everyone!