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

Re: Using ARIA to override semantics

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Mon, 21 Mar 2011 13:46:45 -0700
Message-ID: <AANLkTi==-PBfYkuJorGf_zO_Wv7KccSaaQLNLiVoieMY@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Henri Sivonen <hsivonen@iki.fi>, HTML WG <public-html@w3.org>, "W3C WAI Protocols & Formats" <w3c-wai-pf@w3.org>
thanks tab,

that doesn't happen and agree it shouldn't happen.

aren't the CSS hooks based on the tag/attribute names etc in the DOM?

you can have styles associated using the aria attribute names, but
that has nothing to do with their function only that they are
recognised bits in the DOM right?

so you can do
a[role] {
color : red ;
}


but that is no different from doing

a[hreflang] {
color : blue ;
}

the semantics of the attribute makes no difference right?

or is use of role/aria-* soemthing that should not be allowed?


regards
stevef


On 21 March 2011 13:20, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> On Mon, Mar 21, 2011 at 1:11 PM, Steve Faulkner
> <faulkner.steve@gmail.com> wrote:
>> hi henri,
>>
>> "In particular, the presence of
>> ARIA attributes MUST NOT affect CSS pseudoclass matching"
>>
>> can you provide a code example that illustrates this?
>>
>> I am having problems wrapping my head around what you mean.
>
> For example, role=link making an element match :link, or aria-invalid
> making an element match :invalid.
>
> ~TJ
>



-- 
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 20:47:37 UTC

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