W3C home > Mailing lists > Public > www-style@w3.org > May 2009

Re: css3-selectors Summary of Comment

From: Andrew Fedoniouk <news@terrainformatica.com>
Date: Thu, 07 May 2009 19:52:49 -0700
Message-ID: <4A039E81.3000701@terrainformatica.com>
To: Ian Hickson <ian@hixie.ch>
CC: Janina Sajka <janina@rednote.net>, www-style@w3.org, W3C WAI Protocols & Formats <w3c-wai-pf@w3.org>
Ian Hickson wrote:
> On Thu, 7 May 2009, Tab Atkins Jr. wrote:
>> On Thu, May 7, 2009 at 7:02 PM, Janina Sajka <janina@rednote.net> wrote:
>>> Hover, active, focus:  All elements should be able to take those 
>>> states. Any element that receives focus should be able to make use of 
>>> those. With ARIA and with HTML 5, any element can be focusable. 
>>>  Before that, form elements and buttons are also focusable.
>> CSS has no say on whether elements match these classes; it's entirely up 
>> to the document language.  The CSS engines just need to know what the 
>> document language wants.  As long as HTML5 and ARIA play nicely together 
>> in this respect, we're great.
> 
> This is the relevant text in HTML5:
> 
>    http://www.whatwg.org/specs/web-apps/current-work/#matching-html-elements-using-selectors
> 
> Once ARIA is integrated with HTML5 (which is pending on getting the 
> implementation requirements pinned down and having the ARIA spec address 
> the last call comments [1]), I would be happy to add to that section the 
> relevant ARIA states if that is the technically correct things to do.
> 
> Having said that, it seems like having the ARIA attributes affect selector 
> matching runs counter to the principles behind the ARIA design. Surely if 
> ARIA is to be treated as an accessibility API, it should not affect lower- 
> level layers like CSS. Otherwise, what should happen if the ARIA-level 
> accessibility API semantics conflict with the actual semantics of the 
> language? It would be like ARIA affecting the form submission or form 
> validation requirements in HTML, or changing the way graphics are rendered 
> in SVG.
> 
> 
> [1] In particular, those listed here:
> http://lists.w3.org/Archives/Public/public-pfwg-comments/2009AprJun/thread.html
> 

CSS is indifferent to the nature of state flags of DOM elements.
List of state pseudo-classes like :visited, :checked, etc. does not
belong to CSS in principle.

That is what Tab Atkins Jr. tried to say as far as I understood.

HTML spec is maintaining list of state flags applicable to HTML DOM 
elements domain and that is perfectly fine. So it is not clear
(at least to myself and Tab Atkins Jr.) why Janina decided to address
this to CSS WG.

-- 
Andrew Fedoniouk.

http://terrainformatica.com
Received on Friday, 8 May 2009 02:53:31 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:18 GMT