-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
None
-
Affects Version/s: 8.20.30, 9.4.17, 9.12.2
-
Component/s: (Advanced Roadmaps) Accessibility
-
8.2
-
Severity 2 - Major
Issue Summary
On the "Accessibility Assessment - Roadmaps" page the main landmark is not defined on the page.
Steps to Reproduce
- Open the "Accessibility Assessment - Roadmaps" page.
- Inspect the code of the page.
- Verify that the main landmark is not defined on the page.
Screen Recording
Screen Recording 2024-01-29 at 12.54.41 PM.mov
Actual Results
The main landmark regions is not defined programmatically on the page.
As a result, screen reader users might not be able to identify the main region and navigate between different regions quickly.
Expected Results
Screen reader users should be able to identify each landmark region as well as navigate to different regions on the page.
Every page must have a main landmark specified. Content present in main region of page should be encapsulated under <main> </main> tags OR role=”main” can be provided to the parent <div> element containing the main content so that screen reader users can easily jump to the main landmark or may skip the main section if needed.
Apply the following change:
• Provide main landmark region for the respective page.
Use the following to define the landmark: !https://www.w3.org/favicon.ico!Landmark Regions
code snippet
<div role="main">
<!-- Main content goes here -->
...
</div>
Workaround
Currently, there is no known workaround for this behaviour. 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