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

Re: 3rd try: proposal for marking up groups of links

From: Nir Dagan <nir@nirdagan.com>
Date: Thu, 16 Sep 1999 20:22:04 -0400
Message-Id: <199909170021.UAA29522@vega.brown.edu>
To: thatch@us.ibm.com, Wendy A Chisholm <chisholm@trace.wisc.edu>
Cc: w3c-wai-gl@w3.org
At 05:36 PM 9/16/99 -0500, thatch@us.ibm.com wrote:
>Comments on the proposed reqording.
>Wendy, your rewording included: quote
> ... appears at the top of a page, a user who is reading
>the page through speech synthesis will have to listen to
>all of those links for each page they visit at the site ...
>The example using MAP with block content. 

it is actually only inline content in the example. I think it must be block
in HTML4.0
In anycase <map name="foo"><p>...some links</p></map> should do it.

>I am disappointed to say that:
>1. HPR does not today handle the MAP element with block content. I just
>we did.

what do you mean "does not handle"? does it render the content or not?

>2. Netscape and IE basiaclly ignore the MAP element in this case (your

You mean they render the content, right? That what Netscape4.6, IE5.0,
Opera3.60 and 
Lynx2.8.2 do for me. (I used a <p>..</p> inside the map in my test.)

>3. Amaya does not even render the MAP of your example.

That's a bug in Amaya, (reported already by Charles McCathieNeville to the
Amaya mailing list) but it practicallly doesn't matter since people are
using Amaya 
only as a fifth browser. (people use for authoring, testing pages in yet
browser, etc. It is a testbed browser; not exactly designed for usability 
and mass consumption anyways)

>4. IBM TopPage "corrects" the error and combines the <MAP> and the </MAP>

Didn't get that. Please explain.

>I don't know what to conclude with this.

The conclusion is that block content in MAP is rendered by quite a lot of
(it would desirable to check also Netscape 3, and IE4 and 3)
on the other hand, realy making an image map out of it is not supported.


>Finally, your examples use the "tradition" of enclosing links in
>square brackets. I think that is now bad advice. It sounds awful
>with speech browsers, and screen readers, and it undermines
>one of the best "skip strategies" in the business, "Skip to next
>non link" available in Window-Eyes.
>Jim Thatcher
>IBM Special Needs Systems
>Wendy A Chisholm <chisholm@trace.wisc.edu> on 09/16/99 01:55:01 PM
>To:   w3c-wai-gl@w3.org
>Subject:  3rd try: proposal for marking up groups of links
>Here's the revised proposal, the first proposal is available at
>the 2nd proposal was at:
>the original text that we are proposing to change is at:
> 4.6.1 Grouping and bypassing links
>When a navigation bar - a set of links that appears on every page
>throughout a site
>highlighting other areas of the site - appears at the top of a page, a user
>who is
>reading the page through speech synthesis will have to listen to all of
>those links
>for each page they visit at the site before they get to new content.
>Other users, such as some users with physical
>disabilities, may have to tab through all of these links to reach links
>further down the page.
>There are several methods that you can use to allow users to quickly pass
>of links (navigation bars, table of contents, etc.) to get to other
>portions of a page.
>In today's browsers, you will need to
>provide a link before the group of links that will take the user to the first
>bit of text after the group of links.  In the future, using structural
>markup like the MAP
>element will allow a user agent to navigate past the group on user command.
>To support both today's
>and tomorrow's browsers, we suggest using the MAP element with
>the "title" attribute to group and label the links, plus a "skip" link
>before the group.
>The "skip" link may be hidden using style sheets or be a 1 pixel image that
>is only
>visible by alt-text when images are not loaded.
>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.
>other options that are not as forward or backward compatible:
>1. Provide a style sheet that allows users to hide the group of links.
>2. Provide a script that shows or hides the set of navigation links as
>desired by the user.
>wendy chisholm
>human factors engineer
>trace research and development center
>university of wisconsin - madison, USA
Nir Dagan
Assistant Professor of Economics
Brown University 
Providence, RI

Received on Thursday, 16 September 1999 20:21:04 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:07:16 UTC