Okay - File Explorer running, folder highlighted. Only difference is shift+F10 "context menu O Open O"
...and mea culpa. I was not pressing the Apps key, but the Windows key, henceforth the "menu search box edit" announcement. When pressing the real Apps key I hear "context menu O Open O" Identical to, and expected, to pressing the shift+F10. Never hear the word "application". Dave Carlson Oregonian, woodworker, Engineer, Musician, and Pioneer ----- Original Message ----- From: Brian Vogel To: [email protected] Sent: Friday, February 05, 2016 08:53 PM Subject: Re: How does JAWS announce your Application/Menu Key versus SHIFT+F10 versus INS+F10? Dave, Thanks for posting this information twice, but now I think it will be a third time based on the above. I want to make sure that you're pressing these in a context where a context menu would be the logical result. Those "unavalable" messages suggest to me that you're in a state where a context menu cannot come into play. So, if folks who wish to participate could have File Explorer or Windows Explorer open and a file or folder selected before trying the key presses that would be helpful. I also think I may add CTRL+SHIFT+F10 to the list and, maybe, drop the INS+F10 depending on how the result changes. I am also not clear whether one will or will not need to do a "Route PC to JAWS" before hitting the key or key sequences, but I think not. One of the big advantages of the application/menu key and SHIFT+F10 when JAWS is not running, is that mouse position does not matter, only PC cursor, which is in sync with the JAWS cursor when doing select in my experience, so I'm thinking no cursor routing will be required. The same is not true for the right mouse click because the mouse pointer must be hovering above the selected item for a right click invocation of the context menu. Anything that avoids reliance on mouse pointer positioning is clearly advantageous. Brian
