Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please make this extension more colorblindness-friendly #366

Open
craigfowler opened this issue May 20, 2022 · 0 comments
Open

Please make this extension more colorblindness-friendly #366

craigfowler opened this issue May 20, 2022 · 0 comments

Comments

@craigfowler
Copy link

The test explorer is working just fine in my VS code thanks, but as a colorblind developer, I find it really difficult to find passing/failing tests in the explorer view. I think that the curly-braces used to indicate namespaces and/or test suites turn red or green depending upon pass/fail, but I have an incredibly difficult time seeing the difference between them. I know that the icons inside are either tick/cross and that's fine, but it means I have to expand every suite to find the failing ones.

Suggestions

  • Make the colors configurable, perhaps with presets suitable for the various forms of colorblindness
  • For the red braces, invert the icon's background/foreground (so it's a white brace inside a red background square). This way the icon is noticeably different from the green braces even if the developer is unable to perceive color.
  • Use shades of red/green with markedly different lightness (for example a very pale/faint green, but a bold/solid red). This way they are distinguishable by lightness even if the developer cannot do so by hue

Workaround

For now, what I am doing is ensuring that the "Add to Problems" setting is enabled. This way, I can find the failing tests that way, instead of using the explorer. It does make the explorer a little less useful though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant