WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Standardization of Keyboard Shortcuts

for

From: Bim Egan
Date: Jun 27, 2012 7:46AM

Hi Tim,

Have a look at WCAG 2.0 Failure F15, related to Success Criterion 4.1.2:
(Role, State, Value) . The description explains that the accessibility API
must be supported, otherwise:
"assistive technologies will not be able to understand what the control is
or how to operate it ..."
http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/F15

The problem is that the access technology may prompt users to use the Enter
key, which won't work if I understand you arright.

I came across another example of this type of dichotomy in recent testing
where a menu widget had been created, using ARIA, but the JavaScript
restricted access to open menu items to the tab key only. JAWS has a built
in prompt to "use up and down arrow keys" when it encounters an open menu.
The end result is that the user has no idea how to activate the control.

Hope this helps,

Bim

----- Original Message -----
From: "Tim Harshbarger" < <EMAIL REMOVED> >
To: < <EMAIL REMOVED> >
Sent: Wednesday, June 27, 2012 1:42 PM
Subject: [WebAIM] Standardization of Keyboard Shortcuts


>I have a question, but the best way I can think of to ask the question is
>to explain the situation first.
>
> We have a browser-based user interface. Evidently, the only way to
> activate links or buttons in this interface (via the keyboard) is to press
> the spacebar. However, typically in the browser being used, it is the
> enter key that activates links and buttons.
>
> This is definitely a usability problem. However, I am looking for
> information in WCAG or other standards that might point this out to be an
> accessibility problem.
> Any help is appreciated.
>
> Thanks!
> Tim
> Tim Harshbarger
> Accessible Technology Services
>
> > >