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

Re: Map element read by screen readers

From: Charles McCathieNevile <charles@w3.org>
Date: Fri, 31 Aug 2001 07:26:44 -0400 (EDT)
To: David Woolley <david@djwhome.demon.co.uk>
cc: <w3c-wai-ig@w3.org>
Message-ID: <Pine.LNX.4.30.0108310722340.12237-100000@tux.w3.org>
HTML 4 introduced the concept of the map element as a general method for
grouping links. This was reinforced in HTML 4.01 when it was changed to allow
what already worked - text links and area elements being mixed (for backwards

You are correct about hte name attribute being required, although this
probably would have changed if we had done an even better job.

If the map element contains block content, and not just area elements, then
it should be rendered by graphical browsers, and the only one I know of that
didn't is amaya, where it is a registered bug that may have been fixed now.


Charles McCN

On Fri, 31 Aug 2001, David Woolley wrote:

  > <map title="section navigation">

  This is invalid HTML, reflecting the fact that you are abusing the MAP
  element.  MAP is required to have a name attribute, because it only
  makes sense in the context of a USEMAP.  You also are in violatin of
  a *should* requirement on the A elements; the syntax of SGML doesn't
  really allow the DTD to enforce the requirement that A elements specify

  > <A HREF="page1.htm">Topic 1</A> |

  Map is not a general means of grouping links, but specifically for
  image maps.  A graphical browser, with images on, will not render it.

Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI    fax: +1 617 258 5999
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Friday, 31 August 2001 07:26:55 UTC

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