1905703 - Screen readers are reading out loud an extra button collapsed submenu inside the ChatGPT panel before the Attach file button

Status: NEW

(Core :: Machine Learning, defect, P4)

Description

[Rares Doghi, Desktop QA]

Found in

• Nightly 129.0a1

Affected versions

• Nightly 129.0a1 (2024-07-01)

Affected platforms

• All

Preconditions

• Enable Screen Readers.

Steps to reproduce

1. Reach about:preferences#experimental page.
2. Enable the AI Chat integration.
3. Select the ChatGPT AI provider.
4. Use keyboard navigation to open the Chat GPT sidebar.
5. Reach the Attach File button from the bottom of the panel.
6. Go back one Step.

Expected result

• Only existing buttons should be read out loud by screen readers.

Actual result

• There is an extra button being read out loud by NVDA or Voice Overs right before the Attach File button.

Regression range
Not a regression.

Comment 1

[Anna Yeddi [:ayeddi]]

Attachment: VoiceOver output for the visually hidden focusable Menu popup collapsed button before the Attach file control

Comment 2

[Anna Yeddi [:ayeddi]]

This is an access-S3 issue that does not block a user but makes it difficult to use, because visually hidden but not accessibility hidden content creates additional tab stops for keyboard-only users (with and without screen readers) and switch device users who are already require more effort to navigate the content. This makes the navigation more cumbersome than it should be. It would also be confusing for users with cognitive difficulties, because an unlabelled but focusable element may be crucial for the flow - or may not. They'd need to guess what it could do.

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.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

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.