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

[Bug 27787] New: Sequential Navigation Focus Order for Image Maps

From: <bugzilla@jessica.w3.org>
Date: Thu, 08 Jan 2015 18:27:03 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-27787-2486@http.www.w3.org/Bugs/Public/>

            Bug ID: 27787
           Summary: Sequential Navigation Focus Order for Image Maps
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: mail@rodneyrehm.de
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,

"User agents may also allow individual area elements representing hyperlinks to
be selected and activated (e.g. using a keyboard)."

Every major user agent (Gecko, Trident, WebKit, Blink) adds <area> elements to
the document's sequential navigation focus order. But because the specification
does not explain *how* that should happen, they disagree on the order.

In Blink and WebKit the <area> elements are added to the sequence in DOM order.
In Gecko and Trident <area> themselves are inserted into the sequence in place
of the <img usemap=""> actually using the map containing the <area> elements.

So in Blink and WebKit the image maps are accessible, just not in place of the
image, but wherever they appear in the document. The <map> element might be
placed right after <body>, but the <img usemap> may be used in a modal <dialog>
element. There is no way to Tab through the image's map. (using the <dialog>
here is just an extreme example to make a point.)

"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."

In Trident those multiple references to the same map cause the the associated
<area> elements to occur multiple times in the document's sequential navigation
focus order. In Gecko this should happen, but is masked by a bug. In Blink and
WebKit the <area> elements are only tabbed through once.

Can we get the Trident behavior added to the specification?

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 8 January 2015 18:27:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:03:34 UTC