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: Emmanuelle Gutiérrez y Restrepo <coordina@sidar.org>
Date: Mon, 9 Jul 2012 16:31:03 +0200
Message-ID: <CACusQJiGT=C0vE3tpkSf-FtegO6Yx_gDTEjNWK4ieEjZrtP6MA@mail.gmail.com>
To: Bryan Garaventa <bryan.garaventa@whatsock.com>
Cc: Steve Faulkner <faulkner.steve@gmail.com>, Chaals McCathieNevile <w3b@chaals.com>, WAI Interest Group <w3c-wai-ig@w3.org>, Ramón Corominas <listas@ramoncorominas.com>
Good point Bryan,

"Proper scripting is always necessary to ensure functionality for users
that cannot benefit from ARIA."

It is important to note that, for all developers.

All the best,
Emmanuelle
-- 
Emmanuelle Gutiérrez y Restrepo
Fundación y Seminario SIDAR
URL: www.sidar.org
email: emmanuelle@sidar.org


2012/7/9 Bryan Garaventa <bryan.garaventa@whatsock.com>

> **
> Actually I ran across this not too long ago, where I had a Span tag with
> tabindex=0 and role=link, and tried using just a click event to handle the
> keypress.
>
> This worked fine for screen reader users, but failed completely for
> keyboard only users not using a screen reader.
>
> It's always a good idea to put a key event like keyDown to handle keyboard
> interaction in a redundant manner to ensure accessibility.
>
> The way I explain ARIA to people is that ARIA effects behavior, not
> functionality. Proper scripting is always necessary to ensure functionality
> for users that cannot benefit from ARIA.
>
>
>
> ----- Original Message -----
> *From:* Steve Faulkner <faulkner.steve@gmail.com>
> *To:* Chaals McCathieNevile <w3b@chaals.com>
> *Cc:* WAI Interest Group <w3c-wai-ig@w3.org> ; Ramón Corominas<listas@ramoncorominas.com>
> *Sent:* Monday, July 09, 2012 3:58 AM
> *Subject:* Re: Slides of my WAI-ARIA presentation at SpainJS event
>
> Hi Chaals,
>
> >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
>
> see
> http://www.paciellogroup.com/blog/2011/04/html5-accessibility-chops-just-use-a-button/for more details.
>
> regards
> Steve
>
> On 9 July 2012 11:47, Chaals McCathieNevile <w3b@chaals.com> wrote:
>
>> On Sun, 08 Jul 2012 22:29:30 +0200, Ramón Corominas <
>> listas@ramoncorominas.com> wrote:
>>
>> Hi all, and apologies for cross-posting.
>>>
>>> Last Saturday I gave a presentation in the SpainJS event about creating
>>> accessible apps using WAI-ARIA. The idea was to show JS developers that
>>> accessibility is an essential component to achieve quality coding, and the
>>> potential of ARIA to create more accessible apps.
>>>
>>> I've uploaded the slides here:
>>> http://ramoncorominas.com/**spainjs/<http://ramoncorominas.com/spainjs/>
>>>
>>
>> Nice :)
>>
>>
>> Comments, suggestions or corrections are welcome (smile)
>>>
>>
>> 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'd be interested in learning if that is not the case...
>>
>> cheers
>>
>> Chaals
>>
>> --
>> Chaals - standards declaimer
>>
>>
>
>
> --
> 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
>
>
>
Received on Monday, 9 July 2012 14:31:36 UTC

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