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

RE: Invisible "Skip navigation" link

From: Charles McCathieNevile <charles@w3.org>
Date: Wed, 31 Jul 2002 11:18:15 -0400 (EDT)
To: "Richwine, Brian Lee" <brichwin@indiana.edu>
cc: Steve Vosloo <stevenvosloo@yahoo.com>, WAI IG <w3c-wai-ig@w3.org>
Message-ID: <Pine.LNX.4.30.0207311113560.2128-100000@tux.w3.org>

well, the point is that in anything but the very short term we can expect
browsers to do smart things with accesskeys on their own. iCab makes
available the accesskeys visually (it is only accessible to people who can
see - sigh) as does my telephone browser. A voice based system might choose
to re-map the accesskeys, so the title information (at best only potentially
available anyway, and then only when you know what the object is) seems
redundant for the most part.

(I prefer to have navigation links grouped in a map element, and then you
know exactly what you skip. HTML 4.01 was even revised specifically to make
this work better. Lynx implements it very nicely, but I don't know how many
other browsers do - iCab doesn't seem to allow tabbing beteween links
unfortunately :(

cheers

Charles

On Tue, 30 Jul 2002, Richwine, Brian Lee wrote:

>Why wouldn't you use something like:
>
><a href="#content" title="To Skip Navigation use Access key 2. ">
>
>It seems like this would help relate which access key goes with each statement.
>
>-Brian
>
>-----Original Message-----
>From: Charles McCathieNevile [mailto:charles@w3.org]
>Sent: Tuesday, July 23, 2002 1:43 PM
>To: Steve Vosloo
>Cc: 'WAI IG'
>Subject: RE: Invisible "Skip navigation" link
>
>
>
>Yep, that's what I would do.
>
>cheers
>
>Chaals
>
>On Tue, 23 Jul 2002, Steve Vosloo wrote:
>
>>
>>So, you'd use a full stop (or some other punctuation) AND a space, e.g.
>>
>><a href="#content" title="Skip Navigation. Access key = 2. ">
>>   Skip Navigation
>></a>
>><a href="1.htm" title="Blah blah. Access key = 3. ">
>>   Blah blah
>></a>
>>
>>Sounds like: Skip Navigation. Access key = 2. Blah blah. Access key = 3.
>>
>>As opposed to: Skip Navigation. Access key = 2.Blah blah. Access key =
>>3.(which is gonna sounds real bad!)
>>
>>
>>
>>
>>-----Original Message-----
>>From: Charles McCathieNevile [mailto:charles@w3.org]
>>Sent: 23 July 2002 04:09 PM
>>To: Simon White
>>Cc: Steve Vosloo; WAI IG
>>Subject: RE: Invisible "Skip navigation" link
>>
>>
>>Spaces are usually there to provide appropriate presentation - ensure
>>that the last word of a text alternative isn't run together with the
>>first word following - this makes it easier to read, or understand when
>>spoken by a screen reader.
>>
>>Thanks to Simon for having some history available for the repeats of
>>discussion.
>>
>>cheers
>>
>>Chaals
>>
>>>-----Original Message-----
>>>From: Steve Vosloo [mailto:stevenvosloo@yahoo.com]
>>>Sent: 23 July 2002 14:32
>>>To: WAI IG
>>>Subject: Invisible "Skip navigation" link
>>>
>>>
>>>
>>>What is the best way to code an invisible Skip Nav link?
>>>
>>><a href="#content">
>>>    <img src="spacer.gif" alt="Skip navigation." width="1" height="1"
>>>border="0"> </A>
>>>
>>>Does the <A> need a title with "Skip navigation." link too?
>>>
>>>
>>>And while I'm here, does anyone know why many examples for accessible
>>>links provide a space after a description? And around an "=" sign, e.g.
>>>
>>><a href="#content" accesskey="2" title="Skip Navigation. Access key =
>>>2. ">
>>>    Skip Navigation
>>></a>
>>>
>>
>>
>
>

-- 
Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI  fax: +33 4 92 38 78 22
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Wednesday, 31 July 2002 11:18:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:05 GMT