W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2004

Re: Fw: FW: Skip navigation in WCAG-2

From: david poehlman <david.poehlman@handsontechnologeyes.com>
Date: Sun, 26 Sep 2004 08:49:03 -0400
Message-ID: <003301c4a3c7$349536b0$6401a8c0@DAVIDPC>
To: "TANAKA Satoko" <sako-t@aprico.fujitsu.com>, <w3c-wai-ig@w3.org>

Hi Satoko

In discussion on this topic in the past, it has been pointed out that using
a clear gif if I understand you correctly and I know that a lot of sites do
this will deny the functionality to those who do not use a mouse but do use
the screen.  Instead of skip nav, you can use go to main content or proceed
to main content or some other variant of going to the next logical linking
structure on the page.  All I would advise re shortcuts is to use regular
links but of course, they may look silly to mouse users who don't need to
"go back to top of page" when they can click there.  So:
"main content", "top of page" and "go to home page" are just a few of my

The wcag does say use clear language and I think this is part of what it
gets at although I've seen a lot of accepted practice out there that uses
"skip nav" "home" "top" "next" "more" and many other variations on the one
word theme.  Think of it this way.  If your links were listed in a liniar
fashion as it is possible to do with some modern uas and assistive
technologies, would they make sense in that context?

Johnnie Apple Seed

----- Original Message ----- 
From: "TANAKA Satoko" <sako-t@aprico.fujitsu.com>
To: <w3c-wai-ig@w3.org>
Sent: Sunday, September 26, 2004 8:22 AM
Subject: Re: Fw: FW: Skip navigation in WCAG-2

Thank you for the suggestion.
I'll put the short cuts on the wab site I'm building.

I have another question.
I would like to ask you what is the best way to implement the short
This is the same issue with the case of skip navigation. (I'm sorry,
but I don't know another suitable name, so I use "skip NAV"

I will apologize if this issue has already been solved.

WAI page is using a GIF file for a skip NAV. Does it mean that you
think that using a GIF file for a skip navigation is the most
suitable way to the actual state?

According to the log of the topic, it seems that you have not yet
reached agreement about the way of implementation.

Using CSS, "display: none", is the most proper way, if you want to
hide a link from visual browsers. However, as you know, this CSS
does not work on some screen readers and audio browsers. Therefore I
think that we do not have any ways except the use of a GIF file in
order to provide a solution for current technology users, even if
the way is not structural and not logical.

I would be very pleased if you would tell me how you think about the


Satoko Tanaka
Fujitsu Aprico Ltd.

"david poehlman" <david.poehlman@handsontechnologeyes.com> wrote:

> I would suggest that since there are many people who are not using world
> class technology that any help you can provide for navigation would be of
> great value.  I would also suggest that in providing this help that you
> words that tell me where I am going to go, not what I am going to skip.
> Thanks!
> Johnnie Apple Seed
> ----- Original Message ----- 
> From: "TANAKA Satoko" <sako-t@aprico.fujitsu.com>
> To: <w3c-wai-ig@w3.org>
> Sent: Saturday, September 25, 2004 4:43 AM
> Subject: Re: Fw: FW: Skip navigation in WCAG-2
> Hello.
> I'm new to this ML.
> I read the log of this topic.
> Can I understand that screen reader users can easily move to a point
> which they want with user agent's functions?
> I'm constructing a website, and planning to provide short cuts to
> go back to the content and the search box. The short cuts appear at
> the end of the page.
> According to the log, however, it seems not to be necessary, if
> users can move easily with UA's functions.
> How do you think about providing these short cuts for the screen
> reader users?
> I would appreciate it if you would tell me your opinions.
> Sincerely,
> --
> Satoko Tanaka
> Fujitsu Aprico Ltd.
Received on Sunday, 26 September 2004 12:47:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:29 UTC