Bug 140259 - area elements added to document sequential navigation order in DOM order instead of in place of referencing image
Summary: area elements added to document sequential navigation order in DOM order inst...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2015-01-08 11:09 PST by Rodney Rehm
Modified: 2015-01-08 11:09 PST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rodney Rehm 2015-01-08 11:09:35 PST 
1. <area> and <img> are not associated in tabbing sequence, meaning the <area> elements might be added to the focus sequence at the beginning of the document and the image at the end of the document.
2. if the same <map> element is referenced by two <img> elements, it is not tabbed through twice, but only once

I could not find anything about tabbing order of image maps in the specification, so I opened a bug there as well: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27787

Bug in Blink for reference: https://code.google.com/p/chromium/issues/detail?id=447289
Comment 1 Radar WebKit Bug Importer 2015-01-08 11:09:58 PST 
<rdar://problem/19414598>