Re: Working Meeting for WCAG techniques - Thursday 15 May, 2014 - 4pm EDT

Hi Loretta

Here is a wiki version of the technique

https://www.w3.org/WAI/GL/wiki/Using_aria-describedby_for_link_purpose_-_May_2014


*http://tinyurl.com/pejbk9x <http://tinyurl.com/pejbk9x>*


Cheers,

David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn <http://www.linkedin.com/in/davidmacdonald100>

www.Can-Adapt.com



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy
policy<http://www.davidmacd.com/disclaimer.html>


On Fri, May 16, 2014 at 4:11 PM, David MacDonald <david100@sympatico.ca>wrote:

> Thanks Loretta
>
> I will move it to the WIKI... We'll need more time before using pull
> requests for developing techniques. Perhaps when we are able to get a
> rendering system XML to HTML, where we can see the HTML transformation in
> real time.
>
> Cheers,
>
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
>
> Tel:  613.235.4902
>
> LinkedIn <http://www.linkedin.com/in/davidmacdonald100>
>
> www.Can-Adapt.com
>
>
>
> *  Adapting the web to all users*
> *            Including those with disabilities*
>
> If you are not the intended recipient, please review our privacy policy<http://www.davidmacd.com/disclaimer.html>
>
>
> On Fri, May 16, 2014 at 10:33 AM, Sailesh Panchang <
> sailesh.panchang@deque.com> wrote:
>
>> Lorettaa,
>>
>> >> * Also, note somewhere that the descirption will not show up in link
>> lists. (Nothing >>prevents screen readers from including it, of course, but
>> they don't seem to be doing >>that.)
>> Sailesh: This behavior of SRs is quite right. The aria-describedby
>> text is accessible description and is spoken after the anchor text
>> because it is contextual info and not the link's name. If
>> aria-labelledby is used, that text becomes the link's name and is
>> exposed as the link's identifier in a links list.
>> As one might expect, SRs do not expose a link's contextual info like
>> associated table header cell,  paragraph text or nearest heading text
>> in a links list.
>> >>* We also think there should be a similar technique using
>> aria-labelledby, which has a different set of strengths and weaknesses
>> (mostly related to how screen >>readers handle it).
>> Sailesh: ARIA7 is already documented for SC 2.4.4.
>>
>> Thanks and regards,
>> Sailesh
>>
>>
>> On 5/15/14, Loretta Guarino Reid <lorettaguarino@google.com> wrote:
>> > David, here is the task force feedback on your draft:
>> >
>> > * We like this technique and would like to see it published in the next
>> > update, if possible
>> >
>> > * Logistics: it is very hard to read from github. We would really rather
>> > have you start in the wiki, where it is also easier to make edits. (Like
>> > fixing the typo in imporvements.
>> >
>> >
>> > * We would like user agent notes that explain what current screen
>> readers
>> > do (e.g. order of reading, long delay in VoiceOver before description is
>> > read) and that ARIA doesn't specify what the screen reader should do, so
>> > the behavior may be unpredictable. In general, however, screen readers
>> seem
>> > to read the description automatically for links.
>> >
>> > * Also, note somewhere that the descirption will not show up in link
>> lists.
>> > (Nothing prevents screen readers from including it, of course, but they
>> > don't seem to be doing that.)
>> >
>> > * We also think there should be a similar technique using
>> aria-labelledby,
>> > which has a different set of strengths and weaknesses (mostly related to
>> > how screen readers handle it).
>> >
>> >
>> >
>> > On Wed, May 14, 2014 at 6:53 PM, David MacDonald
>> > <david100@sympatico.ca>wrote:
>> >
>> >> I have to teach tomorrow but I've create ARIA 20 an aria-describedby
>> >> technique  for link context.
>> >>
>> >> *http://tinyurl.com/k3hs3wr <http://tinyurl.com/k3hs3wr>*
>> >>
>> >>
>> >> Cheers,
>> >>
>> >> David MacDonald
>> >>
>> >>
>> >>
>> >> *Can**Adapt* *Solutions Inc.*
>> >>
>> >> Tel:  613.235.4902
>> >>
>> >> LinkedIn <http://www.linkedin.com/in/davidmacdonald100>
>> >>
>> >> www.Can-Adapt.com
>> >>
>> >>
>> >>
>> >> *  Adapting the web to all users*
>> >> *            Including those with disabilities*
>> >>
>> >> If you are not the intended recipient, please review our privacy
>> >> policy<http://www.davidmacd.com/disclaimer.html>
>> >>
>> >>
>> >> On Wed, May 14, 2014 at 7:39 PM, Loretta Guarino Reid <
>> >> lorettaguarino@google.com> wrote:
>> >>
>> >>> The next regular working meeting for techniques for WCAG will take
>> place
>> >>> tomorrow (Thursday) at 4pm EDT
>> >>>
>> >>> There are techniques to discuss on the agenda at
>> >>> https://www.w3.org/WAI/GL/wiki/Techniques_working_meeting_agenda .
>> >>> Please add anything else you would like to talk about and also feel
>> free
>> >>> to
>> >>> attend to help others work through their techniques even if you have
>> >>> nothing on the agenda.
>> >>>
>> >>>
>> >>> The call details are as follows
>> >>>
>> >>> Meeting Information
>> >>> Length: 60 minutes Date: Thursday 08 May Time: 4PM EDT (8pm UTC)
>> >>> Bridge: +1.617.761.6200 (US)
>> >>> SIP: zakim@voip.w3.org
>> >>> Passcode: 9224#
>> >>> IRC channel #wcag-techs
>> >>>
>> >>
>> >>
>> >
>>
>>
>>
>