This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22948 - [AAPI]: clarify mappings for <link>
Summary: [AAPI]: clarify mappings for <link>
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Jason Kiss
QA Contact: HTML a11y API spec bugbot
URL:
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2013-08-14 00:46 UTC by Jason Kiss
Modified: 2014-05-18 22:29 UTC (History)
6 users (show)

See Also:


Attachments

Description Jason Kiss 2013-08-14 00:46:15 UTC
Should expressly indicate mappings for <link> elements that act as hyperlinks (mapped something like normal hyperlinks?), and those that act as external resource links (not mapped?).
Comment 1 alexander surkov 2013-08-15 18:59:04 UTC
can you give an example when <link> acts as a normal hyperlink please?
Comment 2 Jason Kiss 2013-08-15 20:48:15 UTC
If a <link> has an @href and a certain @rel value, it creates a hyperlink. It doesn't act as a "normal" hyperlink. If the <link> has a @rel, it is restricted to the <head>. [1] 

Hyperlinks are "generally exposed to the user by the user agent so that the user can cause the user agent to navigate to those resources, e.g. to visit them in a browser or download them." [2] For a <link> that creates a hyperlink, I'm assuming that if this were to be exposed to the user, it would be via some additional browser UI or functionality. As such, in either case (hyperlink or external resource link), the <link> is not mapped via the accessibility API. So we can keep a single entry for <link> "Not mapped" across the board.

Does that make sense?


[1] http://www.w3.org/html/wg/drafts/html/master/document-metadata.html#the-link-element
[2] http://www.w3.org/html/wg/drafts/html/master/links.html#hyperlink
Comment 3 alexander surkov 2013-08-16 18:19:12 UTC
it sounds reasonable, we may want to add a comment saying that
Comment 4 Jason Kiss 2014-05-18 22:29:35 UTC
(In reply to alexander surkov from comment #3)
> it sounds reasonable, we may want to add a comment saying that

All browsers set <link> to display:none by default and don't map it. The mapping doc now reflects this.

https://github.com/w3c/html-api-map/commit/182fa59ecc06c7038d51fb57ae24b6ee5b0691b6