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

Re: Using ARIA to override semantics

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Mon, 21 Mar 2011 23:13:31 +0100
To: Jonas Sicking <jonas@sicking.cc>
Cc: Steve Faulkner <faulkner.steve@gmail.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, Henri Sivonen <hsivonen@iki.fi>, HTML WG <public-html@w3.org>, W3C WAI Protocols & Formats <w3c-wai-pf@w3.org>
Message-ID: <20110321231331628831.c30e933e@xn--mlform-iua.no>
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
Received on Monday, 21 March 2011 22:14:11 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:23 UTC