WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: keyboard accessibility (WCAG) vs keyboard shortcuts?

for

From: Sean Murphy
Date: Apr 19, 2016 12:43AM

I am thinking you are asking about keystrokes that are built into the web page which are not related to the standard keystrokes for browsers. For example, safari o'rielly provides the user the ability to jump to the next or previous section by using a keyboard shortcut. Depending on the browser determines what keystrokes you have to use as IE and Firefox uses slightly different keys when this methodology is used.

Personally I don't think this is best practise based upon what everyone else has stated and from my personal usage of page via the keyboard. Other users like it because they feel it increases their productivity on a tool.

Jaws included the options because of keyboard conflicts. If WCAG 2.0 doesn't include this, then should it?

Sean
> On 19 Apr 2016, at 5:38 am, Marc Solomon < <EMAIL REMOVED> > wrote:
>
> To clarify John's comments, at least two Windows screen readers that I am aware of have created a special mode that allows certain keys to be ignored by the screen reader while Browse mode/virtual cursor is enabled. This allows the user to have the best of both worlds. They can use commands available in the screen reader for virtual navigation (e.g. move by line with Up and Down Arrow, headings with H, buttons with B, links with L) and at the same time use the web applications keyboard shortcuts without conflicts. I recorded a webinar a few months back with Matt King from Facebook where we discussed our collaboration and demonstrated this functionality.
>
> Regards,
> Marc
>
>