Open Bug 1905638 Opened 5 months ago Updated 4 months ago

Some of the buttons from the Chat GPT Sidebar disappear on hover with High Contrast enabled

Categories

(Core :: Machine Learning, defect, P3)

Desktop
Windows
defect

Tracking

()

Accessibility Severity s3
Tracking Status
firefox-esr115 --- disabled
firefox127 --- disabled
firefox128 --- disabled
firefox129 --- affected

People

(Reporter: rdoghi, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: access, stalled)

Attachments

(1 file)

Attached video 2024-07-01_13h00_21.mp4

Found in

  • Nightly 129.0a1

Affected versions

  • Nightly 129.0a1 (2024-07-01)

Affected platforms

  • Windows

Preconditions

  • Enable High Contrast

Steps to reproduce

  1. Reach about:preferences#experimental page.
  2. Enable the AI Chat integration.
  3. Select the ChatGPT AI provider.
  4. Hover over Attach File button, Help button (bottom right), New Chat (inside the Sidebar from the ChatGPT) and "Options" from the History Chats

Expected result

  • The buttons should still be displayed when the user hovers over them with the mouse cursor

Actual result

  • The Attach file button, Help button, New Chat and Older Chat Options button disappear when the user hovers over them with the Mouse Cursor while High Contrast is enabled.

Regression range
Not a regression.

Priority: -- → P3

In general, the lack of state differentiation on the High Contrast Mode (HCM) is an access-S3 issue since it makes it difficult to discern which control is, in fact, hovered and would be activated if clicked, for HCM users (those with low vision, users with cognitive disabilities, users with dyslexia, with colorblindness, and others).

In this case, it is a high access-S3 because hovering most of the controls does not leave any indication of a control being present there, i.e. not even a tooltip with the name of the control for the Attach File button. Users with cognitive disabilities would be the most impacted because there would be no consistent identification of a control and, when control disappears on hover, it is not clear if it would be, in fact, activated if clicked now.

This appears to be an accessibility issue on the side of the chatbot service. Firefox team is going to pass this information to the provider, but until it is resolved, I'm marking this bug as stalled.

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.

Accessibility Severity: --- → s3
Keywords: stalled
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: