92.0 beta accessibility problem: broke Dragon Naturally speaking browsing; 91.0.1 works
Categories
(Firefox :: Disability Access, defect)
Tracking
()
People
(Reporter: deborah_mozzy, Unassigned)
Details
(Keywords: regressionwindow-wanted)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:92.0) Gecko/20100101 Firefox/92.0
Steps to reproduce:
Used Firefox on Windows and Dragon NaturallySpeaking Professional 14. Went to any page and dictated the name of a link.
Actual results:
On multiple computers, regardless of whether or not add-ons were enabled, including in a newly-created clean profile, whether or not the Dragon Web Extension is even installed on the computer, the same behavior is consistent:
On Firefox 92:
- dictating the name of a link does nothing
- dictating the name of a link in an
about:
page clicked the link
On Firefox 91:
- dictating the name of a link clicked the link
- dictating the name of a link in an
about:
page clicked the link
Expected results:
on any version of Firefox, it should be that
- dictating the name of a link clicks the link
- dictating the name of a link in an
about:
page clicked the link
This is a big accessibility blocker; it means I can't use Firefox 92 at all. I'm going have to go off of beta channel in order to keep using the browser, but if it's not fixed before 92 rolls out I'm not sure what I'm going to do.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'WebExtensions::Untriaged' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Hello,
I don't understand how can I reproduce the issue without Dragon Web Extension installed and since I don't have the package, please let me know the steps to reproduce the issue in Firefox 92 without the extension.
Thanks,
Victor
Updated•3 years ago
|
Reporter | ||
Comment 3•3 years ago
|
||
Dragon web extension isn't necessary for testing the problem, but Dragon naturally speaking is. (Windows speech recognition, which is a built-in, can't click links directly at all.)
I don't know how you could reproduce it without Dragon NaturallySpeaking. In the past I know there have been people at Mozilla who had NaturallySpeaking installed, and Mozilla has fixed bugs that were specific to NaturallySpeaking. Nobody in the Mozilla accessibility team has access to a copy of Dragon anymore?
Comment 4•3 years ago
|
||
Dragon web extension isn't necessary for testing the problem, but Dragon naturally speaking is. (Windows speech recognition, which is a built-in, can't click links directly at all.)
Thanks for clarify it.
It looks this potential regression isn't related to extensions and so I'm moving it to "Firefox :: Disability Access" where it can be investigated and triaged more appropriately.
Comment 5•3 years ago
|
||
What specific beta of Firefox was this tested with? Was it 92.0b6 or was it an earlier version? We don't have access to Dragon Naturally Speaking, but I landed a fix in bug 1725449 which I suspect might address this. That fix was uplifted to 92.0b6.
Updated•3 years ago
|
Updated•3 years ago
|
Reporter | ||
Comment 6•3 years ago
|
||
I just upgraded to 92.0b7 and it's fixed. thank you!
Also I didn't realize that Jamie Teh was at Mozilla now; Firefox accessibility really is superstars all the way down.
Comment 7•3 years ago
|
||
Thanks for confirming the fix and for reporting the issue in the first place. I'll close this as a duplicate.
Description
•