Re: Failures review

In case anyone wants the reference to the algorithm it is at
http://www.w3.org/TR/html-aapi/#a-element

although I do note a bug in the algorithm which I will try to log - namely the accessible description calculation should read

a element accessible description calculation

Use aria-describedby
Otherwise use the title attribute if it wasn't used as the accessible name
If none of the above yield a usable text string there is no accessible description

Regards,
James

On Dec 11, 2013, at 5:16 PM, Sailesh Panchang <spanchang02@yahoo.com> wrote:

> 
> Hi David Firefox exposes the title as the accessible description when it is not interpreted  as the accessible name so both the anchor text and the title on a  link  are exposed by Firefox. This is as per  the algorithm  
> Sailesh---
> Sent from my iPad ... Please pardon "dictapos" and typos ... <grin>
> 
> On Dec 9, 2013, at 7:39 AM, David MacDonald <david100@sympatico.ca> wrote:
> 
>> I think we need to move H33 technique to advisory. The link text and title compete for the AccName and so the title text is not read...  There is an option not on by default to crawl the DOM and select the title attribute, but both cannot be selected and it is a heuristic hack given that the accessibility API doesn’t get this... there are extensive user agent notes on the techniques, about where it doesn’t work, and none of this has been fixed in the 5 years since we published the technique.
>> Providing a supplemental description of the purpose of a link using one of the following techniques:
>> H33: Supplementing link text with the title attribute (HTML)
>>  
>> Cheers,
>> David MacDonald
>>  
>> CanAdapt Solutions Inc.
>> Tel:  613.235.4902
>> http://ca.linkedin.com/in/davidmacdonald100
>> www.Can-Adapt.com
>>   
>>   Adapting the web to all users
>>             Including those with disabilities
>>  
>> This e-mail originates from CanAdapt Solutions Inc. Any distribution, use or copying of this e-mail or the information it contains by other than the intended recipient(s) is unauthorized. If you are not the intended recipient, please notify me at the telephone number shown above or by return e-mail and delete this communication and any copy immediately. Thank you.
>>  
>> Le présent courriel a été expédié par CanAdapt Solutions Inc. Toute distribution, utilisation ou reproduction du courriel ou des renseignements qui s'y trouvent par une personne autre que son destinataire prévu est interdite. Si vous avez reçu le message par erreur, veuillez m'en aviser par téléphone (au numéro précité) ou par courriel, puis supprimer sans délai la version originale de la communication ainsi que toutes ses copies. Je vous remercie de votre collaboration.
>>  
>> From: Andrew Kirkpatrick [mailto:akirkpat@adobe.com] 
>> Sent: December 7, 2013 4:10 PM
>> To: David MacDonald; 'Bailey, Bruce'; thiessenp@acm.org; k.probiesch@gmail.com
>> Cc: 'WCAG Editors'; kirsten@can-adapt.com
>> Subject: RE: Failures review
>>  
>> Great David – thanks a lot. 
>>  
>> From: David MacDonald [mailto:david100@sympatico.ca] 
>> Sent: Saturday, December 07, 2013 10:13 AM
>> To: Andrew Kirkpatrick; 'Bailey, Bruce'; thiessenp@acm.org; k.probiesch@gmail.com
>> Cc: 'WCAG Editors'; kirsten@can-adapt.com
>> Subject: RE: Failures review
>>  
>> I’ve completed my action item...
>>  
>> Possible impacts on
>> F2: Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text.
>> Role of heading would pass? Should discuss...
>> F3: Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information
>> Alternate text via labelled by or aria-label could provide an alternative? This relates with F65 although Marco says should be treated separately from f65 to which I agree… we could allow it and still not change f65, but it muddies the waters? Should discuss...
>> And F3
>>  
>> Cheers,
>> David MacDonald
>>  
>> CanAdapt Solutions Inc.
>> Tel:  613.235.4902
>> http://ca.linkedin.com/in/davidmacdonald100
>> www.Can-Adapt.com
>>   
>>   Adapting the web to all users
>>             Including those with disabilities
>>  
>> This e-mail originates from CanAdapt Solutions Inc. Any distribution, use or copying of this e-mail or the information it contains by other than the intended recipient(s) is unauthorized. If you are not the intended recipient, please notify me at the telephone number shown above or by return e-mail and delete this communication and any copy immediately. Thank you.
>>  
>> Le présent courriel a été expédié par CanAdapt Solutions Inc. Toute distribution, utilisation ou reproduction du courriel ou des renseignements qui s'y trouvent par une personne autre que son destinataire prévu est interdite. Si vous avez reçu le message par erreur, veuillez m'en aviser par téléphone (au numéro précité) ou par courriel, puis supprimer sans délai la version originale de la communication ainsi que toutes ses copies. Je vous remercie de votre collaboration.
>>  
>> From: Andrew Kirkpatrick [mailto:akirkpat@adobe.com] 
>> Sent: December 6, 2013 10:11 AM
>> To: David MacDonald; Bailey, Bruce; Peter <thiessenp@acm.org> (thiessenp@acm.org); k.probiesch@gmail.com
>> Cc: WCAG Editors
>> Subject: Failures review
>>  
>> Just a reminder that we are hoping to get an expedited review of the failures. The failures are athttp://www.w3.org/TR/WCAG-TECHS/failures.html and the place to add your comments ishttp://www.w3.org/WAI/GL/wiki/Techniques/Failures.
>>  
>> This doesn’t need to be an enormous task – you don’t need to SOLVE the problems, just identify them.  You can see my comments on the wiki page for reference.
>>  
>> If you will not be able to review your 20 before the next WCAG call, please let me know as soon as you can.
>>  
>> Thanks,
>> AWK
>>  
>> Andrew Kirkpatrick
>> Group Product Manager, Accessibility
>> Adobe Systems
>>  
>> akirkpat@adobe.com
>> http://twitter.com/awkawk
>> http://blogs.adobe.com/accessibility