-
Bug
-
Resolution: Fixed
-
Low
-
8.4.0, 9.2.0
-
- 4.1.2
- Level-A
- WCAG21
- ax-A11y-251
- ax-Confluence-dc-2024-vpat-sidenavigation
- ax-bug
- ax-confluence-dc-2023-vpat
- ax-confluence-dc-2024-vpat
- ax-confluence-dc-2024-vpat-reuse
- ax-confluence-dc-vpat
- ax-confluence-dc-vpat-pg14
- ax-confluence-dc-vpat-reuse
- ax-confluence-dc-vpat-sidenavigation
- ax-medium-priority
- ax-qa
- internal-kickoff
-
Severity 3 - Minor
-
Issue Summary
The side navigation landmark does not have a programmatically defined accessible name.
Steps to Reproduce
- Navigate onto the mentioned page.
- Navigate onto the mentioned landmark and inspect its code.
- Observe that the landmark does not have a programmatically defined accessible name.
Screenshot
Actual Results
The "Side" navigation landmark does not have a programmatically defined accessible name.
As a result, users of assistive technologies will not be able to understand the purpose of the landmark.
Expected Results
Elements must have programmatically defined accessible names so that their purpose is communicated to assistive technology users. In this scenario, use aria-label attribute to provide an accessible name for the landmark. Make sure that the accessible name signposts the purpose of the landmark.
Note (1): Before implementing any accessible name, kindly contact the content design team.
Note (2): We would suggest you to please change the name of the primary landmark from "Site" to "Primary" to maintain consistency across all Atlassian products.
Code Snippet
<nav aria-label="Side"> ... </nav>
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 Ventura 13.3.1
Chrome - Version 113.0.5672.63 (Official Build) (x86_64)
Firefox- Version 92.0 (64-bit)
Safari- Version 16.4 (18615.1.26.110.1)
JAWS- Version 2023
NVDA- Version 2023.3
Voiceover - Version Latest
- is resolved by
-
A11Y-348 Loading...