WebAIM - Web Accessibility In Mind

E-mail List Archives

RE: (no subject)

for

From: Christian Heilmann
Date: May 6, 2005 7:13AM

>>>If anyone could assist it would be most appreciated.
>>
>>> >
>>> >
>>> > It would be more helpful to also see the HTML itself.
>>> > On a more general note: how does this relate to accessibility?


Looking at the code, it relates insofar as there is no thought
whatsoever about users without JavaScript.

<tr onMouseover="this.bgColor='#e8eeff'"
onmouseout="this.bgColor='#FFFFFF'"><td><a class=a3
href="javascript:void(0)" id="1" name="1" onclick="pframe('1')" >Cape
Town</a></td></tr>

Is so bad it is almost funny.

Granted, maps are hard to make accessible, as they are a visual aid
and you cannot possibly write a textual replacement, but this is so
wrong, listing the errors would take longer than just pointing at
better examples.

I especially resent the right click protection, which must be the most
useless and obtrusive scripting idea ever.

To make this monster a lot cleaner:

1) Either add all maps to the document and link them via an anchor and
write a JS to hide them all onload but only show the one that relates
to the current link.
2) Write a backend script that reloads the page and loads the
different maps and add a JS to simply change the src of the one image
onclick of the links in the list. That way it will work for
non-scripting users and prevent scripting users from reloading.

-- Chris Heilmann
Blog: http://www.wait-till-i.com
Writing: http://icant.co.uk/
Binaries: http://www.onlinetools.org/