#109109Checkbox filters in search modal cannot be navigated with arrow keys
Description
In the global search modal, the “Filter” button opens a dropdown containing multiple checkbox options. These checkboxes can currently only be focused one by one using the Tab key. Navigation within the checkbox list using the arrow keys (up/down) is not possible, which breaks common keyboard interaction patterns and does not meet accessibility requirements.
Steps to Reproduce
- Open a page that provides the global search.
- Activate the search in the top toolbar (search modal opens).
- Focus the “Filter” button in the search modal and press Enter.
- Move focus into the checkbox list (Tab key).
- Try to move between checkboxes using the Up/Down arrow keys.
Observed Behavior
Arrow keys do not move focus between the checkboxes; each checkbox must be focused individually via Tab.
Expected Behavior / Impact
Within a checkbox group, options can be focused using Up/Down arrow keys and toggled using the Space key.
Keyboard users are currently disadvantaged; the interaction is unintuitive and does not follow accessibility recommendations (including BFIT-Bund, WCAG 2.1.1 Keyboard).
- Focus moves into the group via Tab and can then be moved between the options using Up/Down arrow keys.
- The Space key toggles the checked state of the focused checkbox.
- After toggling, focus stays within the group (no unexpected focus loss).
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Files 1
History 3
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2026-04-21T11:23:51+00:00" > 04/21/26, 11:23 </span>
-
Christian Rath-Ulrich commented <span data-processor="relativetime" data-value="2026-10-21T18:48:48+00:00" > 10/21/26, 18:48 </span>
-
Benni Mack commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-11-19T13:42:09+00:00" > 11/19/26, 13:42 </span>Closing this, if Michael has a differnet opinion we’ll re-open it.
The reported behavior does not violate a WCAG success criterion. 2.1.1 Keyboard (Level A), the criterion named in the ticket, is met by the current behavior.
The filter options are native checkboxes (input type=“checkbox” with an associated label) in the live-search dropdown. Each option is its own tab stop, Space toggles the checked state, and focus stays on the checkbox. That is full keyboard operation. 2.1.1 requires operability, not a particular set of keys.
Arrow keys between options are not part of the checkbox pattern. The WAI-ARIA Authoring Practices Guide (APG) defines the checkbox keyboard interaction as:
Tab moves focus to the checkbox.
Space toggles the state.
Each checkbox is in the tab sequence (tabindex=“0”).
Arrow keys belong to composite widgets: radio groups, menus, listboxes, tabs, and grids. The APG does not list checkboxes among them. A radio group has a single tab stop, and arrow keys move between options and select one. A checkbox group is several independent controls.
The expected behavior in the ticket is that radio or composite pattern: one tab stop, then arrow keys and a roving tabindex. Applied to native checkboxes, it contradicts the APG and platform behavior. Screen-reader and keyboard users expect Tab and Space on checkboxes.
EN 301 549 clause 9.2.1.1 and the BFIT-Bund BITV test map directly onto 2.1.1. Arrow-key navigation is required there only when a widget has an ARIA role whose pattern calls for it (menu / menuitemcheckbox, listbox, radiogroup). This dropdown has none of those roles. Bootstrap deliberately omits role=“menu” on dropdowns that contain form controls.
@mte_mscr please confirm