-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
None
-
Affects Version/s: 8.20.30, 9.4.17, 9.12.2
-
Component/s: (Advanced Roadmaps) Accessibility
-
- 4.1.2
- Level-A
- a11y-triaged
- 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-qa
- batman-frontend-triaged
- ril
- wcag21
-
8.2
-
Severity 3 - Minor
Issue Summary
The role is not defined for the interactive elements such as "Locate issues in roadmap", and "Filter by this issue" available by activating the "More actions" ("...") expand/collapse button.
Steps to Reproduce
- Open the "Accessibility Assessment | Dependencies Report" page.
- Navigate and activate the "more actions" ("...") expand/collapse button.
- Navigate to the mentioned instance.
- Inspect the code and observe that the role is not defined.
Screenshot

Actual Results
When the user navigates onto the interactive elements such as "Locate issues in roadmap", and "Filter by this issue", using the keyboard it does not expose the type of control. This is because the role is not defined for the mentioned interactive elements.
This made it difficult for screen reader users to access the functionality associated with it.
Expected Results
An appropriate role must be announced with a screen reader for the interactive elements.
Ensure that the interactive elements are programmatically identified as buttons.
Apply the following changes:
Native implementation:
- Code the mentioned interactive elements using the native <button> element.
ARIA Implementation:
- Provide role="button" for the <div> element of the mentioned interactive elements.
- Remove the aria-hidden attribute from the <div> element of the mentioned interactive elements.
- Modify the scripts to ensure the mentioned interactive elements are keyboard-operable.
Code Snippet
<button data-testid="portfolio-3-portfolio.app-simple-plans.main.tabs.dependencies.issue.meatballs-menu.find-issue-SCEN-7cc3b73a-fa11-4208-807d-ca2075e451ff-in-roadmap"> (...) <span class="ItemParts__Content-sc-14xek3m-5 jRBaLt">Locate issue in roadmap</span> </button>
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