The items from the Hugging Chat sidebar do not change their state when hovered with High contrast enabled
Categories
(Core :: Machine Learning, defect)
Tracking
()
| Accessibility Severity | s3 |
People
(Reporter: rdoghi, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: access, stalled)
Attachments
(1 file)
|
2.38 MB,
video/mp4
|
Details |
Found in
- Beta 130.0b3
Affected versions
- 131.0a1 (2024-08-12)
- Beta 130.0b3
Affected platforms
- Windows
Preconditions
Enable High Contrast
Steps to reproduce
- Reach about:preferences > Firefox labs and Enable the AI chatbot.
- Select the Hugging chat AI from the Ai provider dropdown and Sign in.
- Open the Hugging Chat sidebar.
- Hover over each item from the Hugging chat sidebar.
Expected result
- Each item should change their state on hover.
Actual result
- The items do not change their state on hover.
Regression range
Not a regression.
|
||
Comment 1•2 months ago
|
||
Marking as access-s3 since a hover style does not impact core functionality.
|
||
Comment 2•1 month ago
|
||
As Eitan has mentioned above, the lack of the semantic styling in the High Contrast Mode (HCM) is an access-S3 issue. Note that while it is not blocking the operability of these controls, it makes it difficult to discern which element is, in fact, an active UI and could be activated if clicked, which one is now hovered and which one is not, for HCM users (those with low vision, users with cognitive disabilities, users with dyslexia, with colorblindness, and others).
We need to ensure the appropriate color pairs are used for forced-colors media query (HCM on Win): ButtonFace with ButtonText for the border/label text and for the control background. The hovered state is expected to use SelectedItem and SelectedItemText color combination in place of the Button colors of the default state.
Adding a Figma reference for color combinations for different Win10 and Win11 themes (SSO required), as well as the buttons on HCM (SSO required).
Note: This appears to be an accessibility issue on the side of the chatbot service. Firefox team would need to pass this information to the provider, but until it is resolved, I'm marking this bug as stalled.
Description
•