W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 1998

Re: navigation bars

From: Charles McCathieNevile <charlesn@srl.rmit.EDU.AU>
Date: Fri, 13 Nov 1998 15:27:10 +1100 (EST)
To: Marja-Riitta Koivunen <marja@w3.org>
cc: w3c-wai-gl@w3.org
Message-ID: <Pine.SUN.3.91.981113152209.22316G-100000@sunrise>
To take this in two pieces. If the nav bar is a structure with a class 
then my understanding is that one day CSS will allow us to do pretty 
clever things with it, like keep it as a header or footer to a window 
(like the little "geocities" thing that sits in the window on their 
websites) without making it a big roadblock for people who are not using 
a window.

There are several techniques already used to provide further information 
in a navigation bar which can work well. One is being able to distinguish 
visited from unvisited links (in CSS already) and another is to be able 
to make the current page stand out (usually this is done by making it a 
non-link, and relying on the visual effect, but could be done in an 
accessible way I think)

But these things strike as getting to the priority 4 part of the 
guidelines - the dreaded wish list.

Charles McCathieNevile

On Wed, 11 Nov 1998, Marja-Riitta Koivunen wrote:
> What I really would like to have is a navigation bar that is always
> available to the user at a consistent place in each page and which highlighs
> the current selection. The highlighting tells the user immediately where he
> is at that site (what he selected earlier) and the navigation bar what the
> other higher level topics are. This is important for orienting every user.
> With blind users I think it is even more important: you can directly go and
> hear the higher level topics without a need to go through every link on a site.
Received on Thursday, 12 November 1998 23:30:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:28 UTC