- From: Simon Harper <simon.harper@manchester.ac.uk>
- Date: Mon, 31 Jan 2011 16:55:53 +0000
- To: UAWG list <w3c-wai-ua@w3.org>
Hi there, So this action was to rewrite 1.11.2. We removed 1.11.1 because the viewport aspects are handled in 1.8 - however looking at 1.11.2 it seems to me 'link title' is not extended information - in fact it seems to me more basic than viewport handling. In this case I propose we reinstate 1.11.1 as 1.11.1 (former 3.13.1) Basic Link Information: The following information is provided for each link (Level A) : * link element content, * link title * link status (visited/selected/hover) The Intent for 1.11.1 actually relates to 1.11.2 but can be modified easily as follows: * Intent of Success Criterion 1.11.1 (former 3.13.1): o Users who use screen readers need to be able to easily discover information about a link, including the title of the link in the event that the link content has the same text as other links on the page. Otherwise the effect of selecting that link is not distinguishable. * Examples of Success Criterion 1.11.1 (former 3.13.1): o Robert, who uses a screen reader, hears a list of links read out saying 'more', 'more', 'more'. The browser also displays the link title so that Robert can distinguish which link he must select. * Related Resources for Success Criterion 1.11.1 (former 3.13.1): o Web Content Accessibility Guidelines version 2.0 Now I propose that we rewrite 1.11.2 to be: 1.11.2 (former 3.13.2) Extended Link Information: The following information is provided for each link which does not point to an (x)html file (Level AAA) : * what will be the consequences of selecting the link (will a file download to desktop occur? Will a text file be opened by the browser?) * technology type (of the linked Web resource) * technology file size (of the linked Web resource) * predicted time to load (of the linked Web resource) * intra-page/onsite/offsite (whether the link is internal to the resource e.g., the link is to a target in the same Web page) * Intent of Success Criterion 1.11.2 (former 3.13.2): o Here we wish to mitigate the possibility of unexpected consequences occurring on link selection; this is especially the case for users who cannot see the visual cues present on the web page. For instance, visual styling can be used to imbue groups of simple links with semantic differences such as downloads or offsite links. This may then become a problem because links which seem the same to a user of assistive technology may have unexpected consequences when selected. * Examples of Success Criterion 1.11.2 (former 3.13.2): o Robert, who uses a screen reader, selects a link which is surrounding an image, the user agent downloads the image and displays the raw image file, Robert's assistive technology cannot describe the image or even say what has downloaded because raw images do not have alt elements and image downloaded and displayed is not an html file. If the user agent tells Robert that an image file download will occur on link selection he would not have made that choice as he cannot see the image. * Related Resources for Success Criterion 1.11.2 (former 3.13.2): o Web Content Accessibility Guidelines version 2.0
Received on Monday, 31 January 2011 16:56:22 UTC