Re: programmatically determined link context

The button and link in those two examples still both fail 4.1.2 as they 
lack an accessible name, FWIW.

P

On 19/05/2025 10:46, Ms J wrote:
> Hello
> 
> I am wondering about how 'link purpose' A says /'except where a link is 
> ambiguous to users in general' /so a non-descriptive link isnt 
> automatically a fail - it is only if it is a fail and there /is/ context 
> but it isnt *programmatically determined link context* (defined as text 
> that is in the same _paragraph <https://html.spec.whatwg.org/multipage/ 
> dom.html#paragraph>_, list item, or table cell as the link or in a table 
> header cell that is associated with the table cell that contains the link)
> 
> This is confusing because that seems like *programmatically determined 
> link context* is a weaker definition than just *programmatically 
> determined*
> 
> *For example:*
> 
> *(Ignoring other fails like name, role, value or label in name)*
> 
> <p>close<button></button></p> fails A 1.3.1 as the label is not 
> programmatically associated
> 
> <p>close<a href="#"></a></p> fails AAA 2.4.9 but not A 2.4.4 because 
> although the label is not programmatically associated with the link as 
> its accessible name, it is part of the programmatically determined link 
> context?
> 
> Thanks
> 
> Sarah
> 
> 
> 
> Sent from Outlook for iOS <https://aka.ms/o0ukef>

-- 
Patrick H. Lauke

* https://www.splintered.co.uk/
* https://github.com/patrickhlauke
* https://flickr.com/photos/redux/
* https://mastodon.social/@patrick_h_lauke

Received on Monday, 19 May 2025 09:55:59 UTC