-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
5.11.0
-
Severity 3 - Minor
-
Issue Summary
The <main> landmark region is not defined on the “View incidents” page.
Steps to Reproduce
- Open the "View incidents" page
- Using a screen reader, navigate to the main content.
- Observe that the <main> element is not defined on the page.
Screenshot
Actual Results
The main landmark region is not defined programmatically on the page. Programmatic access to the main section of the web page is missing
As a result, screen reader users might not be able to identify this region and navigate between different regions quickly.
Expected Results
Apply the following changes:
Every page must have a main landmark specified. The 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.
- Provide the main landmark region for the respective section of the page.
- Provide navigation landmark regions with an appropriate accessible label as well.
Use the following to define the landmark: !https://www.w3.org/favicon.ico!Landmark Regions
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
Environment
MacBook Pro (14-inch, 2021)
macOs Ventura 13.4
Chrome - Version 114.0.5735.106 (Official Build) (arm64)
Firefox- Version 112.0. 1
Safari- Version 16.5 (18615.2.9.11.4)
JAWS- Version 2023
NVDA- Version 2023
Voiceover - Version Latest
- links to
- mentioned in
-
Page Failed to load