-
Bug
-
Resolution: Done
-
High
-
9.1.0
-
- 4.1.2
- AXSR-38
- Accessibility
- Level-A
- WCAG21
- ax-at-JAWS
- ax-at-NVDA
- ax-at-VO
- ax-at-user
- ax-bug
- ax-critical
- ax-critical-priority
- ax-customer-escalated
- ax-dev-ready
- ax-esc-oracle
- ax-high-priority
- ax-jira
- ax-jiradc-header
- ax-macos-safari
- ax-platform-dc
- ax-qa
- ax-qa-prioritised
- ax-qa-verified
- ax-windows-chrome
-
9.01
-
1
-
Severity 3 - Minor
-
1
-
Issue Summary
The menu Dashboard/Projects/Issues etc present in the header region has no role=menubar.
Steps to Reproduce
- In the Jira header, keep the screen reader on and navigate to the links such as "Dashboard", "Issues", "Projects" etc.
- Observe role has not been rendered to the screen reader users.
Actual Results
While navigating in the header region of the Jira with the screen reader turned on, the navigation links such as Dashboard/Projects/Issues etc are announced as links which are inappropriate. As a result, the screen reader users will not be able to understand the navigational functionality effectively.
Expected Results
When the screen reader users navigate in the header region, the menubar and its menuitems should be exposed to the screen reader users.
Menu items with submenus are not links and must be excluded from list of links.
- Provide role="menubar" in the <ul> element for the navigation links.
- Provide role="menuitems" in the <li> element for the links.
Refer to the following example of the navigation menubar.
https://www.w3.org/WAI/ARIA/apg/example-index/menubar/menubar-navigation.html
Screenshot:
Screen Recording:
Screen Recording 2022-08-12 at 2.53.24 PM.mov
Workaround
Currently, there is no known workaround for this behaviour. A workaround will be added here when available
- mentioned in
-
Page Loading...
- resolves
-
GHS-248235 Loading...