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



From: Alastair Campbell [mailto:acampbell@nomensa.com]
Sent: Wednesday, July 20, 2016 8:15 AM


Therefore you could have a link such as:

<a href=”/news/” aria-label=”read more”>News</a>



Which would be “news” from looking at it, but “read more” from a screen reader.



I think it opens the SC up to too many connotations and different interfaces, I’d rather keep to link-text + context.

[Jason] In your view, would <a href=”/news/” aria-label=”read more news articles”>read more</a> satisfy the current SC? Should it satisfy 2.4.4?

My suggestion yesterday was simply to promote 2.4.9 to Level AA and thereby address the needs of people who are not using ARIA-aware AT. That suggestion doesn’t seem to have gained much support so far, however.



________________________________

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.

________________________________

Received on Wednesday, 20 July 2016 13:10:55 UTC