W3C home > Mailing lists > Public > public-html@w3.org > April 2011

(unknown charset) Re: False aria-describedby expectations in ARIA Authoring Practices (longdesc)

From: (unknown charset) Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Mon, 25 Apr 2011 21:50:35 +0200
To: (unknown charset) Steve Faulkner <faulkner.steve@gmail.com>
Cc: (unknown charset) mjs@apple.com, jonas@sicking.cc, cooper@w3.org, clown@alum.mit.edu, wai-xtech@w3.org, public-html@w3.org, schwer@us.ibm.com, dbolter@mozilla.com
Message-ID: <20110425215035033936.11c7526d@xn--mlform-iua.no>
Steve Faulkner, Sat, 23 Apr 2011 15:20:46 +0100:
>> Does NVDA need that the browser provides more longdesk access than  
>> Opera and iCab does? Is that technically enough? Or is their stance 
>> political?
> 
> from recollection they thought access via a context menu was fine, but
> would need the image to be focusable so users could access the context
> menu (note this is the same requirement for any keyboard user.

Could you explain the need for keyboard focus a bit more more? E.g. 
does it only mean that one should be able to jump to an image with a 
@longdesc via the tabulator key? Then, imagine a page with 10 images 
were only one of them has longdesc: does it make sense to be able to 
jump to only that single image? Can't the keyboard focus be achieved by 
via @tabindex instead?

I have not checked what the spec says about @tabindex, but a value of 
"0" (tabindex="0") seems to make an element without lifting out of the 
natural focus order.

Leif Halvard Silli
Received on Monday, 25 April 2011 19:51:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:28 GMT