This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The spec says "In user agents that do not support images, or that have images disabled, object elements cannot represent images, and thus this section never applies (the fallback content is shown instead). The following steps therefore only apply to img elements." This rule renders imagemaps associated with OBJECT inaccessible, or it forces authors to put a redundant copy of the links in the fallback content, increasing the probability of author error. It is not clear from the spec that there is a reason this rule needs to exist, while it prevents expansion of imagemap use cases via the more generic <object> element that loads content sometimes more suitable than an <img> can. Edit details: remove the sentence quoted above.
mass-moved component to LC1
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: Removing the sentence quoted would have no effect (it's not a normative sentence — it's just describing the results of other rules). However, this is a non-issue. It's trivial to use an image map with <object> and only give it once and make it accessible: just put the image map inside the <object>.
a11ytf RESOLUTION to close on 2013-10-17: http://www.w3.org/2013/10/17-html-a11y-minutes.html#item04