Re: Fwd: Should 2.4.4 require Link text or ACCNAME, rather than enclosing sentence etc...

Hello Jason and David

Can you add any feedback for the COGA SC in the wiki page at https://www.w3.org/wiki/WCAG/Coga_SC?


When you do so please make sure you read the full text of the success criteria before commenting. I suspect you will find that some of your issues have been at least partially addressed by the full text, and your comment will be more relevant to the actual suggested success criteria.



All the best

Lisa Seeman

LinkedIn, Twitter



---------- Forwarded message ----------
From: White, Jason J <jjwhite@ets.org>
Date: Wed, Jul 6, 2016 at 1:48 PM
Subject: RE: Should 2.4.4 require Link text or ACCNAME, rather than enclosing sentence etc...
To: David MacDonald <david100@sympatico.ca>, John Foliot <john.foliot@deque.com>
Cc: WCAG <w3c-wai-gl@w3.org>


    
  
     From: David MacDonald [mailto:david100@sympatico.ca] 
 Sent: Wednesday, July 6, 2016 1:03 PM
 
 
 
 
   COGA is recommending one normative SCs that would address link destination.
 
   
 
  ​*​
 
 Instructions, labels, navigation and important information are provided with a clear writing style that includes:
  ​ ... ​
 
 "On controls, links and buttons use words that identify their function. Function can be the destination of a link (such as "home" or "contact us")"
  https://www.w3.org/wiki/WCAG/Coga_SC 
 
   
 [Jason] Side note: I don’t know how to define a “clear writing style” without being too subjective or language-specific.
 
   
 COGA appear
​s​
 to acknowledge this, and is also proposing a coga-destination attribute, which is outside the context of WCAG SC's, and more along the lines of WAI ARIA attribute. 
 [Jason] Perhaps Web annotations would be a useful mechanism for doing this, complemented by an ontology of common UI control functions and link destinations so that familiar language or icons can be substituted by an assistive technology for whatever the author provides.
 
   
 We can't require something that doesn't yet exist. I think we can safely say that in this 2.1 version we should do an incremental change, and as the coga-destination attribute makes its way through the W3C process and then to user agent support, we can watch carefully and if it seems doable we can open the language further, in 2.4.4
  
 
  [Jason] Requirements that can be satisfied with annotations, markup or API usage can in principle rise to level A, and therefore, clearly, to level AA. I think a combination of Web annotations, markup, APIs and personalization techniques opens possibilities for much more individualized Web accessibility than we’ve seen before. There is an especially great potential for users with learning and cognitive disabilities to benefit.
  
 
 
 
 
 
  This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.
 
 Thank you for your compliance.