-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
9.12.2
-
9.12
-
Severity 3 - Minor
-
Issue Summary
After closing the "Operations" modal dialog, the keyboard focus does not return to the triggering element.
Steps to Reproduce
- Open the "Backlog" page.
- Navigate to any "issue" present in the backlog and select it.
- Navigate to the "More actions" button and press the "." key.
- Observe that the "Operation" modal dialog will appear.
- Close the dialog using an Esc key or activate the "Close" button and try to navigate further.
- Observe that the focus moves to the beginning of the page.
Screen Recording
Screen Recording 2024-02-19 at 3.20.49 PM.mov
Screenshot
Actual Results
On closing the modal dialog, the programmatic focus does not return to the triggering element. Instead, the focus is moved to the beginning of the page.
This required screen reader users and keyboard-only users to tab-pass the content on the page before they could interact with the content after the triggering element.
Expected Results
The programmatic focus of users should be set on the triggering element of the dialog as soon as the dialog is closed.
Set the keyboard focus to the triggering element of the dialog using JavaScript .focus().
For information on creating accessible modal dialog refer Modal Dialog Example
Workaround
Currently, there is no known workaround for this behaviour. A workaround will be added here when available
Environment
MacBook Pro (16-inch, 2021)
macOs Sonoma 14.3
Chrome - Version 120.0.6099.109 (Official Build) (arm64)
Firefox- Version 92.0 (64-bit)
Safari- Version 17.3 (19617.2.4.11.8)
JAWS- Version 2023
NVDA- Version 2021.2
Voiceover - Version Latest
- is resolved by
-
A11Y-112 You do not have permission to view this issue