css3-selectors Summary of Comment

The Protocols and Formats Wg has the following comments regarding
Selectors Level 3 last call at
http://www.w3.org/TR/2009/WD-css3-selectors-20090310. PF thanks Cynthia
Shelly of Microsoft for leading our review of this draft, and we
apologize for our late response to this last call.


We ask that there be support for ARIA states and properties [1] as pseudoclasses.  Many of these are similar to things that are currently supported as pseudoclasses, in that they can be set in multiple ways.  For example, "checked" can be set from an HTML attribute, from aria-checked, or by user action.  It is useful for a CSS author to be able to style all checked things the same, regardless of how they came to be checked.   Ask whether the CSS WG thinks it's better to make that part of the selectors spec, part of the ARIA spec, or something else.  Is there an extensibility mechanism for psudoclasses.

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.

::before and ::after may offer a work-around to accessibility issues
with generated content not being in the DOM.  PFWG thinks this is a
useful feature and wants to see it supported.

What was the ::selection pseudo-element, and why was it removed?  From
its name it seems it could be quite useful for ARIA-based applications,
which manage their own selection.

Janina Sajka,	Phone:	+1.202.595.7777;
Partner, Capital Accessibility LLC	http://CapitalAccessibility.Com

Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada
Learn more at http://ScreenlessPhone.Com

Chair, Open Accessibility	janina@a11y.org	
Linux Foundation		http://a11y.org

Chair, Protocols & Formats
Web Accessibility Initiative	http://www.w3.org/wai/pf
World Wide Web Consortium (W3C)

Received on Friday, 8 May 2009 00:03:06 UTC