Firefox - Accessibility: The word "alert" output by the NVDA screen reader when opening a new tab from within the Firefox Release Notes page
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
People
(Reporter: elliottabarnes, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:86.0) Gecko/20100101 Firefox/86.0
Steps to reproduce:
Tested with the last several releases of Firefox - both on Windows 7/10 and with the latest build of the NVDA screen reader (2020.4 at present).
-
Navigate to the "Release Notes" page for Firefox (https://www.mozilla.org/en-US/firefox/releases/)
-
Press Ctrl + T to open a new tab
Actual results:
Upon pressing the hotkeys to open a new tab, NVDA immediately speaks the word "alert" - rather than the usual text that would typically be output when opening a new tab
Expected results:
NVDA should interact as it would typically do and announce the element that receives focus when opening a new tab
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Disability Access APIs' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 2•4 years ago
|
||
I suspect this is some quirk with the mozilla.org website rather than a Firefox a11y engine bug (in which case we might have to move this bug elsewhere), but I need to investigate to figure out what's going on to be sure.
Comment 3•4 years ago
•
|
||
(In reply to elliottabarnes from comment #0)
Upon pressing the hotkeys to open a new tab, NVDA immediately speaks the word "alert" - rather than the usual text that would typically be output when opening a new tab
While NVDA does spuriously say "alert", it should then continue to read the rest of the info (because NVDA 2019.3 and later interrupt speech for alerts but then continue reading whatever was interrupted). This is what I'm seeing here. Is that not what you're seeing? If not, what speech synth are you using?
| Reporter | ||
Comment 4•4 years ago
|
||
This is exactly what I'm seeing too - apologies for the lack of clarity on this.
Updated•4 years ago
|
Comment 5•2 years ago
|
||
Elliott, are you still abel to reproduce this? I can't here.
Comment 6•2 years ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:Jamie, since the bug has recent activity, could you please find another way to get the information or close the bug as INCOMPLETE if it is not actionable?
For more information, please visit BugBot documentation.
Updated•2 years ago
|
Description
•