Issue Summary

The keyboard focus is not set programmatically on the "Linked pages" non-modal dialog.

Steps to Reproduce

1. Open the Jira DC instance.
2. In the header section, navigate to the "Projects" button, expand it, and open any project.
3. In the sidebar navigation, go to the "Backlog" link and activate it.
4. Using a screen reader or only keyboard, navigate to the "View linked pages" button and activate it.
5. Try to navigate through the dialog content and observe that the keyboard focus is not set to the dialog.

Screen Recording

Focus bug.mp4

Actual Results

When users activate the "View linked pages" button, a "Linked pages" non-modal dialog appears on the page. However, the keyboard focus is not set on the dialog; instead, the focus moves to the top of the page. Although the dialog is visible on the screen after the button, its content is placed at the end of the page. As a result, screen reader users and keyboard-only users are required to tab through all page content before they can interact with the dialog.

Expected Results

The programmatic focus should be set on the first logical element of the dialog as soon as the dialog appears.

In this case, the keyboard focus should move to the first logical element, such as the "Linked pages" heading of the non-modal dialog.

Apply the following changes:

• Add tabindex="-1" to the <h2> element containing the "Linked pages" heading.
• Set the focus to the heading using the JavaScript .focus() method.

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 Sequoia 15.6
Operations - Windows11
Chrome - Version 140.0.7339.128 (Official Build) (64-bit)
Safari- Version 18.6
JAWS- Version 2023
NVDA- Version 2025.3
VoiceOver - Version Latest