- From: Steve Faulkner <faulkner.steve@gmail.com>
- Date: Mon, 21 Mar 2011 15:20:04 -0700
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Cc: HTML WG <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
hi leif,
i agree that the presence of a longdes should not make the element
interactive, what has been requested by a screen reader vendor is that
in the case of longdesc being accessed via a context menu the presence
of longdesc will cause the image to be inlcuded in the default tab
order. This is so that users can access the context menu and would be
required for keyboard users in general to be able to access the
context menu.
regards
steve
On 21 March 2011 15:13, Leif Halvard Silli
<xn--mlform-iua@xn--mlform-iua.no> wrote:
> Jonas Sicking, Mon, 21 Mar 2011 14:51:14 -0700:
>> On Mon, Mar 21, 2011 at 1:46 PM, Steve Faulkner wrote:
>
>>> aren't the CSS hooks based on the tag/attribute names etc in the DOM?
>>
>> No. The specs defer to the host language and says things like:
>>
>> "The document language determines which elements are hyperlink source
>> anchors" [1]
>>
>> and
>>
>> "What constitutes an enabled state, a disabled state, and a user
>> interface element is language-dependent" [2]
>
> Just a side note to Steve: If @longdesc would have make <img>
> *interactive*, then img:link{} would select it. Just as that selector
> already selects an img element with a @target attribute. So clearly,
> @longdesec does not make <img> interactive.
>
>> [1] http://www.w3.org/TR/CSS21/selector.html#link-pseudo-classes
>> [2] http://www.w3.org/TR/css3-selectors/#enableddisabled
> --
> leif halvard silli
>
--
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, 21 March 2011 22:20:59 UTC