Open Bug 1911302 Opened 2 months ago Updated 2 months ago

Keyboard navigation will reach items from the Anthropic AI sidebar when closed

Categories

(Core :: Machine Learning, defect)

Desktop
Unspecified
defect

Tracking

()

Accessibility Severity s3
Tracking Status
firefox-esr128 --- disabled
firefox128 --- disabled
firefox129 --- disabled
firefox130 --- affected

People

(Reporter: rdoghi, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: access)

Attachments

(1 file)

Attached video HiddenItems.mp4

Found in

  • Nightly 130.0a1 (2024-08-02)

Affected versions

  • Nightly 130.0a1 (2024-08-02)

Affected platforms

  • all

Steps to reproduce

  1. Reach about:preferences#experimental - Firefox Labs page
  2. Enable the AI chatbot integration and Login to the Anthropic AI provider
  3. Use the Tab key to navigate inside the Anthropic AI sidebar.

Expected result

  • The user should only reach the visible items with keyboard navigation.
    Users should only be able to reach the items from the Anthropic Sidebar when its opened.

Actual result

  • The user will have to go through each older chats from the Anthropic sidebar in order to reach visible items.
    Users might select something they dont want using keyboard navigation.

Regression range
Not a regression.

In general, missing focus indicators is an access-S2 issue that makes this part of the UI inaccessible for users of assistive technologies, especially those relying on keyboard alone, because it is not clear what is, if anything, is currently focused and what could happen, if this invisible element is activated. This also makes the navigation with keyboard unpredictable.

In this case, the keyboard focus lands on visually hidden but not accessibility hidden content (the Pin sidebar button), which at the moment is not expected to be used by the user, thus I'm marking it as access-S3. It is still confusing and makes the keyboard navigation more cumbersome than it should be.

Using display: none; on any content that is not expected to be visible would resolve this issue.

This appears to be an accessibility issue on the side of the chatbot service. Firefox team would need to pass this information to the provider, but until it is resolved, I'm marking this bug as stalled.

Accessibility Severity: --- → s3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: