Closed Bug 1403006 Opened 8 years ago Closed 8 years ago

[a11y][UX] Activity Stream design of a scrollable container inside a scrollable container is unintuitive with Talkback

Categories

(Firefox for Android Graveyard :: Activity Stream, defect, P3)

All
Android
defect

Tracking

(fennec+)

RESOLVED DUPLICATE of bug 1398836
Tracking Status
fennec + ---

People

(Reporter: mcomella, Unassigned)

References

Details

You can: - Swipe right over the top sites tiles to scroll to the next page of top sites tiles - Swipe outside of the top sites tiles to scroll to the next page of the home screen (i.e. to Bookmarks, then History) For non-visual users, it's difficult to distinguish the two containers so some options to consider: - Reconsider the Top Sites design - Provide a configurable value so Top Sites can be more intuitive to non-visual users (will this be enough to make it intuitive?) Flagging for triage because this is an important issue that is a comprehensive redesign so I can't determine the priority of myself. Eitan, would you have anything to elaborate on here?
Flags: needinfo?(eitan)
Priority: -- → P3
Rank: 1
tracking-fennec: ? → +
Maybe a good solution would be if a talkback cursor swipe past the last top site would scroll the next top sites pane into view and put the cursor on the first tile there. Aside from that I would remove the swipe hint that talkback gives when landing on the top sites.
Flags: needinfo?(eitan)
(In reply to Eitan Isaacson [:eeejay] from comment #1) > Maybe a good solution would be if a talkback cursor swipe past the last top > site would scroll the next top sites pane into view and put the cursor on > the first tile there. > > Aside from that I would remove the swipe hint that talkback gives when > landing on the top sites. To be explicit, "the swipe hint that talkback gives when landing on top sites" would be Talkback describing the Top Sites view as a "Multipage view" and (sometimes) "Page 1 of 2"? Though perhaps an explicit swipe hint was added in Oreo that I'm unaware of. --- That being said, the changes you suggest can be encapsulated in bug 1398836 and don't require overarching UX changes (this bug) so I'll dupe this.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(eitan)
Resolution: --- → DUPLICATE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.