Open Bug 1905645 Opened 5 months ago Updated 4 months ago

The "attachments" button is displayed a second time in the ChatGPT chat sidebar next to the Text field with High Contrast enabled

Categories

(Core :: Machine Learning, defect, P4)

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 image SquareHigh.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. Inspect the bottom of the ChatGPT sidebar next to the Attach file button.

Expected result

  • The square should not be displayed in the Firefox sidebar with high contrast enabled.

Actual result

  • There is an extra square right next to the Attach File button when we enable High Contrast.

Regression range
Not a regression.

Priority: -- → P4
Summary: There is an extra square displayed in the ChatGPT chat sidebar next to the Text field with High Contrast enabled → The "attachments" button is displayed a second time in the ChatGPT chat sidebar next to the Text field with High Contrast enabled

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, for HCM users (those with low vision, users with cognitive disabilities, users with dyslexia, with colorblindness, and others).

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.

It seems that this is the same button that is being focused as described in the bug 1905703 and is not labelled as described in the bug 1906676 - it either needs to be fixed in the forced-colors media query (HCM on Win) and programmatically labelled, or it should be display:noneed to be removed from both the DOM and Accessibility Tree.

Accessibility Severity: --- → s3
Keywords: stalled
See Also: → 1906676, 1905703

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

For more information, please visit BugBot documentation.

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

Attachment

General

Created:
Updated:
Size: