W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2011

EIR 1.11.2

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 27 Jan 2011 11:49:03 -0600
Message-ID: <AANLkTi=ifDqniEPZz_R36X9i=JCAMiuqX9CcGsWcWdiy@mail.gmail.com>
To: WAI-ua <w3c-wai-ua@w3.org>
1.11.2 Extended Link Information:
The following information is provided for each link (Level AAA) :
    * link title,
    * technology type (of the linked Web resource)
    * internal/external: (whether the link is internal to the resource
e.g., the link is to a target in the same Web page) ??to me this also
means the link is to a target on the same website.

    * Intent of Success Criterion 1.11.2
To help the user decide whether to traverse a link in content. This
helps users for whom following a link may lead to loss of context upon
return, including some users with blindness and low vision, some users
with a cognitive disability, and some users with a physical
disability. Provide relevant author supplied information (@title,
@hreflang, etc.  if available), the destination content type (from
extension on URI if available - .pdf, .doc, etc), and whether the link
is to a target in the same web page, web site, or to an external

    * Examples of Success Criterion 1.11.2
<some name> is reviewing a website. She is only interested in
information on that particular site. Her browser has a preference
setting that allows the indication of content location relative the
current page and/or site.  @@this is weak@@

# Some markup languages allow authors to provide hints about the
nature of linked content (e.g., in HTML 4 [HTML4], the 'hreflang' and
'type' attributes on the A element). Specifications should indicate
when this type of information is a hint from the author and when these
hints may be overridden by another mechanism (e.g., by HTTP headers in
the case of HTML). User agent developers should make the author's
hints available to the user (prior to retrieving a resource), but
should provide definitive information once available.
# The scope of "recently followed link" depends on the user agent. The
user agent may allow the user to configure this parameter, and should
allow the user to reset all links as "not followed recently."
# User agents should cache information determined as the result of
retrieving a Web resource and should make it available to the user.
Refer to HTTP/1.1 caching mechanisms described in RFC 2616 [RFC2616],
section 13.
# For a link that has content focus, allow the user to query the link
for information (e.g., by activating a menu or key stroke).
# Do not mark all local links (to anchors in the same page) as visited
when the page has been visited.

    * Related Resources for Success Criterion 1.11.2
    1. User agents may use HTTP HEAD rather than GET for information
about size and language. Refer to RFC 2616 [RFC2616], section 9.3
   2. For information about content size in HTTP/1.1, refer to RFC
2616 [RFC2616], section 14.13. User agents are not expected to compute
content size recursively (i.e., by adding the sizes of resources
referenced by URIs within another resource).
   3. For information about content language in HTTP/1.1, refer to RFC
2616 [RFC2616], section 14.12.
   4. For information about content type in HTTP/1.1, refer to RFC
2616 [RFC2616], section 14.17.

Jim Allan, Accessibility Coordinator & Webmaster

Texas School for the Blind and Visually Impaired

1100 W. 45th St., Austin, Texas 78756

voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/

"We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Thursday, 27 January 2011 17:49:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:39 UTC