WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: keyboard accessibility (WCAG) vs keyboard shortcuts?

for

From: Chaals McCathie Nevile
Date: Apr 19, 2016 3:50PM

On Mon, 18 Apr 2016 20:37:25 +0200, Lucy Greco < <EMAIL REMOVED> > wrote:

> 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

The problem with twitter keys is that they override things which many
users expect from their browser, so suddenly something unexpected happens
when using a shortcut.

This is an inherent problem with using javascript to implement shortcuts -
as Deborah pointed out elsewhere in the thread.

And a reason why the only kinds of solution I can see working are based on
accesskey - or something that can work the same with a different name,
which seems like a silly idea to me.

cheers

> 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.
>> > >> > >> > >> > >> >
>> >> >> >> >>
> > > > --
Charles McCathie Nevile - web standards - CTO Office, Yandex
<EMAIL REMOVED> - - - Find more at http://yandex.com