Re: (Image)Maps in XHTML 2

> Many web authors use image maps. But image maps are only presentational as
> they link *different regions of a picture* to other ressources. So, they
> are binded to the presentation of the picture. As presentational they
> shouldn't be represented directly in XHTML 2.

<snip />

<< Provide a text equivalent for every non-text element (e.g., via "alt",
"longdesc", or in element content). This includes: images, graphical
representations of text (including symbols), image map regions, animations (e.g.,
animated GIFs), applets and programmatic objects, ASCII art, frames, scripts,
images used as list bullets, spacers, graphical buttons, sounds (played with or
without user interaction), stand-alone audio files, audio tracks of video, and
video. [Priority 1] >>

(See <>)

I know what you mean, but I have to pronounce the importance of alternative
linkage when you use image maps (according to all I learnt about
Accessibility and Usability). This (WAI conformity) IMO implies a) a softer kind of
'binding' as you mentioned before (because all links or actions are not only
related to the picture), and b) you should offer alternatives integrating any
other type of media map, too.

Related to the presentational meaning of image maps I fully agree.

 Jens Meiert.

Jens Meiert

Steubenstr. 28
D-26123 Oldenburg

Telefon +49 (0)441 99 86 147
Telefax +49 (0)89 1488 2325 91
Mobil +49 (0)175 78 4146 5

eMail <>
Internet <>

Received on Thursday, 22 May 2003 02:48:51 UTC