Forum Moderators: open
I use Fireworks to create image maps - am I right in thinking that this creates a client-side map?
In the web accessibility guidelines it says
Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map.
It also says similar for server-side maps.
What does this mean in practical terms? What (if anything) do I need to add to the code generated by fireworks? Am I right in thinking that client-side image maps are better than server-side for accessibility purposes?
If anyone can provide some example code that would be great.
Cheers,
H.
am I right in thinking that this creates a client-side map?
yep
provide redundant text links
basically means provide another set of links, linking to the same pages as the imagemap, so people who cannot use/have difficulty with the imagemap can use this secondary set of links.
And should these links be visible, or would it be OK to hide them with css? I guess what I'm asking is are people who have problems with image maps most likely to have css turned off?
[thelearningfederation.edu.au...]
This seems to imply that the main accessibility issues are with server side maps. Assuming you use titles for each area of the map (for screen readers) and the seperate links are available via the keyboard (by tabbing through), you shouldnt have a problem, and the redundant links may be, well, redundant :)
Ben
It seems that the code produced by Fireworks is pretty accessible then.
I was worried there might be lots of work involved here. I can go worry about other stuff now.
Cheers,
H.
