The Hub currently isn't keyboard navigable: the nav-buttons aren't in the tabindex so navigation is impossible. This can be worked around somewhat by using search (ctrl + shift + P but see also #224) but that prevents users from getting a topic listing once they've navigated away from the top level.
Besides this, many elements that are in the tabindex currently don't have a focus outline or any other kind of focus styling, making it impossible to determine which UI element is currently focused.
Keyboard navigation is a requirement to bring the documentation to a wider audience that can't rely on mouse or touch navigation.
The Hub currently isn't keyboard navigable: the
nav-button
s aren't in the tabindex so navigation is impossible. This can be worked around somewhat by using search (ctrl + shift + P but see also #224) but that prevents users from getting a topic listing once they've navigated away from the top level.Besides this, many elements that are in the tabindex currently don't have a focus outline or any other kind of focus styling, making it impossible to determine which UI element is currently focused.
Keyboard navigation is a requirement to bring the documentation to a wider audience that can't rely on mouse or touch navigation.