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

Use color-blind friendly color! Or let us configure colors. #2

Closed
ghost opened this issue Apr 14, 2016 · 3 comments
Closed

Use color-blind friendly color! Or let us configure colors. #2

ghost opened this issue Apr 14, 2016 · 3 comments

Comments

@ghost
Copy link

ghost commented Apr 14, 2016

.clue-error and .clue-ok are too close in color to be easily distinguished with thin fonts.

@ghost ghost closed this as completed Apr 14, 2016
@clupasq clupasq reopened this Apr 15, 2016
@clupasq
Copy link
Owner

clupasq commented Apr 15, 2016

Good point!

Would it be OK to use red/blue instead of red/green?
Or to alter other aspects of the text (like background, or weight) only in case it's wrong?

Please let me know your thoughts on this.

Thanks!

@ghost
Copy link
Author

ghost commented Apr 15, 2016

Red for error and blue for OK would be fine. In fact that's what I ended up
with when I realized I could use Stylish to change it myself. :)
On Apr 15, 2016 1:47 AM, "Cristian Lupașcu" notifications@github.com
wrote:

Good point!

Would it be OK to use red/blue instead of red/green?
Or to alter other aspects of the text (like background, or weight) only in
case it's wrong?

Please let me know your thoughts on this.

Thanks!


You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#2 (comment)

@clupasq
Copy link
Owner

clupasq commented Apr 15, 2016

Wow, didn't know about Stylish - cool extension. :)
I will update the colors when I have some time.

Thanks a lot: I learned two good things today.

clupasq added a commit that referenced this issue Apr 15, 2016
@clupasq clupasq closed this as completed Apr 15, 2016
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