History sidebar has a "..." menu button that is not labeled
Categories
(Firefox :: Sidebar, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox133 | --- | fixed |
People
(Reporter: ayeddi, Assigned: sclements)
References
(Blocks 1 open bug)
Details
(Keywords: access, Whiteboard: [fidefe-sidebar])
Attachments
(2 files)
Prerequisites:
- Ensure a screen reader is running, i.e. NVDA on WinOS
STR:
- In Firefox, ensure the
sidebar.revamppref is set totrueand the new sidebar is visible - Locate and activate
Historypanel of the sidebar - Locate and navigate to the
...(sorting) control after the search input and observe the screen reader announcement
Expected:
- Role, name, and state of the control is announced, i.e.
Sorting, menu button, collapsed
Actual:
- The button is missing its accessible name (is unlabeled)
- The button that serves as a menu button lacks both
aria-expandedandaria-haspopup=menuattributes
This is an access-S2 issue that makes this part of the UI, including the attached menu, inaccessible for users of assistive technologies. Users with voice control won't be able to call its name to activate it, users of screen readers won't know what is the purpose of this button. Learn more about ways to make image buttons accessible in the W3C WAI Tutorials
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 1•1 year ago
|
||
The severity field for this bug is set to S3. However, the accessibility severity is higher, .
:sclements, could you consider increasing the severity?
For more information, please visit BugBot documentation.
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 3•1 year ago
|
||
| Assignee | ||
Comment 4•1 year ago
|
||
I noticed the chatbot panel has the same pattern of using the 3-dot button as a menu and is missing some of the same attributes, so I've updated there as well.
Comment 6•1 year ago
•
|
||
Backed out for causing sidebar related failures
Logs for the fails can be found in the push link above.
| Assignee | ||
Updated•1 year ago
|
Comment 8•1 year ago
|
||
| bugherder | ||
Updated•1 year ago
|
Comment 9•1 year ago
|
||
Reproduced the issue with Firefox 133.0a1 (2024-10-06) on Windows 10.
The issue is verified fixed with Firefox 134.0a1 (20241105092845) and Firefox 133.0b4(20241104091514) on Windows 10, Ubuntu 22 and macOS 14.
Description
•