W3C home > Mailing lists > Public > public-html-a11y@w3.org > January 2015

New bug on imagemaps

From: <chaals@yandex-team.ru>
Date: Fri, 09 Jan 2015 14:46:28 +0300
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-Id: <529241420803988@webcorp02h.yandex-team.ru>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27787 suggests that there should be more clarity in how focus moves to area elements of imagemaps - in particular that when you reach an image or object that has an associated map, you should be presented with a list of the active areas, much as if the image functioned as a label element for the map.

It says this is the behaviour in trident (I don't have IE so haven't tested) and gecko (Oh, I don't have a testcase either. I'll make one), but not in webkit or blink.

What the spec says now is 

Because a map element (and its area elements) can be associated with multiple img and object elements, it is possible for an area element to correspond to multiple focusable areas of the document.
]]] - http://www.w3.org/html/wg/drafts/html/master/embedded-content.html#image-maps - last "Note"

which I think implies the requested behaviour, but is pretty unclear.

Seems to me that the proposal makes sense. Thoughts? Anyone already got a test case or three?



Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Friday, 9 January 2015 11:46:59 UTC

This archive was generated by hypermail 2.3.1 : Friday, 9 January 2015 11:46:59 UTC