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
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Lucy Greco
> Sent: Monday, April 18, 2016 2:37 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] keyboard accessibility (WCAG) vs keyboard shortcuts?
>
> intresting i wonder why jaws added twitter key commands the ones that twitter uses work grate so what whould these key commands be and do that twitter is not already doing
>
> Lucia Greco
> Web Accessibility Evangelist
> IST - Architecture, Platforms, and Integration University of California, Berkeley
> (510) 289-6008 skype: lucia1-greco
> http://webaccess.berkeley.edu
> Follow me on twitter @accessaces
>
>
> On Mon, Apr 18, 2016 at 11:19 AM, Jonathan Cohn < <EMAIL REMOVED> >
> wrote:
>
>> JAWS 16 and 17 started providing this type of functionality with
>> Twitter and a couple other sites. I believe I heard Facebook call it
>> Web Application Accessible Keys. In JAWS you can get a list of the
>> keys that the web page has overridden default behavior and alsso get
>> shift-1 functionality to speak explanations of the key.
>> Best wishes,
>>
>> Jonathan Cohn
>>
>>
>> On 18 April 2016 at 13:54, Bruno, Michele
>> < <EMAIL REMOVED> >
>> wrote:
>>
>>>
>>> Hello Fellow Advocates,
>>> I have had multiple recent requests asking about "keyboard shortcuts
>>> for accessibility" we have in our web applications. I searched WCAG
>>> again
>> just
>>> in case I missed something and only see reference to keyboard
>>> accessibility; users should be able to navigate/interact with web
>>> pages solely with standard keyboard navigation. I get this. Other
>>> than WebAIM
>>> reference: Keyboard shortcuts are a standard accessibility feature
>>> of
>> most
>>> operating systems. Beyond this, and/or possible mis-understanding of
>>> keyboard (accessibility) vs keyboard shortcuts (OS standards), is
>>> there something more to be aware of?
>>> Thank you in advance.
>>> >>> >>> archives at http://webaim.org/discussion/archives
>>> >>>
>> >> >> archives at http://webaim.org/discussion/archives
>> >>
> > > > > > >