Skip to content
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

Some keyboard shortcuts are announced incorrectly by screen readers #9362

Closed
afercia opened this issue Aug 26, 2018 · 2 comments · Fixed by #9582
Closed

Some keyboard shortcuts are announced incorrectly by screen readers #9362

afercia opened this issue Aug 26, 2018 · 2 comments · Fixed by #9582
Assignees
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Type] Bug An existing feature does not function as intended

Comments

@afercia
Copy link
Contributor

afercia commented Aug 26, 2018

See the various issues / PRs related to keyboard shortcuts, for example #9190 and #8316.

Some of the keyboard shortcuts displayed in the UI use non-alphanumeric keys like comma , or minus -. These characters are generally ignored by screen readers as they're considered "punctuation". Screen readers do have a "verbosity" setting to fine-tune the amount of punctuation that will be read out. However, with default settings some punctuation is just ignored.

For example, the shortcut Ctrl+Shift+, is announced as Control plus Shift plus. See below the NVDA speech viewer does show the comma, but it's not read out: it just makes the screen reader pause briefly:

screenshot 59

VoiceOver with Safari is smart enough to read out the cloverleaf symbol as Command but still ignores the comma and the Shift+⌘, is announced as Shift plus Command:

screen shot 2018-08-26 at 13 55 25

Out of curiosity, I've checked what Google Docs does in these cases. Seems that shortcuts with comma, period, semicolon, are announced correctly:

screenshot 60

screenshot 61

Inspecting the source, turns out they just use an aria-label attribute to expand the shortcut to a screen-reader-understandable form:

screenshot 62

They do that for all the shortcuts, even the ones that wouldn't need to be expanded (I guess to simplify things):

screenshot 63

I'd recommend to implement the same solution, as communicating shortcuts in a way that's not understandable to users who benefit the most from them, defeats a bit the purpose of having shortcuts .

Note:
about the + sign used to separate the keys, I've read @jasmussen comment on #9190 (comment) and seen that, for macs, the + sign has been intentionally removed after the Command symbol, see 5b0b00b and following refactoring. However, I think there's a bit of inconsistency right now.

For the mac shortcuts, I understand the choice to not use symbols and always use key names except for but I think it's a bit confusing visually, especially in some cases, see below:

screen shot 2018-08-26 at 16 49 11

I'd tend to think the smart argumentation behind the usage of the + when preceded by the cloverleaf symbol may potentially confuse users. On the other hand, I'd be in favor of not using the + at all for macs as @jasmussen suggested, and always use it on other OSes instead. Would it be possible to simplify a bit and just use a space as separator for macs and a plus for non-macs? For example:

  • mac: Shift Option ⌘ M
  • non-mac: Ctrl+Shift+Alt+M
@afercia afercia added the [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). label Aug 26, 2018
@afercia
Copy link
Contributor Author

afercia commented Aug 26, 2018

About the plus vs. space, noticed @jasmussen used spaces in this mockup 🙂

#7297 (comment)

@afercia
Copy link
Contributor Author

afercia commented Aug 26, 2018

Note: also shortcut keys like Bksp should preferably be expanded to a better understandable word.

@designsimply designsimply added the [Type] Bug An existing feature does not function as intended label Aug 28, 2018
@talldan talldan self-assigned this Sep 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants