W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2004

RE: [techs] Skip navigation techniques

From: John M Slatin <john_slatin@austin.utexas.edu>
Date: Thu, 17 Jun 2004 08:35:33 -0500
Message-ID: <C46A1118E0262B47BD5C202DA2490D1A0183B1DF@MAIL02.austin.utexas.edu>
To: "Maurizio Boscarol" <maurizio@usabile.it>, "Jim Thatcher" <jim@jimthatcher.com>
Cc: "WAI GL (E-mail)" <w3c-wai-gl@w3.org>

Terrific work, Jim!

To Roberto Scano: Thanks for pointing out that the name attribute for
the anchor element has been disallowed in XHTML 1.1. Do you recommend
using a different attribute that would serve the same purpose?

And about navigating by header: IE doesn't support this, but I think
both Opera and Mozilla do provide single keystrokes for navigating from
heading to heading.I'm not sure about this and can't check reliably,
since JAWS doesn't support either Mozilla or Opera.  And I'm not sure
about other browsers.  But I raise the point because people with low
vision, limited use of their hands, etc., aren't restricted to IE to the
same degree as people using screen readers.

John


"Good design is accessible design." 
Please note our new name and URL!
John Slatin, Ph.D.
Director, Accessibility Institute
University of Texas at Austin
FAC 248C
1 University Station G9600
Austin, TX 78712
ph 512-495-4288, f 512-495-4524
email jslatin@mail.utexas.edu
web http://www.utexas.edu/research/accessibility/


 



-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On
Behalf Of Maurizio Boscarol
Sent: Thursday, June 17, 2004 7:11 am
To: Jim Thatcher
Cc: 'WAI GL (E-mail)'
Subject: Re: [techs] Skip navigation techniques



Jim Thatcher wrote:

>1. Skip Navigation Link
>
>The link should be at or very near the top of the page; it is a link 
>with a local target just before the beginning of the main content.
>
><!-- at or very near the top of the page -->
><a href="#main">Skip Navigation</a>
><!-- many navigation links -->
><a name="main" id="main"></a>
><!-- beginning of main content -->
>

Just a proposal. Observing many blind user navigating in web page, I 
noted that in some cases they don't use the haders to navigate (it 
depends on the skill in using screen reader, which cannot be assumed), 
and sometimes they use the very same typical navigation strategy: skip 
to content, listen to the content, examinate the contextual links at the

beginning and choosing one of them. In other words, they often are 
unaware even of the mere existence of navigation section, if they are 
below the content. If there are many section in the page (secondary 
contents, two or three link sectione, search, login, newsletter 
subscriptions, etc) , they will never notice them, even if they navigate

a lot in the site.

To avoid this "structural blindess" may be useful a paragraph such this 
at the very begin of the body part of the document:

<p>Skip to: <a href="#content">Main content</a> | <a 
href="#search">Search Box</a> | <a href="#nav1">Global navigation</a> | 
<a href="#nav2">local navigation</a>...</p>

This also require the <title> tag content to be significant: they 
understand "where they are" from that title, before the <h1> tag.

I agree on the other proposals of jim, especially on the css method of 
hiding by position: absolute; left: -10000... Visibility and display 
should be avoided until user agent will not be able to render them 
properly according to media specification. At the moment it is not 
always the case.

Bye

Maurizio Boscarol
http://www.usabile.it/
Received on Thursday, 17 June 2004 09:35:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:30 GMT