Open maggiewachs opened 2 months ago
A ticket in Jira was created.
Part of the hold off on implementing these changes revolves around the potential for a Tab refactor.
Outstanding issues with the current Tab implementation:
<a href="#foo">Tab 1</a>
) that doesn't actually use the History API. For instance, navigating to www.thisisalink.com/#tab2 should take a user to a view of www.thisisalink.com where the 2nd tab is active. This does not work.
This is really a usability improvement or enhancement, less so a bug :)
Describe the bug The tab component's implementation of keyboard support is somewhat non-standard:
To Reproduce Steps to reproduce the behavior:
Expected behavior Use a managed focus pattern for the tabs component, where the user can Tab key to the tab list and then use arrows to make a selection. The method for selection should probably be either auto-selection (as it does now with arrow keys) or manual selection (Enter or Space bar to choose a tab). Once a tab is selected, the next Tab key moves focus to the selected content; shift+Tab then moves focus back up to the tab list. Example: https://www.w3.org/WAI/ARIA/apg/patterns/tabs/examples/tabs-manual/
Desktop (please complete the following information):
Additional context It would probably help to include interactive elements in the tab examples, too, to show how focus moves.