-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
8.20.30, 9.12.2, 9.4.17
-
8.2
-
Severity 3 - Minor
-
Issue Summary
Missing list markup for texts such as "SCRUM-1 Heading Missing", "SCRUM Missing list mark-up", and so on, present in the main content.
Steps to Reproduce
- Open the "Accessibility Assessment | Dependencies Report" page.
- Navigate and select the "Team" option from the "Rollup to" expand/collapse button.
- Navigate to the mentioned instance.
- Inspect the code and observe that these elements do not use unordered list semantics.
Screenshot
Actual Results
The "SCRUM-1 Heading Missing", "SCRUM Missing list markup", and so on, texts visually look like a list for which list markup is missing.
As a result, it will be a bad user experience for screen reader users.
Without list markup in the HTML, assistive technologies cannot provide shortcuts that allow users to navigate the lists quickly. Screen readers will not be able to announce the number of lists in the item or other supporting information.
Expected Results
Mark the mentioned texts with <ul> and <li> elements as unordered list markup. This helps users to navigate and interpret the information effectively.
Code Snippet
<ul class="_2pGvv"> <li class="_27fal"> (...) <a href="/browse/SCRUM-1" target="_blank" rel="noopener noreferrer">SCRUM-1</a> <div class="LmYvM" title="Heading Missing">Heading Missing</div> </li> (...) </ul>
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
[JSWSERVER-25585] Accessibility Assessment | Dependencies Report : Missing unordered list semantics
Labels | Original: 1.3.1 Level-A 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 wcag21 | New: 1.3.1 Level-A 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 |
Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 963666 ] |
Priority | Original: High [ 2 ] | New: Medium [ 3 ] |
Introduced in Version | Original: 9.12 | New: 8.2 |
Affects Version/s | New: 8.20.30 [ 106364 ] | |
Affects Version/s | New: 9.4.17 [ 106909 ] |
Labels | Original: 1.3.1 Level-A accessibility ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-desktop ax-high-priority ax-jiradc-vpat ax-jiradc-vpat-accessibilityassessmentdependenciesreport ax-jiradc-vpat-accessibilityassessmentroadmaps ax-jiradc-vpat-pg10 ax-qa wcag21 | New: 1.3.1 Level-A 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 wcag21 |
Component/s | Original: Accessibility [ 62491 ] | |
Component/s | Original: (Advanced Roadmaps) Other [ 73719 ] | |
Component/s | New: (Advanced Roadmaps) Accessibility [ 74392 ] |
Status | Original: Needs Triage [ 10030 ] | New: Ready for Development [ 10049 ] |
Labels | Original: 1.3.1 Level-A accessibility ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-desktop ax-high-priority ax-jiradc-vpat ax-jiradc-vpat-accessibilityassessmentdependenciesreport ax-jiradc-vpat-pg10 ax-qa wcag21 | New: 1.3.1 Level-A accessibility ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-desktop ax-high-priority ax-jiradc-vpat ax-jiradc-vpat-accessibilityassessmentdependenciesreport ax-jiradc-vpat-accessibilityassessmentroadmaps ax-jiradc-vpat-pg10 ax-qa wcag21 |
Description |
Original:
h3. Issue Summary
Missing list markup for texts such as "SCRUM-1 Heading Missing", "SCRUM Missing list mark-up", and so on, present in the main content. h3. Steps to Reproduce # Open the "Accessibility Assessment | Dependencies Report" page. # Navigate and select the "Team" option from the "Rollup to" expand/collapse button. # Navigate to the mentioned instance. # Inspect the code and observe that these elements do not use unordered list semantics. h3. Screenshot !Screenshot 2024-02-05 at 9.52.11 AM.png|width=555,height=320! h3. Actual Results The "SCRUM-1 Heading Missing", "SCRUM Missing list markup", and so on, texts visually look like a list for which list markup is missing. As a result, it will be a bad user experience for screen reader users. Without list markup in the HTML, assistive technologies cannot provide shortcuts that allow users to navigate the lists quickly. Screen readers will not be able to announce the number of lists in the item or other supporting information. h3. Expected Results Mark the mentioned texts with <li> elements as unordered list markup. This helps users to navigate and interpret the information effectively. h3. Code Snippet {code:java} <ul class="_2pGvv"> <li class="_27fal"> (...) <a href="/browse/SCRUM-1" target="_blank" rel="noopener noreferrer">SCRUM-1</a> <div class="LmYvM" title="Heading Missing">Heading Missing</div> </li> (...) </ul> {code} h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available h3. 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 |
New:
h3. Issue Summary
Missing list markup for texts such as "SCRUM-1 Heading Missing", "SCRUM Missing list mark-up", and so on, present in the main content. h3. Steps to Reproduce # Open the "Accessibility Assessment | Dependencies Report" page. # Navigate and select the "Team" option from the "Rollup to" expand/collapse button. # Navigate to the mentioned instance. # Inspect the code and observe that these elements do not use unordered list semantics. h3. Screenshot !Screenshot 2024-02-05 at 9.52.11 AM.png|width=555,height=320! h3. Actual Results The "SCRUM-1 Heading Missing", "SCRUM Missing list markup", and so on, texts visually look like a list for which list markup is missing. As a result, it will be a bad user experience for screen reader users. Without list markup in the HTML, assistive technologies cannot provide shortcuts that allow users to navigate the lists quickly. Screen readers will not be able to announce the number of lists in the item or other supporting information. h3. Expected Results Mark the mentioned texts with <ul> and <li> elements as unordered list markup. This helps users to navigate and interpret the information effectively. h3. Code Snippet {code:java} <ul class="_2pGvv"> <li class="_27fal"> (...) <a href="/browse/SCRUM-1" target="_blank" rel="noopener noreferrer">SCRUM-1</a> <div class="LmYvM" title="Heading Missing">Heading Missing</div> </li> (...) </ul> {code} h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available h3. 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 |
Component/s | New: (Advanced Roadmaps) Other [ 73719 ] |