Issue Summary

After closing the non-modal dialog, the keyboard focus does not return to the triggering element.

Steps to Reproduce

1. Open the "Scrum board" page.
2. Navigate to the issue links and activate it
3. Observe that a non-modal dialog will appear.
4. Close the dialog using an Esc key or activate the "Close" button and try to navigate further.
5. Observe that the focus moves to the beginning of the page 

Screen Recording

Screen Recording 2024-02-05 at 6.49.07 PM.mov

Screenshot

Actual Results

On closing the non-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 to [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