8748 2010-01-14 15:22:25 +0000 Differentiating hyperlinks referring to the same tag in different scopes 2010-10-04 14:30:11 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All RESOLVED NEEDSINFO http://www.w3.org/TR/html5/history.html#link-type-tag a11y P2 normal --- 1 gez.lemon ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 31042 0 gez.lemon 2010-01-14 15:22:25 +0000 Link type "tag" specifies the link relationship, but does not specify how the tag name is to be determined apart from the link's text equivalent. The specification does not define how an author might differentiate hyperlinks referring to the same tag in different scopes. For example, on Flickr, there are two links for each tag: "your photos with tag: 'foo'" and "others' photos with tag: 'foo'"… If the text equivalent for both links the same, an assistive technology user will not be able to perceive the difference. If the text is different, there is no machine-readable way for a script to understand that both links refer to the same tag. The Microformats wiki page for rel-tag attempts to solve this problem by enforcing a RESTful tag URL apart from the text equivalent, but it still has several unaddressed development and internationalization issues. <http://microformats.org/wiki/rel-tag-issues> If this type of link relationship is to remain, consider adding an optional data attribute to allow the author to explicitly state the tag name if it is not the same as the text equivalent. 31839 1 cooper 2010-02-11 17:26:49 +0000 Per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html, the HTML A11Y TF does not plan to formally work on this issue at this time. This does not mean the TF has no interest in it, but does not have immediate plans to work on it. The TF may review the issue in the future. 32302 2 ian 2010-02-17 22:35:46 +0000 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: Did Not Understand Request Change Description: no spec change Rationale: The tag name is determined by the link's destination, not by the contents of the element. Would an example showing how to do your Flickr case help? I'd be happy to elaborate on what the spec says now if you think that would be helpful. It's not clear to me what the spec says that would lead to the misunderstanding in the bug description, so any advice along those lines that you could give me would be very helpful also.