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

There is a lack of consensus to make additional requirements to SC 2.4.4 or
to remove anything from the definition of programmatically determined link
text that could be *perceived* as changing the SC in Version 2.1. Nor is
there momentum to remove techniques.

We have the authority to do all these things under our 2.1 charter. We can
make some techniques only apply to WCAG2 and not to 2.1, which is
completely consistent with backward compatibility, but any changes will
need a critical mass of consensus and momentum.



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 6:27 PM, Katie Haritos-Shea GMAIL <ryladog@gmail.com
> wrote:

> About Removing techniques……(mentioned earlier in this thread)
>
>
>
> This issue leads us back to the dated and/or having Techniques mapped to a
> WCAG version discussion we had a few months back.
>
>
>
> We cannot remove Techniques that are sufficient to meet WCAG 2.0.
>
>
>
> We will have to identify which WCAG version Techniques (sufficient,
> advisory and failures) belong to
>
>
>
> ​​​​​
>
>
>
>
>
>
>
> ** katie **
>
>
>
> *Katie Haritos-Shea*
> *Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)*
>
>
>
> *Cell: 703-371-5545 <703-371-5545> **|* *ryladog@gmail.com*
> <ryladog@gmail.com> *|* *Oakton, VA **|* *LinkedIn Profile*
> <http://www.linkedin.com/in/katieharitosshea/> *|* *Office: 703-371-5545
> <703-371-5545> **|* *@ryladog* <https://twitter.com/Ryladog>
>
>
>
> *From:* White, Jason J [mailto:jjwhite@ets.org]
> *Sent:* Wednesday, July 20, 2016 4:56 PM
> *To:* Andrew Kirkpatrick <akirkpat@adobe.com>; 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"?
>
>
>
>
>
>
>
> *From:* Andrew Kirkpatrick [mailto:akirkpat@adobe.com <akirkpat@adobe.com>]
>
> *Sent:* Wednesday, July 20, 2016 4:45 PM
>
> 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.
>
>
>
> If there is no change in what passes or fails, we should handle it in
> Understanding.
>
>
>
> There is a change: if you use aria-label or similar mechanisms to override
> link text for an assistive technology, such that the label makes the
> purpose clear but the text of the link does not, it will pass, whereas it
> arguably fails now.
>
>
> ------------------------------
>
> This e-mail and any files transmitted with it may contain privileged or
> confidential information. It is solely for use by the individual for whom
> it is intended, even if addressed incorrectly. If you received this e-mail
> in error, please notify the sender; do not disclose, copy, distribute, or
> take any action in reliance on the contents of this information; and delete
> it from your system. Any other use of this e-mail is prohibited.
>
>
>
> Thank you for your compliance.
> ------------------------------
>