Issue Summary

The programmatic focus is not moved to the "Inline comment thread" non-modal dialog.

Steps to Reproduce

1. Open the Confluence Cloud Homepage.
2. From the Sidebar navigation, expand Spaces and open any space.
3. Open a page that contains inline comments.
4. Using a screen reader or only the keyboard, activate the "Comment 1" button to open the dialog.
5. Try to navigate through the dialog content.
6. Observe that focus is not set onto the dialog.

Screen Recording

Inline comment thread issue

Actual Results

When users activate the "Comment 1", "Comment 2", or "Comment 3" buttons to open the "Inline Comment Thread" non-modal dialog, programmatic focus does not move to the dialog; instead, it remains on the triggering element. Although the dialog appears after the triggering element visually, its content is available earlier in the page structure. As a result, screen reader and keyboard-only users must tab through the 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 it appears.

Set keyboard focus to the first logical element, such as the "Previous comment" button, using JavaScript’s .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 Tahoe 26.2
Operations - Windows11
Chrome - Version 144.0.7559.133 (Official Build) (64-bit)
Safari- Version 26.2
JAWS- Version 2023
NVDA- Version 2025.3.2
VoiceOver - Version Latest