Issue Bug Closed

#91645Incorrect keyboard focus order in tab menus

Elisabeth Zeilinger 06/15/20, 09:16 updated 12/02/25, 14:36

Description

When you have a tab menu, e.g. with the modal “Create new content element”, you see a tab menu with “Typical page content”, “Form elements”, “Menu”, etc.
The tab order for this component ist incorrect. First you tab through the tab menu, then you tab through the content of the focussed tab.
Correct would be: when focussing a tab menu, the next focusable element should be the content of this tab. Navigating through the tab menu should work with arrow keys.

*The following keyboard rules should be implemented for tab menus:*
- Tab: When focus moves into the tab list, places focus on the active tab element. When the tab list contains the focus, moves focus to the next element in the page tab sequence outside the tablist, which is typically either the first focusable element inside the tab panel or the tab panel itself.

When focus is on a tab element in a horizontal tab list:
- Left Arrow: moves focus to the previous tab. If focus is on the first tab, moves focus to the last tab. Optionally, activates the newly focused tab (See note below).
- Right Arrow: Moves focus to the next tab. If focus is on the last tab element, moves focus to the first tab. Optionally, activates the newly focused tab (See note below).

When focus is on a tab in a tablist with either horizontal or vertical orientation:
- Space or Enter: Activates the tab if it was not activated automatically on focus.
- Home (Optional): Moves focus to the first tab. Optionally, activates the newly focused tab (See note below).
- End (Optional): Moves focus to the last tab. Optionally, activates the newly focused tab (See note below).

See implementation example here:
https://www.w3.org/TR/wai-aria-practices/examples/tabs/tabs-2/tabs.html

Reviews 2

Files 1

History 915

  1. Gerrit Code Review pushed patch set 1 for main to change 90096 status Accepted Under Review <span data-processor="relativetime" data-value="2025-07-18T12:41:36+00:00" > 07/18/25, 12:41 </span>

  2. Andreas Nedbal commented <span data-processor="relativetime" data-value="2025-07-18T12:54:33+00:00" > 07/18/25, 12:54 </span>

    I have fixed this behavior in the above patch, I have some things that are not perfectly clear to me however:
    • I currently added support for both left/up and right/down moving the focus in the navigation. I’m not sure if the directional navigation should follow what’s visible (top-down) or just left and right for previous and next.
    • If we go for left and right as directional keys, I probably need to implement inverse navigation for RTL systems, right?

    Design-wise the active state of the navigation button is also sub-optimal, it’s not discernible that we entered tab-state in the navigation, and we only notice once we use the directional keys that we’re inside it.

  3. Andreas Nedbal commented <span data-processor="relativetime" data-value="2025-07-18T14:13:29+00:00" > 07/18/25, 14:13 </span>

    I consulted someone with deeper knowledge into WCAG Patterns and got my answers. I also got referred to the Tabs pattern documentation: https://www.w3.org/WAI/ARIA/apg/patterns/tabs/

    Following things are done now:

    • I now specify aria-orientation as vertical explicitly to denote direction of navigation and only use up/down directional arrow keys.
    • The tab toggles now have role="tab" as well as aria-selected
    • If the menu is displayed (a new case for this is the Form element selection, where the menu is not shown) the content area is properly denoted as role="tabpanel"
    • Navigating with the arrow keys between the navigation item now also directly toggles them, following the recommendation of the Tabs pattern.
  4. Andreas Nedbal commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2025-09-11T15:10:10+00:00" > 09/11/25, 15:10 </span>

    Applied in changeset commit:a39d7ec8b85aad46d44cbe00a20f78822b6cf328.