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

 >>>What problem does it solve

The proposed changes will pastorally steer developers away from depending
on the enclosing *sentence* or *paragraph* as the link context and will
move them towards a more robust programmatic association such as the
accessible name. There is no change to what passes or fails.


>>>and how do we know it is actually a problem?

I teach blind users how to use screen readers about 20% of my time, so I'm
exposed to a fair number of screen reader users at all levels. Beginner and
intermediate screen reader users depend heavily on lists of links. Advanced
users such as those who we associate with do not tend to depend on links
lists as much. Links lists with many ambiguous link names
is definitely a problem for beginner and intermediate screen reader users.
Even some advanced blind users like Sina Bahram feel this way.
https://twitter.com/SinaBahram/status/755524965395496960



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 Wed, Jul 20, 2016 at 3:13 PM, Andrew Kirkpatrick <akirkpat@adobe.com>
wrote:

> *[Jason] I think my proposal to broaden the definition of
> “programmatically determined link context” addresses David’s issue. So far,
> no one has put forward good reasons for rejecting it.*
>
> I’m still waiting for the clear reasons to accept it. What problem does it
> solve, and how do we know it is actually a problem?
> AWK
>
>
>