Issue Summary
After activating the “Sort“ button, the keyboard focus moves to the another interactive element on the page.
Steps to Reproduce
- Open "JSM System Dashboard" page.
- Navigate to the "Projects" in the header section and choose any ITSM project from the options.
- Navigate to the "Raise a request" link in the side navigation and activate it.
- Navigate to the "Requests" in header and select the "Approvals" option.
- Navigate and activate the "Sort" button in the table header.
- Observe that the keyboard focus moves to the "Search for requests" input field.
Screen Recording
Screen Recording 2024-12-13 at 11.21.04 AM.mov
Actual Results
When the user activates the “Sort“ button of the "Reference" and "Requester" table headers in the main content area of the page, the focus moves inappropriately to the "Search for requests" input field on the page instead of staying the keyboard focus on the sort button itself.
As a result, keyboard-only and screen reader users will have to navigate the screen content again before accessing the content after the triggering button.
Expected Results
When the user activates the Sort button, the keyboard focus should remain on the Sort button itself so that the user won’t have to tab-pass the content again on the page.
Ensure that the keyboard focus does not moves any other interactive element which can be achieved via the JavaScript focus() method.
For more information, refer to the following link: [HTMLElement: focus() method - Web APIs | MDN|https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/focus]
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.
Environment
MacBook Pro (16-inch, 2021)
macOs Sonoma 15.1.1
Chrome - Version 131.0.6778.109 (Official Build) (arm64)
Firefox- Version 92.0 (64-bit)
Safari- Version 17.6 (19618.3.11.11.5)
JAWS- Version 2023
NVDA- Version 2021.2
Voiceover - Version Latest
Bug
Low
A11Y-592 You do not have permission to view this issue
