-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
None
-
Affects Version/s: 8.20.30, 9.4.17, 9.12.2
-
Component/s: (Advanced Roadmaps) Accessibility
-
- 2.4.1
- Level-A
- WCAG2.1
- a11y-triaged
- 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-accessibilityassessmentreleases
- ax-jiradc-vpat-accessibilityassessmentroadmaps
- ax-jiradc-vpat-pg05
- ax-macos-safari
- ax-qa
- ril
-
8.2
-
Severity 3 - Minor
Issue Summary
The main landmark region is not defined on Accessibility Assessment - Releases page
Steps to Reproduce
- Open the "Accessibility Assessment - Releases" page.
- Using screen reader, pull the list of landmarks
- Notice that the <main> element is not defined on the page.
Screenshot

Actual Results
The main landmark region is not defined on the Accessibility Assessment - Releases page.
As a result, screen reader users might find it difficult to navigate to different sections of the page quickly.
Expected Results
Every page must have a main landmark specified.The content present in the main region of the page should be encapsulated under the <main> </main> tags OR role="main" can be provided to the parent <div> element containing the main content so that screen reader users can quickly jump to the main landmark or may skip the main section if needed.
For more details visit https://www.w3.org/WAI/GL/wiki/Using_ARIA_landmarks_to_identify_regions_of_a_page
Workaround
Required, if there is no workaround please state:
Currently there is no known workaround for this behavior. A workaround will be added here when available
Environment
MacBook Pro (16-inch, 2021)
macOs Monterey Version 12.3.1
Chrome - Version 101.0.4606.81 (Official Build) (64-bit)
Firefox- Version 93.0 (32-bit)
Safari- Version 15.3 (17612.4.9.1.5)
JAWS- Version 2022
NVDA- Version 2020.3
Voiceover - Version Latest
- links to