W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2012

Re: Slides of my WAI-ARIA presentation at SpainJS event

From: Ramón Corominas <listas@ramoncorominas.com>
Date: Mon, 09 Jul 2012 14:13:12 +0200
Message-ID: <4FFACAD8.7090306@ramoncorominas.com>
To: Steve Faulkner <faulkner.steve@gmail.com>
CC: Chaals McCathieNevile <w3b@chaals.com>, WAI Interest Group <w3c-wai-ig@w3.org>
Hello Chaals, Steve and all.

In this case I wanted to illustrate a case where keyboard-specific 
events are needed, since I have to control the up and down keys (the tab 
key will focus the radio-group, not every radio button). I've also 
noticed that the space bar triggered some onclick events, but the 
behaviour was a bit erratic, and aria-labelledby seemed to not work very 
well.

I also noticed that alert role did not work well (or at least not the 
way I expected), so I used the generic "region" instead. All my demos 
where using Firefox 13 and JAWS 13 on Windows XP.

In any case, the idea was to highlight different things to take into 
account when programming, since most JS programmers there didn't know 
anything about accessibility.

Thanks for your feedback!
Ramón

Steve wrote:

>> I think pretty much all browsers allow activating click
 >> events with the keyboard, and will add things if you give them
 >> a tabindex. So adding specific keyboard handling is probably
 >> redundant if you're just using click (mouseover, focus, and
 >> various other things are still not so good).
 >
> I think you are right, but need to take into account keyboard behaviour 
> for things like buttons, which require activation on space key press as 
> well as enter key
Received on Monday, 9 July 2012 12:16:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:13:30 UTC