Firefox - Accessibility: Right-Click Context Menu for the Search Bar not automatically Recognised by the NVDA Screen Reader
Categories
(Firefox :: Disability Access, defect)
Tracking
()
People
(Reporter: elliottabarnes, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
Tested with NVDA 2019.1 and Firefox 69 X64 on Windows 7 X64.
To reproduce:
-
Open a new window/tab, and navigate to the Search Bar - this assumes that you have both the Address and Search Bars shown separately
-
Either hit F10 or the Applications key to invoke the right-click context menu
Actual results:
NVDA stays silent; the only way to tell that the context menu has actually been opened is to cursor down once, at which time the first option in the list is automatically output.
Expected results:
It'd be useful if NVDA could automatically recognise that a menu has been triggered, and announce this accordingly. I'm not actually sure if this has ever worked, but logging either way; if it's felt that this is more of an NVDA issue rather than Firefox, happy to relog with NV Access.
Comment 1•5 years ago
|
||
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Indeed, I can confirm that the context menu is not automatically recognized, on the latest Nightly or Firefox 69.0.1, when invoked in the Search bar or even the navigation bar. Not sure though what the right behavior should be in this case. I'm setting a component to this bug and hopefully, someone with more knowledge in this area will take a look over.
Comment 2•5 years ago
|
||
This is actually a long-standing issue, and I think we have a bug on file for it somewhere already, but I can't find it.
Question for Asa, who is the product manager for accessibility: Are there plans to deprecate the separate search box at some point? It is no longer enabled for new profiles anyway, and all functionality is provided (and accessible) in the new URL bar.
Also NI'ing Jamie for prioritization and thoughts.
Comment 3•5 years ago
|
||
The same bug exists in the main address bar; this is not specific to the search bar. I'm pretty sure the underlying cause is the same.
Description
•