W3C home > Mailing lists > Public > public-html@w3.org > June 2008

Other aria representations [was: Re: ARIA as stop-gap]

From: Jim Jewett <jimjjewett@gmail.com>
Date: Thu, 5 Jun 2008 20:09:05 -0400
Message-ID: <fb6fbf560806051709l2236c652ode31f1a9947c5418@mail.gmail.com>
To: "HTML WG" <public-html@w3.org>
Cc: "Leif Halvard Silli" <lhs@malform.no>

Leif Halvard Silli  wrote:

> OTOH <element aria="prefix-value" > would work
> fine with CSS selectors

There may be several aria attributes on a single element.  They could
be space-separated, but that starts to look like a sub-element that
has to be parsed out using a microsyntax. And you need to worry about
line-wrap bugs.

That might be an acceptable cost, *iff* it were worth re-opening the
aria-integration with other working groups and about-to-ship
implemetors.

> If we really want it to be simple for authors to select
> elements based the element's aria values, then a
> *new* selector is needed.

That would be up to CSS selectors.

It might be worth defining some new pseudo-classes, similar to :lang
-- but I'm not convinced.

I suspect that most people will never use any aria-* properties except
for those defined as part of the standard elements' own definitions.
So they'll just style the elements directly.

I suspect that people who do create custom widgets will usually want
different styling for the custom widget than they want for the
standard elements.  (Or why bother to write a custom version?)  If so,
then you only want to capture explicitly declared aria properties, and
the CSS 2.1 attribute selectors are good enough.  I'm betting that CSS
2.1 bugs will be fixed faster than a new function gets implemented.

For those times when common styling really is desirable, a
comma-separated list of selectors is probably still easier than a new
function.

-jJ
Received on Friday, 6 June 2008 00:09:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:18 GMT