Is your feature request related to a problem? Please describe.
There are several places where a user will press a keystroke which opens a dialog which may not be obvious to all users. Examples are:
NVDA+f pressed twice opens a dialog with the formatting of the current caret location
NVDA+r runs OCR and presents the results in a buffer the user can navigate
NVDA+k pressed twice (from NVDA 2023.1) opens a dialog with the destination URL of the current link.
Where opening something like NVDA settings should (generally) be obvious that the user is in a dialog,, these examples may not be.
Describe the solution you'd like
My suggestion is to append "press escape to close" to the title of these dialogs / the information which is read when the user activates the keystroke.
Describe alternatives you've considered
As it is currently, I think most users work it out, although it may still be confusing at first. I think the proposal wouldn't inconvenience anyone, as the information would be read last and could be skipped / ignored.
Additional context
Suggested during a conversation with user Jared via email.
Is your feature request related to a problem? Please describe.
There are several places where a user will press a keystroke which opens a dialog which may not be obvious to all users. Examples are:
NVDA+f pressed twice opens a dialog with the formatting of the current caret location
NVDA+r runs OCR and presents the results in a buffer the user can navigate
NVDA+k pressed twice (from NVDA 2023.1) opens a dialog with the destination URL of the current link.
Where opening something like NVDA settings should (generally) be obvious that the user is in a dialog,, these examples may not be.
Describe the solution you'd like
My suggestion is to append "press escape to close" to the title of these dialogs / the information which is read when the user activates the keystroke.
Describe alternatives you've considered
As it is currently, I think most users work it out, although it may still be confusing at first. I think the proposal wouldn't inconvenience anyone, as the information would be read last and could be skipped / ignored.
Additional context
Suggested during a conversation with user Jared via email.