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

a couple things to remember

1) that all techniques have to be supported by AT.  You can’t have a sufficient technique that is not supported by (the majority) of AT out there.   (per the conformance rules) 

2) any accessibility markup is by definition programmatically determinable per the guidelines -  IF IT IS ACCESSIBILITY SUPPORTED 
 (so there is usually a delay between a new markup like ARIA coming into existence and its ability to be ‘sufficient technique’.    )    And this MAY differ by part of ARIA if AT companies decide to only support part of it.  (lovely eh?) 

gregg

> On Jul 20, 2016, at 4:56 PM, White, Jason J <jjwhite@ets.org> wrote:
> 
>  
>   <>
> From: Andrew Kirkpatrick [mailto:akirkpat@adobe.com <mailto: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.
>