-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 9.5.1
-
Component/s: Accessibility
-
Severity 3 - Minor
Issue Summary
The main region is defined two times programmatically which is not a best practice as per the WCAG SC.
Steps to Reproduce
- Open the home page.
- Go to projects and select any one from the table.
- Select any one repository.
- Go to side navigation and activate the "Create pull request" link.
- Inspect the code and verify that landmark is defined incorrectly.
Screenshot
Actual Results
The main landmark is defined using <section role="main"...> and <main> elements on the page. This will create confusion for screen reader users.
As a result, screen reader users might not be able to identify the exact main region and navigate between different regions quickly.
Expected Results
Remove role "main" from the <section> element as it also includes "side navigation". Keep the <main> element and we can remove the role "main" from that as we are already using the native elements which is sufficient enough.
Code Snippet
<main id="main" class="aui-page-panel-content"> (...) </main>
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 Sequoia Version 15.2 (24C101)
Chrome - Version 131.0.6778.266 (Official Build) (arm64)
Firefox- Version 112.0.1 (64-bit)
Safari- Version 18.2 (20620.1.16.11.8)
JAWS- Version 2023
NVDA- Version 2020.3