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

Re: Ideas for the ACSS module of CSS3

From: Sean Palmer <wapdesign@wapdesign.org.uk>
Date: Fri, 13 Oct 2000 16:26:49 +0100
Message-ID: <004f01c0352a$28824b20$18e793c3@z5n9x1>
To: "Robin Berjon" <robin@knowscape.com>
Cc: "Ian Hickson" <ianh@netscape.com>, <webmaster@richinstyle.com>, <www-style@w3.org>
> > > That's why you should put the navigation bar:
> > >    1. in structural markup (not a table)
> > >    2. at the bottom of the file
> >Been there - doesn't work.
> Besides, accessibility will only happen if there's an easy way for the
> average webmaster to make it happen, and a simple CSS line would make it
> much easier than either of your points.

Exactly.

.navbar { play: optional; skip: true; }

Simplicity itself. And when it is applied, visually you could have:-
[home] [mail] [back] ...
to:
[skip] [home] [mail] [back] ...
Or whatever, based on a UA's built in style processor;

And aurally: "Now follows another stupid navigation bar that you've heard a
million times before. To skip this bar, please holler 'aaargh!' now."

Please, CSS WG, take note.

Maybe better:
.navbar { play: optional; allow-skip: true; alt: uri(#intro); }

Kindest Regards,
Sean B. Palmer
WAP Tech Info - http://www.waptechinfo.com/
Received on Friday, 13 October 2000 11:28:52 GMT

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