|
|
|
|
|
by tomxor
2543 days ago
|
|
Had you used a monochrome filter on software while adding accessibility you probably wouldn't suggest using shade as method of differentiation (it's simple to try, i recommend it). We already use luminescence mainly for discerning shape, when you throw "shades" into the mix it's usually too subtle for the purpose of differentiation. Additionally in the physical world how are you going to determine the shade of something relative to something that is not present? i.e if you only have one cable in front of you. We don't have absolute perception, it tends to be affected by context, additionally the lighting now seriously affects your judgement... The reason this is so different to colour is because luminescence is a single receptor type (rods), with which you are trying to compare intensity of an area of one type of signal filled with other detailed information; whereas with colour you have three signal types (cones), in combination and at a lower detail than rods, so it's effectively separate information with at least 2^3 completely distinct permutations to differentiate in almost any lighting or context. This also explains why the absence of only a single cone receptor type has a significant impact on perception since it drops to 2^2 halfing the completely distinct permutations, of which two are merely black and white, so you actually drop from 6 to 2 non-monochromatic permutations - so you see it is far more challenging using either shade or partial cone types. |
|