nvaccess / nvda

NVDA, the free and open source Screen Reader for Microsoft Windows
Other
2.08k stars 626 forks source link

Request: Mouse hover states shortcut key (and current setting) #10319

Open TechHorseG opened 4 years ago

TechHorseG commented 4 years ago

Feature request: When mousing over the settings on an option screen, also include the shortcut key amongst what is read out.

I will often hover over a few sections until I hear the one I want to interact with, such as, for example, the pitch settings for your NVDA voice. But I then have to go the long way around, tab-tab-tabbing to get to that control in order to discover that the shortcut key was alt+e (for example). Whereas if I had been told alt+e on the initial mouse hover I could get there straight away.

Also useful would be for the mouse hover to reveal the current setting of that setting. EG state whether the checkbox is checked.

josephsl commented 4 years ago

CC @feerrenrut

From: TechHorseG notifications@github.com Sent: Thursday, October 3, 2019 11:20 AM To: nvaccess/nvda nvda@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [nvaccess/nvda] Request: Mouse hover states shortcut key (and current setting) (#10319)

Feature request: When mousing over the settings on an option screen, also include the shortcut key amongst what is read out.

I will often hover over a few sections until I hear the one I want to interact with, such as, for example, the pitch settings for your NVDA voice. But I then have to go the long way around, tab-tab-tabbing to get to that control in order to discover that the shortcut key was alt+e (for example). Whereas if I had been told alt+e on the initial mouse hover I could get there straight away.

Also useful would be for the mouse hover to reveal the current setting of that setting. EG state whether the checkbox is checked.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/10319?email_source=notifications&email_token=AB4AXEBLMR5YLGHK2JEUTTDQMYZTFA5CNFSM4I5GRJVKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HPPJF6A , or mute the thread https://github.com/notifications/unsubscribe-auth/AB4AXEHSSEN7QFAUISHMD5DQMYZTFANCNFSM4I5GRJVA .

JulienCochuyt commented 4 years ago

@TechHorseG: If I'm not wrong, these are called "accelerator keys" rather than shortcuts, as the shortcut is indeed alt+accelerator or alt+shift+accelerator depending on the context.

As originally stated in https://github.com/nvaccess/nvda/issues/10317#issuecomment-538030967 I would be in favor of trying to implement this not only for the NVDA GUI, but rather more generally for every GUI we can retrieve the information for, including web pages.

For web pages, the information is already announced when reviewing a node either in browse or focus modes. No doubt we can alter the mouse tracking to announce it as well.

For other GUIs, does anyone know if and how this information can be retrieved using IAccessible2 and UIA?

TechHorseG commented 4 years ago

Thanks for response. If I could extend this request for what is read under the mouse pointer.

  1. If it is an option in a dialogue box, state what the option is set to. For example, in the find dialogue in notepad if I hover over where I know the Match case option to be, it just says "Match case". Whereas if I tab there it'll say "Match case checkbox not checked alt+c". It would be useful if the mouse hover told me everything in the latter statement, as I would quickly have everything I need to know.

  2. It would be useful if when in Browse Mode, mouse hover also told you what the element is (landmark, heading, level etc). For example in Google if I hover over a result it will just tell me the text of that result. Whereas if it told me that this result was "heading level 3" I could know straight away that 3 is the key likely to move between the search results.

Another example is Amazon. I can see the list of results of a search but again its a case of tryingh various browse mode keys before discovering that its results list corresponds to heading level 2. Again, if hovering the mouse over the first result told me heading level 2, I would know straight away that "2" is the key to use to move through the search results.

Thanks. This sort of thing would help productivity for those who can see enough to use the mouse to quickly 'get them started'' , but then like to take advantage of keyboard controls. These ideas would much help in terms of 'bridging the gap'.