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

Re: proposal for wording re: grouping links (WCAG techniques document)

From: Nir Dagan <nir@nirdagan.com>
Date: Mon, 30 Aug 1999 13:55:26 -0400
Message-Id: <199908301754.NAA10904@dark.brown.edu>
To: Wendy A Chisholm <chisholm@trace.wisc.edu>, w3c-wai-gl@w3.org
Just a small technical thing. In the HTML DTD, the "name" attribute 
is required for the map element, and is omitted in the example.
(The rational was that map is used with an image that references it.)

Regards,
Nir.


At 10:40 AM 8/30/99 -0500, Wendy A Chisholm wrote:
>Hi,
>
>I am responding to Charles' (CMN), Marja's, and Al's comments in this
message.
>
>CMN::
>>Sounds OK to me, except that <map>....</p> needs to be changed in the
>>example.
>>
>oops.
>
>CMN::
>>Actually I would suggest that we review our examples and make them into
XHTML
>>examples, or provde equivalent XHTML examples, in the event that XHTML
>>becomes a recommendation.
>>
>I followed the "HTML Compatibility Guidelines"  within the XHTML spec
>[available at http://www.w3.org/TR/xhtml1/#guidelines] to modify the
>example.  Let me know if I've missed something.
>(end of CMN:: comments)
>
>Per the comments received, the following text is proposed for section
>4.6.1.  Note that in considering Al's suggestions, proposed text for
>sections 3.5 (navigation) and 3.11 (validation) will follow in a separate
>e-mail.
>
>Marja said that the first link took up too much visual space.  I actually
>made it longer because until people get used to it, "bypass navigation bar"
>does not give much information about where that link goes.  So, I added a
>short phrase.  I also called it "skip" rather than "bypass" in hopes of
>making it easier to understand.  I also added  the number of links in the
>navigation bar to the "title" of the MAP to give the user some idea of how
>many links they are missing.  This will help them gauge the consistentcy of
>use of this element between pages.
>
>I like Al's suggestion that if someone wants to hide it they can use a one
>pixel image.  This is similar to the "invisible d-link." Although it is
>kind of hack, if people are tabbing through links they will get to it. If
>it is hidden with a style sheet it won't be in the tab order. 
>
>Another option is to use something short like "D" with the "title"
>attribute on the link.  I think we need to wait until UAs are making the
>"title" attribute available consistently, and heck, by then they'll
>probably be happily skipping around block content and we won't need that
>first link anyway!  <grin>
>
>
>
>Here's the revised proposal:
>
> 4.6.1 Grouping and bypassing links 
> 
> When links are grouped into logical sets (for example, a navigation bar
>that appears on every page in a site) they should be marked up as a unit.
>Navigation bars are usually the first thing someone encounters on a page.
>For users with speech synthesizers, this means hearing the same links on
>every page before reaching the interesting content of a page. Other
>keyboard users, such as some users with physical disabilities, will have to
> tab through all of these links to reach links further down the page. Note:
> this is not true for all browsers. 
> 
> We suggest using the MAP element with the "title" attribute to group and
>label the links. There are a number of techniques that may be used to allow
>users to jump past  the group of links. 
> 
>1. The first link in the group skips over the set of navigation links  when
>selected. 
>2. Provide a style sheet that allows users to hide the set of navigation
>links. 
>3. Provide a script that shows or hides the set of navigation links as
>desired by the user. 
> 
> The first option seems to be most backwards and forwards compatible. The
>other two options are not as backwards compatible  and will hopefully not
>be necessary in the future as we anticipate that user agents will allow
>users to skip over structural block elements such as  MAP or DIV. 
> 
> Example. 
> 
> In this example, the MAP element groups a set of links. The "title"
>attribute gives it a human readable label, which may be anything from
>"Credits," "QuickLinks around 
>our site." The "class" attribute identifies  the group as a navigation bar
>(e.g., for style sheets). The link at the  beginning of the group  links to
>the anchor after the group.  This link will not be necessary once user
>agents allow users to jump over block content.
> 
>     <HEAD>
>     <TITLE>How to use our site</TITLE>
>     </HEAD>
>     <BODY>     
>       <MAP title="Site-wide navigation bar - 12 choices" class="nav">    
>         [<A href="#how" title="Bypass the links you have seen on every
>other page and get right to the content.">Skip navigation bar.  Go to "how
>to use this site."</A>]
>         [<A href="home.html">Home</A>]
>         [<A href="search.html">Search</A>]
>         [<A href="new.html">New and highlighted</A>]
>         [<A href="sitemap.html">Site map</A>]
>         [ ... 8 other links ....]
>       </MAP>     
>       <H1><A name="how" id="how">How to use our site</A></H1>
>     <!-- content of page -->     
>     </BODY>     
>  
>  End example.
> 
===================================
Nir Dagan
Assistant Professor of Economics
Brown University 
Providence, RI
USA

http://www.nirdagan.com
mailto:nir@nirdagan.com
tel:+1-401-863-2145
Received on Monday, 30 August 1999 13:54:37 GMT

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