W3C home > Mailing lists > Public > www-style@w3.org > October 2000

Ideas for the ACSS module of CSS3

From: Sean Palmer <wapdesign@wapdesign.org.uk>
Date: Sat, 14 Oct 2000 16:44:51 +0100
Message-ID: <001901c035f5$b17701c0$d3dc93c3@z5n9x1>
To: <www-style@w3.org>
Cc: "Ian Hickson" <ianh@netscape.com>
> It might be nice to be able to specify this sort of behaviour in style
> sheets, though I feel it is likely that it will mostly be a matter solely
> of user preference.

Not nice: essential. Let me iterate: this is a WAI thing, not really tied in
completely with ACSS/Aural CSS. The checkpoints clearly state:
13.6 Group related links, identify the group (for user
agents), and, until user agents do so, provide a way to bypass the
group.
[Priority 3]
It then goes on to offer a lot of useless and actually poor HTML
implementations to cover itself. What I am proposing is a CSS solution to
this problem one that denotes a style for a set of grouped links that allows
UAs to render a bypassing mechanism. I cannot verse it simpler than that. It
is not just a good idea, I believe that it is firmly necessary to help
authors comply with the WCAG guidelines.
As stated before, this doesn't just apply to aural browsers, because it
firmly sets a navbar type style to grouped links, or company logos that
don't need to be repeated. I.e. it offers a choice to the user to skip
things that the Author has decided are skippable. It provides authors the
choice of letting UAs know that a certain element is "optional".
The only problem now is how to best implement such a solution!

> There may also be some issues with properties that apply to both media: If
> I set different values for the same property for two media to which the
> document is being rendered synchronously, should the two media receive
> their respective values, or should the media be considered together, so
> that the settings conflict, and the final value is determined by the
> normal cascading rules? I suspect that there may not be a single correct
> answer which applies to all properties.
Yes, part of the reasoning behind the else() descriptor, but this isn't as
clear cut.

Kindest Regards,
Sean B. Palmer
WAP Tech Info - http://www.waptechinfo.com/
Received on Saturday, 14 October 2000 11:45:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:06 GMT