-
Notifications
You must be signed in to change notification settings - Fork 130
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
Ensure all relevant components have a focus state #410
Comments
I went ahead and tested all components that are in the live docs to refine this issue. All components have acceptable focus states except for:
While I was there, I also tested the hover states, here's what I found:
Possible solutions for some of the cases above could also be replicating the same hover styles for focus styles. I wrote about this here: https://css-tricks.com/having-a-little-fun-with-custom-focus-styles/ Hope this was helpful, let's get to work 🚀 |
🎉 This issue has been resolved in version 2.0.0-alpha.16 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 2.0.0-beta.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Describe the bug
At the moment, not all of our components have a focus state. Here is an article describing the topic. The short summary is that this is very helpful for screen readers, people with keyboards, etc.
We should do a review of components and add focus states where necessary.
Expected behavior
Components like links, buttons, etc. should all have a focus state that is visible to the user.
The text was updated successfully, but these errors were encountered: