-
Notifications
You must be signed in to change notification settings - Fork 82
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
Color-Blind friendly UI #426
Comments
Yeah, this change would be really nice (would help me as well). I think the best thing to do is to change green to blue, but that's just my suggestion. You could probably just create a setting that lets the user choose a colorblind mode if they wanted to. |
The ADA recommends against the following color combinations: |
That sounds like a good idea. do you want to work on this together? |
Specifying own colors would be a nice feature, though if that is too much work for you, we can stick to changing all instances of green to blue for now. Although, LEGUP might already have the color blue reserved for something, so you might have to pick a new color scheme. I'll leave the design up to you. |
You can find the colors for the proof tree in: The colors you should care about are CORRECT_COLOR and INCORRECT_COLOR, but you may want to play around with others to make things look nice |
…rs can specify their own colors for Bram-Hub#426.
Describe the current behavior of what you're trying to improve. If your enhancement request related to a problem, please also describe the problem.
Lots of LEGUP's UI is based on things lighting up red or green. The problem with that is that color blind people(like myself) have a hard time understanding when something is wrong.
Describe the improvement you'd like
Simple fixes can include changing the contrast between the reds and greens, or switching to red and blue.
High priority changes are the proof tree, short truth table rule icons and maybe the colors on the short truth table board.
Describe alternatives you've considered
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: