E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 3 (In chronological order)

From: Tim Harshbarger
Date: Wed, Jun 27 2012 6:42AM
Subject: Standardization of Keyboard Shortcuts
No previous message | Next message →

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

From: Steve Faulkner
Date: Wed, Jun 27 2012 7:36AM
Subject: Re: Standardization of Keyboard Shortcuts
← Previous message | Next message →

Hi tim

the common keystroke for links in browsers is the enter key.
the common keystrokes for buttons is the enter and space keys.

AT that announce keyboard interaction hints, JAWS for example, will
announce the presence of a button and indicate to use the spacebar to
activate it.
So users expect to be able to use the space key to activate a button.


HTH

regards
steveF


On 27 June 2012 13:42, Tim Harshbarger
< = EMAIL ADDRESS REMOVED = >wrote:

> 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
>
> > > >



--
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html

From: Bim Egan
Date: Wed, Jun 27 2012 7:46AM
Subject: Re: Standardization of Keyboard Shortcuts
← Previous message | No next message

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 ADDRESS REMOVED = >
To: < = EMAIL ADDRESS 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
>
> > >