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
Since we're not displaying the actual input field, but rather treating its label as the input, the obvious solution would be to add a tabIndex to the label. This would work, but comes with its own set of issues - on its own, that change would trip up the no-noninteractive-tabindex rule. This could be solved by giving the label a role (say, button), but would then cause another issue by tripping the no-noninteractive-element-to-interactive-role rule. To be honest, I'm not sure the best way to deal with this off hand.
Describe the bug
RadioInput fails to be placed within tab order, making it inaccessible for screen readers
Input options should also have a focus state
Expected behavior
I expect the thing to bloody work with tab controls
Steps to reproduce
Additional Information (optional)
No response
FuelRats IRC Nickname (optional)
No response
The text was updated successfully, but these errors were encountered: