Quote:
Originally Posted by Hitch
Are you sure you don't need JS, or at least JSON, etc., for parsing (I know that's not the right term..) the various areas on the map? ??? Are you sure? I know you're a programmer, sweetie. But I could swear that I read something, somewhere in time (far enough back that my ancient brain can't pull it out...) about that. No?
|
Imagemaps are just HTML. No JS or anything about it.
Mozilla's page explains <area>:
https://developer.mozilla.org/en-US/...L/Element/area
It is pretty much just like an <a>, but you define a shape of clickable areas, and then you say "if this location is pressed, do this" (visit the link, jump to this section, etc.).
Although maybe you are thinking about more of the Server-Side methods:
https://en.wikipedia.org/wiki/Image_map#Server-side
... I suspect you could also use Javascript to do X, Y, or Z with imagemaps. I wouldn't know, I barely have even messed with the things. And I suspect there are tools out there to try to generate the clickable areas more easily (like a map of the US states, etc. etc.). :P
Side Note: I also stumbled across the
<map> page in the EPUB3 Accessibility Guidelines:
Quote:
Server-side maps are inherently less accessible, both because they require that the reader be able to see the image to discern the regions and also because they require that the reader be able to click on the image in an exact spot.
Client-side maps make use of an associated map element to define the clickable regions. Each region is specified in an area element, and each area should include an alt attribute that indicates its purpose so that non-visual readers can easily discover the functionality. Assistive technologies allow readers to iterate over these areas, making them a much friendlier option than server-side maps, and without requiring intrusive fallbacks.
In fact, server-side maps provide no additional functionality, so their use is never recommended. If one must be used, a set of links corresponding to each clickable region should be provided so that readers who cannot interact with the map have equal access to the functionality.
Note that maps of either kind should never be used when a better alternative is available (e.g., to make an image of text linkable).
|
Even IF they were supported on devices (which they aren't), it still doesn't seem like it would work well at all on a non-PC devices. It seems like quite a bit of the functionality relies on hovering a mouse over certain areas.