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
In the above animation, I've started out with focus on the search input. I then tab forward and backward through the interactive elements in this UI. For forward tab order is:
Input
First list item
Anchor tag within the the first list item
Anchor tag within the the second list item
Backward tab order is:
Anchor tag within the the second list item
Anchor tag within the the first list item
"Add new visualization" button
Input
Ideally, the forward tab order shouldn't contain redundant/confusing selections (e.g. both the list item and the anchor within it), and the backward tab order should be the simple reverse of the forward tab order:
Input
"Add new visualization" button
Anchor tag within the the first list item
Anchor tag within the the second list item
We can probably address this by removing the keyboard-accessibility logic identified in #12483, and simply relying upon the default browser-defined tab order.
The text was updated successfully, but these errors were encountered:
@timroes Just CC'ing you on this because I know you're very interested in creating intuitive navigation with complex components like these. Feel free to review the code and chime in if you think it's worth refactoring and debugging it. Personally, I think it's OK to remove it and use the default tabbing behavior for now, and then implementing custom keyboard navigation later in a cleaner/reusable fashion.
I would agree with @cjcenizal that it might be the best solution for now to return to regular tab order and have a discussion how we want to handle all that kind of lists accessibility and usability wise (and implement this in a reusable component in the end).
In the above animation, I've started out with focus on the search input. I then tab forward and backward through the interactive elements in this UI. For forward tab order is:
Backward tab order is:
Ideally, the forward tab order shouldn't contain redundant/confusing selections (e.g. both the list item and the anchor within it), and the backward tab order should be the simple reverse of the forward tab order:
We can probably address this by removing the keyboard-accessibility logic identified in #12483, and simply relying upon the default browser-defined tab order.
The text was updated successfully, but these errors were encountered: