[Bookmarks Evolution] Sorting menu focus order doest not follow the visual reading order
Categories
(Firefox for Android :: Bookmarks, defect)
Tracking
()
People
(Reporter: ayeddi, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: access, Whiteboard: [fxdroid][group1])
Attachments
(1 file)
Steps to reproduce
- Have TalkBack running
- Open Firefox and navigate to the Settings > Bookmarks menu
- Using logical navigation gestures (swipe left-to-right with one finger) navigate to the first control after a title - the sorting button (
More options
per bug 1961231) - Activate the sorting menu by double-tapping the screen
- Observe the TB announcemen
- Proceed reviewing the list of options using logical navigation gestures and observe the TB focus behavior
Expected behavior
- The menu should first get the topmost option focused ("Sort by newest"), then the second ("Sort by oldest") etc. following the visual reading order.
Actual behavior
- The first item focused in the checked option (on the screenshot, it's "Sort by A to Z") which is not the first in the visual reading order (on the screenshot, it's the 3rd), only then the TB focus goes back to the topmost item ("Sort by newest"), then the visually second ("Sort by oldest"), then skipping the previously announced option, to the last item in the list ("Sort by Z to A").
Device information
- Firefox version: Firefox Nightly 139.0a1 (build #2016084991)
- Android device model: Samsung Galaxy A54 5G
- Android OS version: 14
Any additional information?
Following visual reading order is recommended because it would allow users of a screen reader who still can see their screens to follow the focus without sudden jumps in it.
Updated•6 months ago
|
Comment 1•6 months ago
|
||
The severity field is not set for this bug.
:boek, could you have a look please?
For more information, please visit BugBot documentation.
Updated•4 months ago
|
Comment 2•2 months ago
|
||
I believe this is a known bug, related to bug 1919104
It's something in our design system, and I believe that it's a system prompt. See my notes in this comment. The main constraint here is that we manually modify the traversal order so that we can "pre-select" the currently selected item, and that's why the traversal order is preserved.
If we are okay with starting from index 0, then we can work make that happen. Otherwise, starting from the current selection makes it hard to preserve the traversal order
Description
•