-
Notifications
You must be signed in to change notification settings - Fork 855
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
Login/Can't post empty comment: hard to read #7992
Comments
All good points, mate. I also stated in your topic before that they should be darker, and the mock-ups that I made. Support. |
White on #f7a935 has a contrast ratio of 1.89:1 |
Why not just black on orange? |
I mean, I am not sure about others, but I think it would be easier for me to read white on a dark red, and the red has already been used on scratchr2 pages, which has a higher contrast than the scratch-www color at least from what I remember. |
Either one depends on people's preferences, not those who just want it for style. This is about accessibility. |
I used white on red because black on orange would definitely give me headaches and be hard to read for me |
Or even just bold the text. |
While logging in, most errors are hard to read:
(using required field error as example here)
This also occurs with empty comments:
Steps to Reproduce
Possible resolution would be changing the hex color of the text from #fff / white to #000 (black)
Operating System and Browser
Firefox 121.0 (32 bit)
Used LibreWolf 120.0-2 (Windows MSIX Package) for screenshots
The text was updated successfully, but these errors were encountered: