Input type=date and datetime-local shadow-root controls to provide visual hover state indication
Categories
(Firefox :: Theme, enhancement)
Tracking
()
People
(Reporter: ayeddi, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: access)
Attachments
(2 files)
STR:
- Open Firefox and navigate to the following URI:
data:text/html, <input type="date" value="2022-12-15">
- Hover over each of the editable field (for
type=date
its month, day, year) and a reset button within the field to observe the hover behavior - Repeat steps 1-2 for the
data:text/html, <input type="datetime-local" value="2022-12-15">
Expected:
- Editable fields show visible indication of the state change from default to hovered
- Button within a field shows visible indicator of its hovered state as well
Observed:
- No change in the visual presentation of editable fields and a button
Note: Per the WCAG 2.1, the active user interface component may pass because of its position (button) or a border (input), but because the date/datetime-local inputs include multiple active UI (each field is editable separately plus the button, when applicable) it becomes unclear what is actionable and what is not actionable with a mouse, unless the control is clicked. In the case with a Reset button it means that the user clears out the entire field to figure out if the icon is functional or not. Plus, the /
, :
etc between editable fields are not actionable and cannot be removed, which is not clear until focused or clicked. The passing indication for editable fields could be a pointer change.
Reporter | ||
Updated•2 years ago
|
Reporter | ||
Comment 1•2 years ago
|
||
Adding a Calendar button to the bug, because its hover indication (without HCM running) is subtle as shown on the screenshot attached - the opacity changes to 1 and this is the only indication provided
Reporter | ||
Comment 2•2 years ago
|
||
To highlight that the input fields do not provide any hover indication, incl. the pointer that stays the same
Description
•