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

How about this?

Accessible Name
​: ​
The accessible name is the name of a user interface element. Each platform
accessibility API provides the accessible name property. The value of the
accessible name may be derived from a visible (e.g., the visible text in a
link) or invisible (e.g., alternate text that reports to the accessible
name) property of the user interface element.

Adapted from https://www.w3.org/TR/wai-aria/terms


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 10:13 AM, David MacDonald <david100@sympatico.ca>
wrote:

> Agree
>
> 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 9:27 AM, Katie Haritos-Shea <ryladog@gmail.com>
> wrote:
>
>> I like this idea, but, only if we have a very clear defonition of
>> Accessible Name that makes it clear it is not limited to the ARIA usage.
>>
>> Katie Haritos-Shea
>> 703-371-5545
>>
>> On Jul 19, 2016 9:14 AM, "David MacDonald" <david100@sympatico.ca> wrote:
>>
>>> ***This is proposed for version 2.1. NOT for 2.0 ***
>>>
>>> Do we want to consider replacing
>>> ​"
>>> programmatically determined link context" with "Accessible name" in
>>> 2.4.4.
>>>
>>> This will simplify the requirement, eliminate that awkward definition
>>> that few developers understood, and ensure that when screen reader users
>>> pull up a list of links on on conforming page, they will not get "learn
>>> more" etc... because screen readers provide the accessible name in the
>>> links list, not just the link text. So an aria-label or aria-labelledby
>>> will render a meaningful text in the list. AccessibleName wasn't well
>>> understood or supported back in 2006-2008.
>>>
>>> ===Current===
>>>
>>> 2.4.4 Link Purpose (In Context): The purpose of each link can be
>>> determined from the link text alone or from the link text together with its
>>> ​​
>>> programmatically determined link context, except where the purpose of
>>> the link would be ambiguous to users in general. (Level A)
>>>
>>> ​=== Proposal change===
>>>
>>> 2.4.4 Link Purpose (In Context): The purpose of each link can be
>>> determined from the link text alone or Accessible Name, except where the
>>> purpose of the link would be ambiguous to users in general. (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>
>>>
>>
>