Closed
Bug 1903827
Opened 1 year ago
Closed 1 year ago
Close tab on tabstrip is not providing a context to TalkBack
Categories
(Firefox for Android :: Tabs, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox129 | --- | fixed |
People
(Reporter: ayeddi, Assigned: npoon)
References
(Blocks 1 open bug)
Details
(Keywords: access, Whiteboard: [fxdroid][group4])
Attachments
(1 file, 1 obsolete file)
Steps to reproduce
- Ensure a TalkBack is running
- Open Firefox and confirm the a tab is opened
- If this is a New Tab:
- dismiss the keyboard (until the bug 1902757 is resolved) and, if opened, any OMC onboarding notifications or type in any URL
- open any tab, i.e. wikipedia from tiles
- Open another tab (repeating step 3)
- With TalkBack, navigate to the first open tab in the tabstrip
- Using a navigational gesture of TalkBack (swiping left-to-right with one finger, in LTR/English, for instance), navigate to the
Close tabbutton within this tab and observe the TB announcement - Repeat steps 5-6 for the second tab and compare the TalkBack announcements for two
Close tabbuttons.
Expected behavior
- A context is provided and it is clear, which tab would be closed, when activated.
- Navigation with TB shortcuts between buttons makes it clear, which tab's Close button is focused
Actual behavior
- Both buttons are announced the same -
Close tab- and it is not clear, which tab would be, in fact, closed if one of them is activated. - While navigating with TB shortcuts between buttons, is not clear, which tab's Close button is focused.
Device information
- Firefox version: Nightly 129.0a1 (build #2016026447)
- Android device model: Samsung Galaxy Tab S7+
- Android OS version: 13
Any additional information?
- The severity of this issue could've been access-S4 if Close buttons would've been hidden when multiple tabs are opened. In that case, i.e. as another major browser does, when only one tab has an on-screen Close button, there are less other options when guessing which tab would be, in fact, closed when this control is activated. But in the situation when there are multiple
Close tabbuttons present in the reading order, it is hard to navigate to the needed one and make a precise choice. Especially, with the selected/current state information being missed (addressed in bug 1902761) - Another major browser on the same device does announce the title of the tab, i.e.
Close Wikipedia tab, but another remediation option could be grouping a tab view which currently includes both the tab and its Close button.
| Assignee | ||
Updated•1 year ago
|
Assignee: nobody → npoon
| Assignee | ||
Updated•1 year ago
|
Whiteboard: [fxdroid][group4]
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
•
|
||
As a follow up to this accessibility bug, I noticed that a similar thing is happening in the tabs tray (in grid view) but not in the tabs tray (in list view) and I couldn't find an existing bug about this. Would you please follow these steps to reproduce the bug and file another bug if this is an issue? The steps to reproduce (on a phone) are as follows:
Steps to Reproduce
- Ensure a TalkBack is running
- Open Firefox and confirm that a tab is opened
- Open the Tabs Tray and ensure that the tabs view is set to "Grid"
- If this is a New Tab:
i. dismiss the keyboard (until the bug 1902757 is resolved) and, if opened, any OMC onboarding notifications or type in any URL
ii. open any tab, i.e. wikipedia from tiles - Open another tab (repeating step 3)
- With TalkBack, navigate to the first open tab in the Tabs Tray
- Using a navigational gesture of TalkBack (swiping left-to-right with one finger, in LTR/English, for instance), navigate to the Close tab button within this tab and observe the TB announcement
Actual Behaviour
- Both buttons are announced the same - Close tab - and it is not clear, which tab would be, in fact, closed if one of them is activated.
- While navigating with TB shortcuts between buttons, is not clear, which tab's Close button is focused.
Device Information
- Android device model: Samsung A35
- Android OS version: Android 14
Flags: needinfo?(ayeddi)
| Assignee | ||
Comment 2•1 year ago
|
||
| Assignee | ||
Comment 3•1 year ago
|
||
Updated•1 year ago
|
Attachment #9408739 -
Attachment is obsolete: true
| Assignee | ||
Comment 4•1 year ago
|
||
I was told that the behaviour should be similar in the Tabs Tray grid view so I have filed a bug here
Flags: needinfo?(ayeddi)
Updated•1 year ago
|
Severity: -- → S2
Priority: -- → P1
Pushed by calu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a31e53c97151
Close tab button on Tab Strip is providing a context to TalkBack r=android-reviewers,007
Comment 6•1 year ago
|
||
Backed out for causing lint failures.
Backout link: https://hg.mozilla.org/integration/autoland/rev/a433930b93fc67faae81b2e1135806aac25646d3
Failure log: https://treeherder.mozilla.org/logviewer?job_id=463968513&repo=autoland
Flags: needinfo?(npoon)
Updated•1 year ago
|
Attachment #9408741 -
Attachment description: Bug 1903827 - Close tab button on Tab Strip is providing a context to TalkBack → WIP: Bug 1903827 - Close tab button on Tab Strip is providing a context to TalkBack
Updated•1 year ago
|
Attachment #9408741 -
Attachment description: WIP: Bug 1903827 - Close tab button on Tab Strip is providing a context to TalkBack → Bug 1903827 - Close tab button on Tab Strip is providing a context to TalkBack
Pushed by calu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/260a424d4946
Close tab button on Tab Strip is providing a context to TalkBack r=android-reviewers,007
Comment 9•1 year ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox129:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 129 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•