Open Bug 1905650 Opened 5 months ago Updated 4 months ago

The Google Gemini buttons from the Sidebar disappear on Hover with High Contrast enabled

Categories

(Core :: Machine Learning, defect, P4)

Desktop
Windows
defect

Tracking

()

Accessibility Severity s2
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

(2 files)

Attached video Geminibuttons.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 Google Gemini AI provider.
  4. Hover over the buttons from the Chat Panel.
  5. Open the Sidebar and Hover over the buttons from the Gemini side panel

Expected result

  • Every button should be displayed when the user hovers over it with High Contrast enabled.

Actual result

  • The Buttons disappear when the user Hovers over them with High Contrast enabled.

Regression range
Not a regression.

Attached video HighContrastGemini.mp4

Please also note that the Actions for a Gemini response also disappear on hover with High Contrast enabled

Priority: -- → P4

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 an access-S2 because the input area for the prompt - the crucial control for the entire flow of the chatbot - is practically missing in HCM (due to lack of any visual indication of any operability of the element and no hover or focused states being provided) that make a feature not discoverable/actionable by users with low vision - it looks like this is just an instructional text which is static. It is not clear how to proceed and where to, in fact, start typing the input to start the chat.

Also, 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 Gemini v button. Other tooltips appear far away from the label text which may be missed by a user with magnification software or a physical magnifier in hands. 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: --- → s2
Keywords: stalled

The severity field for this bug is set to S3. However, the accessibility severity is higher, .
:tarek, could you consider increasing the severity?

For more information, please visit BugBot documentation.

Flags: needinfo?(tziade)
Severity: S3 → S2
Flags: needinfo?(tziade)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: