-
Notifications
You must be signed in to change notification settings - Fork 27.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Confusing accessibility help message in an editor #191672
Comments
Yeah, I've wondered about this wording. It means disable the aria hint that told you to open this (the accessible view). Perhaps replacing |
Oh, do you mean that you would user Alt+F6 to disable the aria hint? Maybe it could say that? |
the hint only exists for features which have a corresponding |
In fact, it was a different bug that Joyce was seeing this when she invoked the help dialog in the editor. That was fixed as well. #191722 |
It's not a toggle, rather a one-way action by design as users will almost never want to enable a hint they're familiar with. |
Right, so "Disable the accessibility help for this feature using Alt+F6" |
Accessibility help and verbosity are different things. |
My bad, "Disable the accessibility verbosity for this feature using Alt+F6" The point is that the current text doesn't make clear the connection between the parenthesized text and the directive preceding it |
Oh, for screen reader users, including the keybinding in parenthesis is expected and a recommended practice. It reduces verbosity. |
Then should the preceding sentences in the accessibility help for the chat response follow that pattern, instead of "To do __, invoke the __ command"? |
I thought that would be wordy/redundant: To disable verbosity for this feature, invoke the command Also, unlike the others, this command doesn't appear in the command palette, so it's not important to indicate the command title here IMO. |
It is aligning with the accessible view specific actions like "exit this dialog via the escape key". the spacing there currently looks wrong though (no space, not on its own line) |
I could also tweak that like so for more consistency |
I see your point though. We should improve the consistency here and also probably lessen the redundancy. |
The text was updated successfully, but these errors were encountered: