-
Bug
-
Resolution: Fixed
-
High
-
None
-
CCMA - 3.10.3
-
Severity 3 - Minor
-
Accessibility
Issue Summary
The keyboard focus is not set onto the modal dialog.
Steps to Reproduce
- Open the Confluence instance.
- Navigate to the site navigation and activate the "Administration" control.
- Navigate to "General configuration" and activate it.
- Navigate to "Migration Assistant" and activate it to open the migration assistant.
- Using a screen reader or keyboard, activate the "Begin Assessing/View app assessment" and "Begin Preparing" buttons to open a modal.
- Use the "Down Arrow" or "Tab" key to navigate through the dialog content.
- Observe that focus is not set onto the dialog.
Screen Recording 1:
Screen Recording 2:
https://jira.atlassian.com/secure/attachment/471119/Screen%20Recording2.mkv
Actual Results
When users activate the "Begin Assessing/View App Assessment" and "Begin preparing" buttons, the programmatic focus is not set on the "Assess Your Apps" and "Connect to Cloud" modals. Instead, the focus moves incorrectly elsewhere on the page.
Although the modal dialog is visible at the center of the screen, its content is positioned at the end of the page for keyboard-only and screen reader users. This forces screen reader and keyboard-only users to tab through the page’s content before they can interact with the modal dialog.
Expected Results
The programmatic focus should be set on the first logical element of the dialog as soon as it appears.
Set the keyboard focus to the first logical element of the modal dialog using JavaScript's .focus() method.
For information on creating accessible modal dialogs, refer to:
https://www.w3.org/WAI/ARIA/apg/example-index/dialog-modal/dialog.html
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 Sonoma 14.7
Operations - Windows11
Chrome - Version 131.0.6778.70 (Official Build) (64-bit)
Safari- Version 18.0
Firefox- Version 131.0.3 (64-bit)
JAWS- Version 2023
NVDA- Version 2024.4
VoiceOver - Version Latest
The issue seems to be resolved in the latest version of CCMA
The video link of the behavior in the latest version of CCMA: https://stage.loom.com/share/10ba21bfb0ac478d9af9748e3e2638ed?sid=25df01b0-573f-4b0e-ac53-f1bf2e3f511e