-
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
Improve accessibility #36
Conversation
While it's good to improve contrast, this looks too ugly. Before: After: To name a few things:
|
Hey @sindresorhus , Thanks for the feedback! I believe the perception of how it looks is mostly a matter of opinion. Nonetheless, I would agree that it could be better. I have a few counter points about your comments though.
I didn't understand this point. Could you expand on it?
Could you expand on that? As I understand, not having the big contrast means it's not accessible, as that's the "label" for the field as well.
That was based on WebAim contrast checker and the background used in that block. Do you have some source to check the color, or some extra information on why it shouldn't be that much?
How you suggest a better approach should be?
I see what you mean, and that's an interesting comment. I believe browsers wouldn't have implemented it as a default behavior if the caret was enough though, there is not a lot of highlight to it. We need to also remember that accessibility is for those with low vision that might not see the caret, as it's quite subtle. Also some people might be using using screen magnifier that are not covering the whole screen and not find the focus.
I can do that, for sure. Out of curiosity, give this is not being applied in a fixed layout and the image seems to have enough quality to see it clearly (at least for me), could you explain why that is important? |
The checkmark should be green.
Accessibility is not binary. We can improve it without extreme contrast. A placeholder is not meant to be as readable as normal text. We can instead make the font slightly less thin. However, in the future, we could consider supporting the upcoming
Slightly darker than the current. Regarding the input field. We could maybe do a shadow. Something that looks more pleasing.
It looks blurry on high-DPI screens. |
Hey @sindresorhus, Sorry for the delay in sending this changes, I had a few very busy weeks. I'm pushing some update based on your comments. I hope you consider this better, but we can do some more adjustments if you find it necessary.
I'm colorblind and I missed that 😅 . I don't think we need to fix that in terms of a11y though.
I made it 400 (before was 300), In my opinion it was better with 300 and slightly darker. Let me know if this is ok, or you prefer to revert back to the original.
I like that idea. Although my only concern left would be the placeholder, and just because it is currently serving as a label as well.
I reviewed the colors I implemented there and turns out I got it a little bit off tone. Finding the right tone I managed to get "base" a little bit ligther. The thing is What do you think?
That was a very nice suggestion. I think it looks a lot nicer now!
Does this look ok now? |
- Replace outline for box-shadow on focused elements. - Revert input placeholder color and make font-weight 400 (before 300). - Improve focus state on toggle-all label. - Add green color on completeded items checkbox. - Update colors on filter buttons. - Update screenshot image.
|
Hello @sindresorhus, I pushed some changes. I hope you are ok with them an we can merge this.
Done
This was introduced between v2.2.0 and v2.3.0. Nevertheless, I fixed it.
I feel like anything I try to do here will be a simple guess trying to please you, as the accessibility guidelines indicate this color. I would suggest you change that to a color if you find more suitable.
Done
Because it's in the parathesis I took that more as a suggestion than a requirement. I personally feel like that is inconsitent and doesn't match the whole structure of the app. Feel free to apply that change. |
Thanks :) |
Hey folks,
I was reviewing the TodoMVC a11y features and I saw you improved colors already, but there are some more improvements possible.
This MR is improving on:
I also wrote a couple of articles in Medium about what I did: