Open Bug 1905640 Opened 5 months ago Updated 5 months ago

The Temporary Chat button from the ChatGPT menu inside the Firefox Sidebar is not displayed with High Contrast

Categories

(Core :: Machine Learning, defect, P3)

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

(1 file)

Attached image 2024-07-01_12h58_42.png

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. Open the ChatGPT menu from the middle of the Sidebar

Expected result

  • The Temporary Chat button should be displayed with High Contrast

Actual result

  • The temporary chat button is not displayed with High Contrast enabled.

Regression range
Not a regression.

Priority: -- → P3

Triaging it as access-S2 because the control is nearly missing, it is useless for a user with HCM on (i.e. someone with low vision, or with cognitive disability, or with dyslexia who relies on the High contrast mode themes) - the state is not visible and there are no alternative ways to learn if the toggle is on or off.

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. Also, for selectable controls, SelectedText and SelectedBackground color combination could be used to indicate their selected/on state.

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.

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: