-
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
On the "Accessibility assessment | Roadmaps" page, the "Start" and "End" input fields in the "Filter" are not explicitly associated with their visual label.
Steps to Reproduce
- Navigate onto the above mentioned page.
- Navigate to the "Custom" button in the "Filter" section and activate it.
- Navigate onto the mentioned form fields and inspect the code.
- Observe that the form fields are not programmatically associated with their visual label.
Screenshot
Actual Results
The "Start" and "End" input fields are not explicitly associated with their visual label using “for” and “id” attribute. As a result, users of assistive technologies found it challenging to interact with the form field.
Expected Results
The labels and the form fields should be explicitly associated. To implement this, use <label> element. As well, associate the <label> element with the form field using “for” and “id” attributes. Make sure that the values within “for” and “id” match appropriately.
Code Snippet
<label for="i1">Start</label> <input type="text" id="i1" ...>
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
