Open Bug 1887199 Opened 1 year ago Updated 1 year ago

Voice Access Windows 11 Show Numbers Doesn't Mark Tabs

Categories

(Firefox :: Tabbed Browser, defect, P3)

Firefox 126
Desktop
Windows 11
defect

Tracking

()

Tracking Status
firefox-esr115 --- affected
firefox124 --- affected
firefox125 --- affected
firefox126 --- affected

People

(Reporter: dlhubble, Unassigned)

Details

Attachments

(1 file)

Steps to reproduce:

Have Firefox open with multiple tabs running.
Turn on Voice Access in Windows 11.
Say "open FireFox."
Say "show numbers."

Actual results:

No numbers are placed over other open tabs making it impossible to select them other than with saying "press ctrl tab" repeatedly.

Expected results:

Numbers should have been put over other open tabs so you could say "click [number]" and the tab would be selected. This is working in Edge.

Summary: Voice Access Windows 11 Show Numbers Doesn't Show Tabs → Voice Access Windows 11 Show Numbers Doesn't Mark Tabs

The Bugbug bot thinks this bug should belong to the 'Firefox::Tabbed Browser' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Tabbed Browser

Comparison - tabs of Firefox Nightly + Chrome + Edge with Voice Access on Win11 after Show Numbers command

i think the issue is that that the AT is looking for the focusable state, but only the selected tab has it. we do it this way because only the selected tab is in the tab order. the tab bar manages it's own focus with arrowing etc. worth checking if they actually are focusable of if there is another attribute we could be using, for example the action name.

Looks like all our tabs have an action, but their name is "switch", it might be as simple as the action name or something else. adding a "focusable" state should be the last resort.

(In reply to Anna Yeddi [:ayeddi] from comment #2)

Created attachment 9394574 [details]
Comparison - tabs of Firefox Nightly + Chrome + Edge with Voice Access on Win11 after Show Numbers command

Details for the image attached:
On my Win11, Voice Access behaves a bit better with Chrome: the numbers are added to the tabs as they are added to the Edge tabs, but sending a click to a tab with Chrome only shows a tab preview, you cannot open it with the direct command. Edge opens the tab with the click {number} command. Both show numbers for both the each tab and its X Close button.
Firefox only shows numbers for Fx View and active tab and + Open new tab.

Does setting accessibility.uia.enable to true in about:config help? Note that this is only remotely useful in latest Nightly. It's probably a good idea to restart Firefox after doing that just in case, even though it's not strictly necessary.

The severity field is not set for this bug.
:mconley, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(mconley)
Severity: -- → S4
Flags: needinfo?(mconley)
Priority: -- → P3

I can confirm this issue on Win11 with Nightly v126.0a1, Beta v125.0b9 and ESR v115.9.1esr. Numbers aren't shown for the opened tabs in the browser window.

Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Unspecified → Windows 11
Hardware: Unspecified → Desktop
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: