W3C home > Mailing lists > Public > wai-xtech@w3.org > February 2009

Re: ARIA style sheet

From: Anne van Kesteren <annevk@opera.com>
Date: Tue, 24 Feb 2009 04:40:18 +0100
To: "Chris Blouch" <chris.blouch@corp.aol.com>, "James Craig" <jcraig@apple.com>
Cc: "'W3C WAI-XTECH'" <wai-xtech@w3.org>
Message-ID: <op.upt65gau64w2qv@annevk-t60.oslo.opera.com>
On Mon, 23 Feb 2009 21:24:49 +0100, Chris Blouch  
<chris.blouch@corp.aol.com> wrote:
> I think Matt Machell wasn't saying so much that role:slider was a style
> but that we should embrace using something like CSS selectors to map one
> or more DOM nodes to one or more sets of ARIA attributes. Call it a
> shorthand way to add semantics. If I have 20 sliders and each one is a
> constructed by a <div class="slider"></div> it seems systemically wrong
> to have to put in all the ARIA attributes inline repeatedly whether by
> hand or via a dom walking script. We should have a means to infer the
> applicable ARIA semantic attributes from the already stated class or
> other other fingerprints defined by the selector. Maybe the problem is
> folks call them CSS selectors when really they could be used for broader
> purposes. Imagine all the handy stuff the selector cascade process could
> do to auto-generate appropriate ARIA markup for the same generalized
> chunk of HTML based on the context of its location in the DOM. All those
> joys and challenges of specificity could be made to work for ARIA as  
> well.

XBL 2.0 will allow that. ETA unknown.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Tuesday, 24 February 2009 03:41:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 13:16:01 GMT