W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2011

[Bug 13451] New: Don't disallow image map on object

From: <bugzilla@jessica.w3.org>
Date: Fri, 29 Jul 2011 14:16:16 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-13451-2486@http.www.w3.org/Bugs/Public/>

           Summary: Don't disallow image map on object
           Product: HTML WG
           Version: unspecified
          Platform: PC
               URL: http://www.w3.org/TR/2011/WD-html5-20110525/the-map-el
        OS/Version: Windows XP
            Status: NEW
          Keywords: a11y, a11ytf
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: cooper@w3.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, public-html-a11y@w3.org

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.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 29 July 2011 14:16:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:56 UTC