[a11y] Sometimes, "Undo" button doesn't work with TalkBack enabled
Categories
(Fenix :: Tabs, defect)
Tracking
(Accessibility Severity:s2, firefox128 affected)
People
(Reporter: apetridean, Unassigned)
References
Details
(Keywords: access, Whiteboard: [fxdroid] [ux-fun-2024])
Attachments
(1 file)
2.00 MB,
video/mp4
|
Details |
Prerequisites:
Enable TalkBack on the device
Ensure you have some tabs opened
Steps to reproduce
- Open the Firefox application.
- Tap on the tab stray.
- Delete some tabs by swiping.
- Double tap on the UNDO button.
- Observe the behavior.
Expected behavior
The tab is restored and appears in the tab tray screen.
Actual behavior
Nothing happens when double-tapping on the UNDO button.
Device information
Firefox version: Firefox 128.0b9
Android device model: Xiaomi Pad5 (Android 13)
Additional Information
This issue was observed only on Xiaomi Pad5 (Android 13).
Comment 1•2 months ago
|
||
Thank you for reporting it, Adina!
This feels like a borderline access-S2
and access-S3
, triaging it as the former because, while a user could technically reopen the tab from the History, but this is a workaround that would require additional physical and mental efforts for TalkBack users while it's provided in one action for general touch audience. It makes it more annoying thought that the snackbar times out before you could even read it and reach it (per WCAG, 20 sec per action could provide a more or less sufficient time for more users, but the snackbar times out much sooner, not allowing to focus the Undo
button and activate it)
@Adina, I'm wondering, if this may be a general issue with these Undo snackbars - have you noticed it not working or/and disappearing even when focused with TalkBack in other use cases?
@Chris, maybe this could be resolved on a component level - to allow the snackbar to stay for 20 sec OR until a user performs an action (activates something with a tap for non-TB and with double-tap for TB users, for instance) AND, if the snackbar or its content is focused with TalkBack or switch before the time out, wait until the focus is moved away after the 20 sec passed to allow them to review the message and, if they choose to, to act on it (to undo the action). WDYT?
Comment 2•2 months ago
|
||
The severity field for this bug is set to S3. However, the accessibility severity is higher, .
:007, could you consider increasing the severity?
For more information, please visit BugBot documentation.
Comment 3•2 months ago
|
||
(In reply to Anna Yeddi [:ayeddi] from comment #1)
@Chris, maybe this could be resolved on a component level - to allow the snackbar to stay for 20 sec OR until a user performs an action (activates something with a tap for non-TB and with double-tap for TB users, for instance) AND, if the snackbar or its content is focused with TalkBack or switch before the time out, wait until the focus is moved away after the 20 sec passed to allow them to review the message and, if they choose to, to act on it (to undo the action). WDYT?
Fixing the snackbar component to avoid this problem in all snackbars is a good idea, if it's possible.
I'll add this bug to our UX Fundamentals bug backlog.
Updated•2 months ago
|
Reporter | ||
Comment 4•2 months ago
|
||
This issue is device-specific; I was able to reproduce it only on the Xiaomi Pad5 (Android 13) in that specific scenario. I could not reproduce it on the latest Nightly 130.0a1 from 10.07.2024 or on Firefox 127.02. This issue is very intermittent, occurring at a rate of 1/5.
Reporter | ||
Comment 5•2 months ago
|
||
This issue is no longer reproducible on the latest Nightly 130.0a1 (from 01.08.2024) with the Xiaomi Pad5 (Android 13). Therefore, we are closing this issue.
Description
•