Unable to navigate using keyboard navigation after reaching the "Manage Nightly settings" link from the Customize Sidebar
Categories
(Firefox :: Sidebar, defect)
Tracking
()
People
(Reporter: rdoghi, Assigned: muffinresearch)
References
(Blocks 1 open bug)
Details
(Keywords: access, Whiteboard: [fidefe-sidebar])
Attachments
(2 files)
Found in
- Nightly 129.0a1
Affected versions
- Nightly 129.0a1 (2024-07-08)
Affected platforms
- All
Preconditions
- Set the following prefs:
sidebar.revamp - true
sidebar.verticalTabs - true
Steps to reproduce
- Open the Customize Sidebar panel.
- Use Tab in order to reach the Manage Nightly settings link.
- Use Tab or Shift tab in order to move away from the link.
Expected result
- The user should be able to navigate without issues.
Actual result
- The user can reach the Manage Nightly settings link but remains locked on the link unable to move away from it.
Regression range
Not a regression.
Comment 1•4 months ago
|
||
This is an access-S3 issue that makes parts of the UI, especially the navigation to the web content, difficult for users of assistive technologies to use.
While the current implementation is not fully blocking most of a11y customers from using the feature, it is a high access-S3
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.
This keyboard trap can be exited by using an F6
key to move between Firefox landmarks, but 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. Users may also not know if there is anything in the list after this link. But this trap, in fact, happens with the very last element of the sidebar, so I'm triaging it as access-S3
which is very close to the bug 1905305 and the access-S2
realm.
Updated•4 months ago
|
Updated•4 months ago
|
Assignee | ||
Updated•4 months ago
|
Assignee | ||
Comment 3•4 months ago
|
||
Assignee | ||
Updated•4 months ago
|
Comment 5•4 months ago
|
||
bugherder |
Reporter | ||
Comment 6•4 months ago
|
||
Verified as fixed in our latest Nightly 130.0a1 (2024-08-04)
Description
•