Understanding 2.1.4: Character Key Shortcuts (Level A)

w3c / wcag-eo

Repository for EO editorial work on WCAG

Other

4 stars 7 forks source link

Understanding 2.1.4: Character Key Shortcuts (Level A) #12

Open nrhsinclair opened 5 years ago

nrhsinclair commented 5 years ago

Post issues and possible suggestions here.

a11ycob commented 5 years ago

Minor edits only required

bakkenb commented 5 years ago

Every time I try to access the link for "Accesskeys" in the fourth paragraph, chrome freezes on me and I have to restart the application.

Happening to anyone else?

bakkenb commented 5 years ago

Benefits

Bullet one problem areas in bold/italics: "Speech users will be able to turn off single-key shortcuts so they can avoid accidentally firing batches of them at once. This will allow speech users to make full use of [dictation] programs that offer single-key shortcuts to keyboard users." I am not sure what "firing batches of them at once" means. I think I know, but it is too unclear, especially for anyone that does not even know what speech recognition/dictation software is or does.

Example 2

"A keyboard-only user is in a long issues thread." - this is jargon as I assume it is referring to a github issue thread. Maybe change to "A keyboard-only user is in a long email thread."

Overall

The only other thing is that I feel some editing could be done to shorten the length of this content without changing any meaning of what is presented. It seems long, but maybe that is because they use a lot of text to explain how speech driven software works.

vmmiller commented 5 years ago

I think it should be shortened and possibly, some restructure of a couple of paragraphs. It seems a bit long and windy. Some editing required. Some jargon could be removed. Some comments: first paragraph: is it necessary to keep "inappropriate" 3rd paragraph: is "generally work in a single-mode" necessary? Could it be shortened to "Speech Input users generally use a mix of dictation and speech commands." 3rd paragraph: Is it necessary to state "a user might say a bit of dictation, such as", why not "a user might say aloud "..." - is it important to state "dictation" 3rd paragraph: "all encompassing mode" - a bit of jargon 6th paragraph: don't fully understand the example with "y" Benefits: first bullet point is unclear to me with the "firing"

vmmiller commented 5 years ago

Every time I try to access the link for "Accesskeys" in the fourth paragraph, chrome freezes on me and I have to restart the application.

Happening to anyone else?

No, Brent, it didn't happen to me.

nrhsinclair commented 5 years ago

It does seem to include a good bit of background information, more so than most understanding docs (however, the information does provide additional understanding), feels more like an article, not necessarily a bad thing, since it reads easily :)

Propose revising: current: Single-key shortcuts are the exception. suggest: However, single-key shortcuts are problematic.

current: Speech users will be able to turn off single-key shortcuts so they can avoid accidentally firing batches of them at once. suggest: Speech users will be able to turn off single-key shortcuts so they can avoid accidentally executing shortcuts unintentionally.

nrhsinclair commented 5 years ago

Accesskeys link did not freeze as Brent described, but did take a few moments to load the linked content.

I expected the underlined terms in the Key Terms section to link to definitions, however they did not.