Re: (WCAG 2.1) Do we want to replace ​"programmatically determined link context" in 2.4.4 with "Accessible Name"?

My proposal is that the user will know where the link goes from the
Accessible Name nothing more. We could provide guidance on a good length.

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*
Tel:  613.235.4902

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

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://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 Tue, Jul 19, 2016 at 7:29 PM, Jonathan Avila <jon.avila@ssbbartgroup.com>
wrote:

> Ø  Links lists in AT only pull the accessibleName, I think they are
> worried about being overly chatty with the AccessibleDescription.
>
>
>
> How would an accessible name and description on a links list that includes
> what you are proposing to be included only the accessible name to be any
> more chatty?  You are proposing stuffing the exact same information into
> the name which would provide the exact same result.  If the description was
> used by screen reader then the user could choose how much information to
> hear if the screen reader made including description an option.  If it were
> all crammed in the accessible name then user who didn’t want the chattiness
> would have no way to filter it out!  So better in the description IMO.
>
>
>
> Jonathan
>
>
>
> Jonathan Avila
>
> Chief Accessibility Officer
>
> SSB BART Group
>
> jon.avila@ssbbartgroup.com
>
> 703.637.8957 (Office)
>
>
>
> Visit us online: Website <http://www.ssbbartgroup.com/> | Twitter
> <https://twitter.com/SSBBARTGroup> | Facebook
> <https://www.facebook.com/ssbbartgroup> | Linkedin
> <https://www.linkedin.com/company/355266?trk=tyah> | Blog
> <http://www.ssbbartgroup.com/blog/>
>
> Check out our Digital Accessibility Webinars!
> <http://www.ssbbartgroup.com/webinars/>
>
>
>
> *From:* David MacDonald [mailto:david100@sympatico.ca]
> *Sent:* Tuesday, July 19, 2016 7:13 PM
> *To:* Jonathan Avila
> *Cc:* WCAG
> *Subject:* Re: (WCAG 2.1) Do we want to replace ​"programmatically
> determined link context" in 2.4.4 with "Accessible Name"?
>
>
>
> Links lists in AT only pull the accessibleName, I think they are worried
> about being overly chatty with the AccessibleDescription.
>
>
>
> But I think what I'm hearing here is not much momentum to add this
> requirement to WCAG 2.1.
>
>
>
> Perhaps just adding Accessible Name to 2.4.4 rather than replacing
> programmatic link context. At least that will provide an encouragement to
> people to do this.
>
>
>
> *2.4.4
> <http://www.w3.org/TR/2008/REC-WCAG20-20081211/#navigation-mechanisms-refs> Link
> Purpose (In Context):* The purpose of each link
> <https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-refs.html#linkpurposedef> can
> be determined from the link text alone or from the link text together with
> its programmatically determined link context
> <https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-refs.html#pdlinkcontextdef>,
> or from its Accessible Name except where the purpose of the link would be ambiguous
> to users in general
> <https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-refs.html#ambiguouslinkdef>.
> (Level A)
>
>
>
>
>
>
> Cheers,
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
>
> Tel:  613.235.4902
>
> LinkedIn
> <http://www.linkedin.com/in/davidmacdonald100>
>
> twitter.com/davidmacd
>
> GitHub <https://github.com/DavidMacDonald>
>
> www.Can-Adapt.com <http://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 Tue, Jul 19, 2016 at 5:44 PM, Jonathan Avila <
> jon.avila@ssbbartgroup.com> wrote:
>
> If the links list doesn't take into account the accessible description
> then it seems like a bug.   I don't think we should force all of the
> contextual text into the name.
>
>
>
> Jon
>
> Sent from my iPhone
>
>
> On Jul 19, 2016, at 4:45 PM, David MacDonald <david100@sympatico.ca>
> wrote:
>
> The aria-describedby does not factor into accessible name calculation,
> only the accessible description calculation.  So it won't appear in a links
> list.
>
>
>
> The Title will if there is no other Accessible Name.
>
>
> Cheers,
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
>
> Tel:  613.235.4902
>
> LinkedIn
> <http://www.linkedin.com/in/davidmacdonald100>
>
> twitter.com/davidmacd
>
> GitHub <https://github.com/DavidMacDonald>
>
> www.Can-Adapt.com <http://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 Tue, Jul 19, 2016 at 11:13 AM, Patrick H. Lauke <redux@splintered.co.uk>
> wrote:
>
> On 19/07/2016 15:41, Sailesh Panchang wrote:
>
> Plus another one for Greg's comment.
> One can also use title or aria-describedby  to qualify what  the
> linked text "Read more"  relates to ... that is not an accessible
> name.
>
>
> Just on this one point, note that title, aria-describedby etc all form
> part of what's taken into consideration for the accessible name calculation
> of an HTML element - see
> https://www.w3.org/TR/html-aapi/#accessible-name-and-description-calculation
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>
>
>
>