The Firefox elements are no longer recognized by the VoiceOver screen reader after pressing the "Keep in Dock" button
Categories
(Core :: Widget: Cocoa, defect, P3)
Tracking
()
Accessibility Severity | s4 |
Tracking | Status | |
---|---|---|
firefox89 | --- | unaffected |
firefox90 | --- | affected |
firefox91 | --- | affected |
People
(Reporter: cmuntean, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: access)
[Affected versions]:
- Firefox Beta 90.0b5;
- Nightly 91.0a1
[Affected Platforms]:
- macOS 10.15.7;
- macOS 15.14.6;
- macOS 11.4;
[Prerequisites]:
- Have the latest Firefox 90 Beta.
- The Firefox is not kept in dock.
- Have the VoiceOver screen reader enabled.
[Steps to reproduce]:
- Open the Firefox browser using a new clean profile.
- Press the tab key until the "Keep in Dock" button is focused.
- Press the "Enter" key.
- Wait until the VoiceOver reads the Header 1, then navigate through the browser using the tab key.
- Observe the behavior.
[Expected result]:
- The VoiceOver screen reader keeps reading all the focused elements.
[Actual result]:
- The VoiceOver screen reader no longer reads the focused elements.
[Notes]:
- If the browser is unfocused and then focused again, the VoiceOver continues reading the focused elements.
Reporter | ||
Updated•3 years ago
|
Comment 1•3 years ago
|
||
This might be related to bug 1714148 perhaps also caused by the Dock getting killed and restarted? I noticed after clicking "Keep in Dock" in Firefox, VoiceOver announces the next screen of about:welcome then starts announcing…
"actions available, You are currently on a application dock item. To open this application, press Control-Option-Space. To show exposé press Control-Option-Command-Space first to bring up the action…"
And pressing control-option-left/right does indeed move through items on the Dock.
Comment 2•3 years ago
|
||
Cosmin, can you monitor if Firefox is getting killed and restarted?
Reporter | ||
Comment 3•3 years ago
|
||
I have monitored all the Firefox processes while reproducing the issue, but from what I have observed no process was killed. However, I have noticed that the VoiceOver focus jumps on the first item in the docker and remains focused even if you are navigating through the Firefox elements using the keyboard.
I have uploaded a screen recording of this behavior. You can find it here: GDrive.
Please let me know if you need any other information.
Comment 4•3 years ago
•
|
||
The issue isn't Firefox getting killed as that would likely result in Firefox closing completely. I mentioned the Dock getting killed in comment 1.
Moving to a macOS related component although if inappropriate here, most likely it'll end up in Toolkit::General matching original bug 1709598.
Comment 5•3 years ago
|
||
Are you able to reproduce this behavior when you pin Google Chrome to the Dock in the same way?
Reporter | ||
Comment 6•3 years ago
|
||
@Stephen I am not sure if I can reproduce this behavior in the same way with Chrome, because this issue is related to the "Keep in Dock" button from the "about:welcome" page in Firefox.
Do you know if Chrome has a similar button or option so I can try to reproduce this behavior?
Comment 7•3 years ago
|
||
Yes:
- Ensure that Google Chrome is not installed on the system.
- Download Google Chrome.
- Open Disk Image and double-click the app icon (don't drag and drop to the Applications directory).
- When prompted, click to Install Google Chrome.
The difference here might be that Google Chrome wasn't running at the time that the Dock is killed, but it would be good to get confirmation whether or not VoiceOver works after the Dock is killed and restarted.
Reporter | ||
Comment 8•3 years ago
|
||
@Stephen thank you for providing the steps to test this behavior in Chrome. I have followed them and it seems that after Chrome is installed and pin to the Dock, the VoiceOver screen reader focuses the new tab from Chrome and continues reading all the focused elements using the keyboard navigation.
So it seems that VoiceOver works as expected using this method for Chrome.
I have also made a screen recording. You can find it here: GDrive.
Comment 9•3 years ago
|
||
Thank you for verifying!
Updated•3 years ago
|
Updated•1 year ago
|
Description
•