Device name not reported when using synced tabs menu with a screen reader
Categories
(Firefox :: Sync, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox73 | --- | verified |
People
(Reporter: Jamie, Assigned: markh, Mentored)
Details
(Keywords: access, Whiteboard: [access-p2])
Attachments
(1 file)
STR (with the NVDA screen reader):
- Ensure you have at least one synced tab on another device.
- Press the Firefox Account button on the toolbar.
- Choose Synced Tabs.
- Press down arrow until you reach the first synced tab.
- Expected: NVDA should have reported the name of the device the tab was synced from, as well as the name of the tab.
- Actual: It doesn't; it only reports the tab name.
The best way to fix this would be to make each client a container with role="group" and label it with the device name using aria-labelledby. Unfortunately, right now, there isn't a container element; the buttons are just appended after the label:
https://searchfox.org/mozilla-central/rev/a78233c11a6baf2c308fbed17eb16c6e57b6a2ac/browser/components/customizableui/CustomizableWidgets.jsm#789
I'm not sure whether I can safely add an intervening container here without breaking visual styling (or what element to use), so I can't fix this myself.
Comment 1•5 years ago
|
||
Thanks for the great bug report, Jamie. Can I presume this bug also affects the Synced Tabs list in the sidebar?
Hey eoger, is this bug in the right place for the Synced Tabs menu?
Comment 2•5 years ago
|
||
Moving to Sync so we can triage, thanks!
Comment 3•5 years ago
|
||
The component has been changed since the backlog priority was decided, so we're resetting it.
For more information, please visit auto_nag documentation.
Reporter | ||
Comment 4•5 years ago
|
||
(In reply to Mike Conley (:mconley) (:⚙️) (Wayyyy behind on needinfos) from comment #1)
Can I presume this bug also affects the Synced Tabs list in the sidebar?
Yes, though the synced tabs sidebar has a whole bunch of other problems that are far worse than this one, making it much uglier (practically unusable?) for screen reader users than the menu. I will try to get around to filing a separate bug for that.
Updated•5 years ago
|
Comment 5•5 years ago
|
||
The priority flag is not set for this bug.
:markh, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 6•5 years ago
|
||
Updated•5 years ago
|
Comment 8•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Comment 9•5 years ago
|
||
I've reproduce this issue with Fx 72.0a1 (2019-11-24) on Windows 10 x64., using the provided steps from description.
The issue is verified fixed with Fx 74.0a1(2020-01-29) and Fx 73.0b11 on Windows 10 x64 and Windows 7x86.
Assignee | ||
Updated•5 years ago
|
Description
•