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

>>Is this **just** for blind users?

The Accessible Name is available to any AT or software for any disability.
Its there for anything that wants to use it.

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 4:53 PM, John Foliot <john.foliot@deque.com> wrote:

> Question: Do we currently have (or envision) a Success Criteria that
> mandates “links lists”?
>
>
>
> While super-useful to screen reader users, how do I, as a sighted
> non-screen-reader user get a similar construct in my user-agent? Or is it
> solely dependent on the Assistive Technology to provide this accommodation
> (shortcut/enhancement)? Is this **just** for blind users?
>
>
>
> Once again, it seems like we are driving towards mandated patterns, and
> not abstracted functional requirements: If we want to see the ability to
> expose a list of links for all users (I could see this being a benefit to
> some cognitively challenged users as well) then whatever we write up must
> be achievable in such a way as to not be dependent on a specific pattern or
> software.
>
>
>
> JF
>
>
>
> *From:* David MacDonald [mailto:david100@sympatico.ca]
> *Sent:* Tuesday, July 19, 2016 3:44 PM
> *To:* Patrick H. Lauke <redux@splintered.co.uk>
> *Cc:* WCAG <w3c-wai-gl@w3.org>
> *Subject:* Re: (WCAG 2.1) Do we want to replace ​"programmatically
> determined link context" in 2.4.4 with "Accessible Name"?
>
>
>
> 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
>
>
>