Don't use "click here" as link text

Re:Don't use "click here" as link text – W3C by danillonunes on Wednesday July 02, 2025 @12:12PM (#44445488)

The problem here is that the screen reader will just read the link text and not the contract around it. In this case, the correct examples proposed by W3C will read just as "Amaya”, which are almost as unhelpful.

[ Parent | on HN ]

Re:Don't use "click here" as link text – W3C by burningChrome on Wednesday July 02, 2025 @12:54PM (#44446001)

Even the WCAG level A success criteria clearly states:

The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.

https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-...

Having a single word announced by the screen reader to me would fail this criteria.

[ Parent | on HN ]

Re:Don't use "click here" as link text – W3C by danlitt on Wednesday July 02, 2025 @03:16PM (#44447719)

together with its programmatically determined link context really is the operative phrase in this quote. I would encourage you to actually read the examples on the page you link to - several of them announce just one or two words.

[ Parent | on HN ]

Re:Don't use "click here" as link text – W3C by burningChrome on Wednesday July 02, 2025 @05:00PM (#44448774)

OP's comment addressed that:

The problem here is that the screen reader will just read the link text and not the contract around it.

I would encourage you to read OP's comment first?

[ Parent | on HN ]

Re:Don't use "click here" as link text – W3C by danlitt on Thursday July 03, 2025 @04:18PM (#44458817)

I'm not sure what you mean now. Did you intend your quote from the WCAG to support OP's point, or to indicate that the screen reader has a bug?

[ Parent | on HN ]