Remove the legacy search stack and its config flags
Open
@pringelmann is already working on this.
Since Jun 29, 2026.
1. to develop
accessibility
feature: search
technical debt
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Legacy is the accessibility fallback, so it goes only once the new search has an independent a11y signoff. In practice that means graduating unified search out from behind the enable_non-accessible_features switch. Decide the two legacy-only behaviours first: enableLiveSearch (type-then-Enter) and the in:/- inline filter syntax.
- BITV / WCAG 2.1 AA sign-off obtained for the new search
-
enableLiveSearch+ inline-filter-syntax carry-or-drop decision recorded - legacy view files + bundle + webpack entry removed
-
unified_search.enabled/enable_non-accessible_featuresgate removed - Finish the combobox ARIA once
NcListItemsupports it upstream: addaria-selectedto the active option andtabindex="-1"on result anchors so Tab goes input. - Verify with NVDA + VoiceOver that the active row and its group are announced, since one combobox's
aria-activedescendantspans several per-providerrole="listbox".
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.