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

To achieve the goal, it seems there are two things:


-          Clarify that link-text can be enhanced (or hindered) by the accessible name calculation.
I.e. the link text can be over-ridden, and both have to work.

-          Add to the methods of having context, e.g .with aria-describedby.

Is that right?

I’m just wary of relying on additional mechanisms (e.g. aria-label) when they can confuse as much as improve.
Jason’s update helps with that.

The related changes for techniques are a useful barometer of the change, thanks for those. My initial take is:

-          I’m ambivalent about removing G53 & H78 (context of a paragraph), it is weak context but if someone piped up with a use-case it they be worth keeping. I’m lacking history on those, sorry.

-          Is H33 (title on link text) sufficient for SC 2.4.4? I didn’t think it was. Happy to drop given the ongoing lack of user-agent support.

-          H80 (heading as context) is still useful as context (i.e. I know of sites where that is relied on, and the user-agent side hasn’t changed in that regard).

-          Could we add a technique for describing links with aria-describedby? I can’t see one in the official 2.4.4 list [1].

Cheers,

-Alastair

1] https://www.w3.org/WAI/WCAG20/quickref/?showtechniques=244#qr-navigation-mechanisms-refs


From: David MacDonald <david100@sympatico.ca>
Date: Wednesday, 20 July 2016 at 14:34
To: Alastair Campbell <acampbell@nomensa.com>
Cc: Jonathan Avila <jon.avila@ssbbartgroup.com>, 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"?

Both Alastair and Jason make good points. I've tweaked the WIKI to amend the definition programmatically determined link context and leave the SC as is.

https://www.w3.org/WAI/GL/wiki/Modify_2.4.4_to_include_Accessible_Name_for_link_destination



Cheers,
David MacDonald



CanAdapt Solutions Inc.
Tel:  613.235.4902

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

twitter.com/davidmacd<http://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 9:28 AM, David MacDonald <david100@sympatico.ca<mailto:david100@sympatico.ca>> wrote:

I started a WIKI to capture possible amendments that reflect the emerging consensus here which I believe is:

1) to add the concept of Accessible Name
2) NOT change the requirements of the SC

The proposal is to not change the requirements of 2.4.4, but rather to shift focus away from enclosing sentence and paragraph for link context, and towards new better ways of establishing programatic context.
https://www.w3.org/WAI/GL/wiki/Modify_2.4.4_to_include_Accessible_Name_for_link_destination


Cheers,
David MacDonald



CanAdapt Solutions Inc.
Tel:  613.235.4902<tel:613.235.4902>

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

twitter.com/davidmacd<http://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 7:27 AM, David MacDonald <david100@sympatico.ca<mailto:david100@sympatico.ca>> wrote:
How about this for WCAG2.1

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, or from its Accessible Name except where the purpose of the link would be ambiguous to users in general. (Level A)


Cheers,
David MacDonald



CanAdapt Solutions Inc.
Tel:  613.235.4902<tel:613.235.4902>

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

twitter.com/davidmacd<http://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 6:33 AM, Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>> wrote:

David wrote:

> 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.



I have to agree with John’s:

> whatever we write up must be achievable in such a way as to not be dependent on a specific pattern or software.



The concept of “programmatically determined” is necessarily wider than “Accessible name”. The examples of links in the context of a structure (under headings, under table headings) is still important.



I’d be happy supplementing the current docs with description of accessible name and examples of its use, but I don’t think it can replace it.



Cheers,



-Alastair