Details
-
Bug
-
Resolution: Cannot Reproduce
-
Low
-
None
-
9.7.0
-
9.07
-
Severity 3 - Minor
-
Description
Issue Summary
On the “Backlog” page, the focus does not return to the element that triggered the content when the new content is closed.
Steps to Reproduce
- Navigate onto the mentioned page.
- Navigate onto the "Issue Key: SCRUM-10", "Issue Key: SCRUM-17 Issue with status done", "Issue Key: SCRUM-14", and so on, links and activate any of them.
- Observe that a new content gets opened.
- Using just a keyboard, dismiss the new content by activating the “Close details” button.
- Observe that the focus does not return to the elements that triggered the content.
Actual Results
When the “Close details” button is activated to close the new content, the focus does not return onto the triggering link. It instead moves at the top of the page. This illogical focus order might make the page difficult to understand for the keyboard and screen reader users.
Expected Results
Make sure that the focus returns to the element that triggered the content. Make sure that when the user dismisses the new content, the focus returns onto the triggering elements. This can be done with the “focus” method. For similar examples, please refer “https://developer.mozilla.org/en-US/docs/Web/API/HTMLOrForeignElement/focus”
Screen Recording
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 Monterey Version 12.4
Chrome - Version 103.0.5060.134 (Official Build) (arm64)
Firefox- Version 93.0 (32-bit)
Safari- Version 15.5 (17613.2.7.1.8)
JAWS- Version 2022
NVDA- Version 2020.3
Voiceover - Version Latest