[swift-evolution] Proposal SE-0009 Reconsideration
cocoadev at charlessoft.com
Mon May 23 13:41:43 CDT 2016
As another colorblind developer, this kind of is an issue. While I *can* discern colors, the only one that sticks out strongly is blue. If you’ve got reds, greens, browns, or oranges, my experience will be on a continuum from “I think that’s red?” in the best case, “I can figure this out if I accessibility-zoom it into a huge color patch” in the middle, and “Let me get out DigitalColorMeter” in the worst case. Purple, of course, is very hard to distinguish from blue. I guess grey is distinguishable, if you consider it a color. Other than that, syntax highlighting doesn’t do a lot for me.
Plus, I might end up having to use a different source editor sometimes, particularly when I’m doing a large refactor and Xcode is stuck in its “SourceKitService crash every time two characters are typed” thing. I’d really rather have things differentiable in the language itself rather than relying on external crutches.
> On May 23, 2016, at 11:43 AM, Jeff Kelley via swift-evolution <swift-evolution at swift.org> wrote:
> As a colorblind developer, this isn’t really an issue. The vast majority of colorblind people can discern colors. As long as the IDE allows you to customize which colors it displays, you can find a palette that will work with your eyes (for my type of colorblindness, for instance, I have difficulty differentiating blue and purple, so I wouldn’t use both in my syntax highlighting color scheme). As long as color isn’t the only thing differentiating on-screen elements, adding colors to syntax highlighting is beneficial even to us colorblind developers. :)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution