-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
8.20.30, 9.12.2, 9.4.17
-
- 2.4.3
- Level-A
- accessibility
- ax-at-JAWS
- ax-at-NVDA
- ax-at-VO
- ax-at-user
- ax-bug
- ax-desktop
- ax-high-priority
- ax-jiradc-arj
- ax-jiradc-arj-vpat2024
- ax-jiradc-vpat
- ax-jiradc-vpat-accessibilityassessmentdependenciesreport
- ax-jiradc-vpat-accessibilityassessmentroadmaps
- ax-jiradc-vpat-pg10
- ax-kb-user
- ax-qa
- ril
- wcag21
-
8.2
-
Severity 3 - Minor
-
Issue Summary
When the user activates the "Locate issue in roadmap" button, the focus moves to the "Scope" input field inappropriately.
Steps to Reproduce
- Open the "Accessibility Assessment | Dependencies Report" page.
- Navigate and activate the "More actions" ("...") button.
- Navigate and activate the "Locate issue in roadmap" button.
- Observe that the focus moves to the “Scope” input field present in the "Roadmap" page.
Screen Recording
Screen Recording 2024-02-05 at 2.33.59 PM.mov
Actual Results
When the users activate the "Locate issue in roadmap" button, the focus moves to the "Scope" input field instead of moving to the first interactive element present on the "Roadmap" page.
Expected Results
When the user activates the “Locate issue in roadmap” button focus should move to the first interactive element i.e. "Hierarchy" button present in the "Roadmap" page which can be achieved via 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 (13-inch, 2018)
macOs Ventura 13.3.1
Chrome - Version 109.0.5414.119 (Official Build) (64-bit)
Firefox- Version 92.0 (64-bit)
Safari- Version 16.4 (18615.1.26.110.1)
JAWS- Version 2022
NVDA- Version 2021.2
Voiceover - Version Latest
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|