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

Re: Using ARIA to override semantics

From: Sam Ruby <rubys@intertwingly.net>
Date: Mon, 21 Mar 2011 08:57:54 -0400
Message-ID: <4D874B52.9060604@intertwingly.net>
To: Henri Sivonen <hsivonen@iki.fi>
CC: HTML WG <public-html@w3.org>, W3C WAI Protocols & Formats <w3c-wai-pf@w3.org>
On 03/21/2011 06:51 AM, Henri Sivonen wrote:
> On Sun, 2011-03-20 at 06:28 -0400, Sam Ruby wrote:
>
>> Even better, can you propose specific text which would clarify the
>> situation?
>
> Sure:
>
> - -
>
> The presence of ARIA attributes in a document SHOULD NOT have observable
> effects in user agents compared to the absence of the attributes beyond
> what is exposed to assistive technologies and the effects that generally
> arise from having any attributes present in the DOM (the attributes
> being available via getAttribute, etc., and attribute selectors matching
> on the attributes' presence in the DOM). In particular, the presence of
> ARIA attributes MUST NOT affect CSS pseudoclass matching and SHOULD NOT
> affect user interface modalities that don't use assistive technologies.
>
> - -
>
> If the above paragraph is something that the PFWG does not mean, I think
> discussing what *is* meant by the PFWG definitely needs further
> discussion.

Thanks!  To be clear, I am not endorsing the specific suggestion, but 
the overall approach to quickly converge on spec clarity.

- Sam Ruby
Received on Monday, 21 March 2011 12:58:31 UTC

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