-
-
Notifications
You must be signed in to change notification settings - Fork 446
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
Tab is Not Focussed on First Click #272
Comments
Hi, does anyone mind if I work on this issue? |
I'd say go for it! It's probably a good idea to detail what the current behaviour is (since the issue is from almost a year ago — although I don't think the behaviour has changed in the mean time) and how you'd like to change it. |
hey @flurmbo, any update about this issue? |
This is still relevant. I guess there are no updates on this one. |
I am also wondering if there will be a fix for this. I think this was working properly in an earlier version of React tabs. It is considered an accessibility violation not to display a focus ring around the active tab. |
BREAKING CHANGE: The tabs are now instantly focused on click. The default styling has been adapted for that, so that there is no outline shown anymore on focus. closes #272
🎉 This issue has been resolved in version 4.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
When clicking on a tab, it is expected that focus would be placed on that tab to instantly enable keyboard navigation. Currently this does not occur until the second click, or by pressing tab.
It is also worth noting that WAI-ARIA recommends handling roving tabindex like this: https://www.w3.org/TR/wai-aria-practices/#kbd_roving_tabindex
The text was updated successfully, but these errors were encountered: