One of my major bug bears is the reliance on colour to communicate meaning. As a tester it’s super easy to question any product or communication that relies on colour. Just ask whether meaning will be lost if viewed without colour.
If you have a graph for example where each line is representing a finding or value, and they are each different colours then print the graph in greyscale and see if you can still make sense of the data. Is the key good enough, are the lines slightly different shapes (dot, dashes etc) or do you lose all functional understanding?
Relying on colour to communicate meaning is often a very lazy approach to designing products and it’s something we, as testers, should be acutely aware of and test for.
It’s never right or wrong to use colour to communicate meaning but we should always ask the question; “Will we ever have a circumstance where someone will not see the colour as we have defined it and hence lose the meaning?” Or some other better phrased question.
Here’s a good tool for putting yourself in the shoes of someone with varying magnitudes of colour blindness – http://colororacle.org/
My site under “Normal Vision”
My site under “Deuteranopia” vision – it’s a green deficiency and affects about 5% of males
My site under “Protanopia” vision – this is quite rare.
My site under “Tritanopia” vision – this is very rare.
My web site doesn’t rely on any colour to conduct meaning but you could quite easily see how some websites, graphics and explanations could clearly lose their value when viewed by someone with colour blindness.