You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.
You can see that on the demo page: one can navigate using the arrow keys, but it's impossible to select a disabled button. As a consequence, the user can't select option 4, except by going to option 1 and then pressing the Left arrow key.
Which leaves me to wonder, if an option is surrounded by disabled options, would it be at all possible to select it using the keyboard?
This affects Chrome, Safari and Firefox.
The text was updated successfully, but these errors were encountered:
You are not supposed to be able to navigate to a disabled input with the keyboard. If you couldn't get to the fourth radio button in a group like that, it was a bug. But the third one should never receive focus.
Correct! I needed to read that again. If a radio button is surrounded by disabled inputs it should be selectable, because it isn't disabled. Although that would be a confusing user experience that I hope wouldn't happen in the wild.
the arrow key should skip the button 3 and auto-select button 4
That's what I meant indeed, thanks for fixing my broken english! The point is that a disabled radio button breaks the navigation using the arrow keys, which it shouldn't do IMO.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
You can see that on the demo page: one can navigate using the arrow keys, but it's impossible to select a disabled button. As a consequence, the user can't select option 4, except by going to option 1 and then pressing the Left arrow key.
Which leaves me to wonder, if an option is surrounded by disabled options, would it be at all possible to select it using the keyboard?
This affects Chrome, Safari and Firefox.
The text was updated successfully, but these errors were encountered: