1905305 - Unable to reach the ChatGPT Chat History using keyboard navigation

Status: NEW

(Core :: Machine Learning, defect, P3)

Description

[Rares Doghi, Desktop QA]

Attachment: 2024-06-28_13h47_14.mp4

Found in

• Nightly 129.0a1

Affected versions

• Nightly 129.0a1 (2024-06-28)

Affected platforms

• All

Steps to reproduce

1. Reach about:preferences#experimental page.
2. Enable the AI Chat integration.
3. Select the ChatGPT AI provider.
4. Reach the AI chat Sidebar using Keyboard navigation.
5. Open the Chat GPT sidebar menu.
6. Use the Tab key in order to reach a chat from the History.

Expected result

• The user should be able to navigate to the Chat History in the Chat GPT sidebar menu using Keyboard

Actual result

• The users is Stuck at the Explore GPT's menu option.
  Going back with Shift Tab will reach the Chat History but once the user wants to go back he remains stuck on the Explore GPT's option.

Regression range
Not a regression.

Comment 1

[Ania]

Pretty annoying for accessibility and is reproducible on chatgpt.com, regardless of whether it's opened in the sidebar or not (so might need to be punted to webcompat).

Comment 2

[Anna Yeddi [:ayeddi]]

This is an access-S2 issue that makes parts of the UI, especially the navigation inaccessible for users of assistive technologies to use. While the current implementation is not fully blocking most of a11y customers from using the feature, the issue is marked as access-S2 because it does create barriers for many groups of users, especially those keyboard-only users who are new to relying on the keyboard input only, for users of switch devices and other alternative inputs. While this keyboard trap can be exited by the reverse navigation, it is not something that is expected to happen (it is a workaround) and some less experienced users or users with cognitive disabilities may not be aware of. This trap is also appearing in the middle of the menu list, thus it is less likely that a user would expect any bad focus management too (as it may be the cause of the bug 1905327 that has a lower a11y severity).

As Ania pointed out in the comment above, this appear to be an accessibility issue on the side of the chatbot service. Firefox team will need to pass this information to the provider, but until it is resolved, we could mark this bug as stalled.

Comment 3

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

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.

Comment 4

[Mike Kaply [:mkaply]]

I think they might have fixed this (I can't recreate).

Can you recheck?

Comment 5

[Rares Doghi, Desktop QA]

Hi @Mike, This issue still occurs in our latest Nightly build 130.0a1 (2024-07-23).

Comment 6

[Rares Doghi, Desktop QA]

Attachment: 2024-07-24_11h49_11.mp4

Comment 7

[Mike Kaply [:mkaply]]

Thanks, we've reported it.