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

Title serves as a name in cases like H65 or when  a close -X link rendered via CSS relies on title.  But this is not being suggested in above emails.   

Sailesh. ...Sent from my iPhone

> On Jul 21, 2016, at 5:28 PM, Patrick H. Lauke <redux@splintered.co.uk> wrote:
> 
>> On 21/07/2016 22:11, Sailesh Panchang wrote:
>> Patrick,
>> The page you reference clearly distinguishes accessible-name and
>> accessible-description as two properties.
>> I do not see how you conclude, "title, aria-describedby etc all form
>> part of what's taken into consideration for the accessible name
>> calculation".
> 
> I tripped up on the aria-describedby...however, "title" does form part of the accessible name calculation.
> 
> For instance, for input, the UA does the following to determine the accessible name (note point 5):
> 
> 1. Use aria-labelledby
> 2. Otherwise use aria-label
> 3. Otherwise use the associated label element
> 4. Otherwise use the placeholder attribute
> 5. Otherwise use the title attribute
> 6. If none of the above yield a usable text string there is no accessible name
> 
> P
> -- 
> Patrick H. Lauke
> 
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> 

Received on Thursday, 21 July 2016 21:47:58 UTC