I’m also a developer on the project Andy is referring to. Just to clarify, this
is under .net 4.8 using Winforms. I’ve definitely seen other context menus work
correctly under NVDA, so wonder if this is a winforms issue.
From: program-l-bounce@xxxxxxxxxxxxx <program-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Nate Kile
Sent: January 14, 2022 12:20 PM
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] Re: NVDA, .net context menu
Interesting, not sure if it is even related, but yesterday I was filling out a
form and NVDA would not read the fields as I tabbed through, I had to exit the
form and arrow up to read the label but in JAWS, it could read each field as I
tabbed through.
On Fri, Jan 14, 2022 at 3:22 AM <sonfire11@xxxxxxxxx
<mailto:sonfire11@xxxxxxxxx> > wrote:
Hi,
I am working on a project that requires the use of a system tray context menu.
When the user accesses it with JAWS, everything works as expected. EX: The name
of the context menu is announced, and JAWS reads the first focused item. On the
other hand, NVDA only announces “unknown”. It is then up to the user to press
down arrow to hear the name of the context menu and the first focused item. Has
anyone else seen this type of strange behavior from NVDA?
