-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
8.20.30, 9.12.2, 9.4.17
-
- 2.4.1
- 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
- ril
- wcag21
-
8.2
-
Severity 3 - Minor
-
Issue Summary
On the “Accessibility Assessment | Dependencies Report ” page, the main landmark region is not defined.
Steps to Reproduce
- Open the "Accessibility Assessment | Dependencies Report" page.
- Inspect the code and notice that the no <main> landmark is defined on the page neither any HTML element is provided with role="main" for the main content area.
Screenshot
Actual Results
Programmatic access to the main section of the web page is not used. This resulted in screen readers not being able to orient themselves to the page and navigate easily to the main section of the page.
Expected Results
Every page must have a main landmark specified. Content present in the main region of the 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.
Follow this link !https://www.w3.org/favicon.ico!Landmark Regions for more understanding.
Code snippet
<main>..main content area..</main>
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
