-
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
-
Severity 3 - Minor
Issue Summary
On the "Accessibility assessment | Roadmaps" page, The checkboxes in the "Scope" table do not have programmatically defined accessible names.
Steps to Reproduce
- Navigate onto the above mentioned page.
- Navigate onto the mentioned instances and inspect their code.
- Observe that the checkboxes do not have programmatically defined accessible names.
Screenshot
Actual Results
The checkboxes in the "Scope" table do not have programmatically defined accessible names.
As a result, users of assistive technologies will not be able to understand the purpose or the functionality associated with the form fields.
Expected Results
Interactive elements must have programmatically defined accessible names so that their functionality is communicated to assistive technology users.
In this scenario, we would recommend you to associate these checkboxes with the data in the "Issue" column. As these column has descriptive data, this would provide more context to these checkboxes. For this, specify unique IDs to both, the checkboxes, as well as the data of the "Issues" column. Reference the id attributes of both via aria-labelledby attribute respectively.
Code Snippet
<td><input aria-labelledby="a1"></td> <td id="a1"><a href="...">SCRUM-7</a>...</td>
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 Ventura 13.3.1
Chrome - Version 113.0.5672.63 (Official Build) (x86_64)
Firefox- Version 92.0 (64-bit)
Safari- Version 16.4 (18615.1.26.110.1)
JAWS- Version 2023
NVDA- Version 2023.3
Voiceover - Version Latest
- links to