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

[UX] provide colorblind options for State column in Qubes VM Manager #1533

Open
mfc opened this Issue Dec 21, 2015 · 4 comments

Comments

@mfc
Member

mfc commented Dec 21, 2015

The yellow and green of the State column in Qubes VM Manager are hard to distinguish for colorblind users.

thanks for reporting @hdevalence

@mfc mfc added the UX label Dec 21, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Dec 21, 2015

Member

@bnvk any ideas? Maybe different shapes?

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Member

marmarek commented Dec 21, 2015

@bnvk any ideas? Maybe different shapes?

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

@bnvk

This comment has been minimized.

Show comment
Hide comment
@bnvk

bnvk Feb 18, 2016

I think replacing the green dot with an "On" icon and replacing the yellow dot with something else should work. While not colorblind, I've never been sure what the yellow dot actually means @marmarek ?

bnvk commented Feb 18, 2016

I think replacing the green dot with an "On" icon and replacing the yellow dot with something else should work. While not colorblind, I've never been sure what the yellow dot actually means @marmarek ?

@unman

This comment has been minimized.

Show comment
Hide comment
@unman

unman Apr 16, 2017

Member

@andrewdavidwong Confirmed this issue still arises in 3.2 milestone, although it should be trivial to resolve.
Who is our go to UX person?

Member

unman commented Apr 16, 2017

@andrewdavidwong Confirmed this issue still arises in 3.2 milestone, although it should be trivial to resolve.
Who is our go to UX person?

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Apr 16, 2017

Member

Who is our go to UX person?

I'm afraid we don't have one at the moment.

Member

andrewdavidwong commented Apr 16, 2017

Who is our go to UX person?

I'm afraid we don't have one at the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment