-
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
-
1
-
Severity 3 - Minor
Issue Summary
The text elements such as "4 issues without team”, and "Blocks" are not defined using heading markup.
Steps to Reproduce
- Open the "Accessibility Assessment | Dependencies Report" page.
- Navigate and activate the "Rollup to" button.
- Navigate and select the "Team" option.
- Navigate to the mentioned instance.
- Inspect the code and observe that the text is not marked up using an HTML heading.
Screenshot 1

Screenshot 2

Screenshot 3

Actual Results
The "4 issues without team” text (available by selecting "Team" options from the "Rollup to" expand/collapse button ), "Demo 1" text, and "Blocks" text present within the "Blocks" non-modal dialog (available by activating the "Blocks", and "Blocks about 1 - month" buttons), are not semantically declared as heading. As a result, screen reader users found it difficult to understand the page content structure.
Expected Results
When any element titles or categorizes any content, it should semantically be declared as a heading. Mark up the "4 issues without team”, and "Blocks" texts using <h2> markup and "Demo 1" text using <h1> markup.
Make sure that the heading levels correctly communicate the page's structure, such as the parent-child relationship between the headings.
Code Snippet
<h1>demo1<h1>
(...)
<h2 class="_60kYZ">4 issues without team</h2>
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