The Anthropic Claude Edit Chat title dropdown buttons do not change their state with High Contrast enabled
Categories
(Core :: Machine Learning, defect)
Tracking
()
| Accessibility Severity | s3 |
People
(Reporter: rdoghi, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: access, stalled)
Attachments
(1 file)
|
2.49 MB,
video/mp4
|
Details |
Found in
- Beta 130.0b3
Affected versions
- 131.0a1 (2024-08-08)
- 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 Anthropic Claude from the Ai provider dropdown and Sign in.
- Select any older Chat or start a new one.
- Click the Chat title in order to show the Rename/Delete buttons.
- Use Up/Down Arrows in order to select one of the buttons.
- Use the mouse cursor to hover on top of the buttons.
Expected result
- The Rename or Delete buttons should change their state when hovered over or selecte with keyboard navigation
Actual result
- The Rename and Delete button do not change their state when reached with Keyboard navigation or Hovered over with the mouse cursor.
Regression range
Not a regression.
|
||
Comment 1•2 months ago
|
||
The lack of the semantic styling in the High Contrast Mode (HCM) is an access-S3 issue since 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 SelectedText and SelectedBackground 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).
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
•