Top
Best
New

Posted by theandrewbailey 7/2/2025

Don’t use “click here” as link text (2001)(www.w3.org)
520 points | 343 commentspage 5
bArray 7/2/2025|
I disagree. I think we need to make it clear that following hyperlinks should always be a cognitive choice.

> To download W3C's editor/browser Amaya, [click here].

This gives you an option, where multiple options may be available.

> To download Amaya, go to the [Amaya Website] and get the necessary software.

This is even better, as 'click here' assumes the input device.

> Get [Amaya]!

Whilst being simpler, it does not make clear that the action is optional.

Whether I click something may require some additional information around the link, for example:

> To download W3C's free editor/browser Amaya, go to the [Amaya Website] and select the latest version on the home page.

Now I know that it's free, and I have instructions to carry out to find what I'm looking for.

Cthulhu_ 7/2/2025||
This is very much from a sighted person's point of view. When you use screen readers, you can switch to a 'links' navigation mode and only go through links, in which case all you'd hear would be "click here", "Amaya website" and "Amaya".

See also https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-..., also keeping in mind that since June, the underlying WCAG guideline is a EU-wide legal requirement for company websites.

tempfile 7/2/2025|||
I don't think this is right. The WCAG allows for "programmatically determined link context" which includes text surrounding the actual link. "click here" is bad but "Amaya website" or "Amaya" are fine.

e.g. from the WCAG examples you link to:

> An account registration page requires successful completion of a [Turing test](https://www.w3.org/TR/turingtest/) before the registration form can be accessed.

bArray 7/2/2025|||
> This is very much from a sighted person's point of view. When you use screen readers, you can switch to a 'links' navigation mode and only go through links, in which case all you'd hear would be "click here", "Amaya website" and "Amaya".

I think this is a UX problem with screen readers, and actually probably something LLMs might massively help with. If I was designing something for screen readers, I would probably have interactive elements within a context window, i.e.:

    <context>To download W3C's free editor/browser Amaya, go to the <a href="..">Amaya Website</a> and select the latest version on the home page.</context>
The user would hear "Amaya Website" and would then have some ability to also hear the link context. For pages missing the context windows some attempt could be made to create one automatically.

> See also https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-... , also keeping in mind that since June, the underlying WCAG guideline is a EU-wide legal requirement for company websites.

On this page itself, within the box "Success Criterion (SC)" the listener would hear "purpose of each link", "programmatically determined link context", "ambiguous to users in general". The last one is, well, ambiguous to users in general. Even as a sighted person, without selecting it, I wouldn't know what it is actually going to link to.

I would say that the web is generally actively hostile towards screen readers, and not because of a lack of WCAG adoption. You have text in images (not just static, but also GIFs), JS heavy components, delayed loading, dependant interactions (such as captchas, navigation drop downs, etc), infinite scrolling - the list just goes on. The web is primary a highly visual space and likely will remain so.

I don't think the EU's accessibility act is actually enforceable [1]. Unlike cookies, some of the changes required are massive, to the point where it may not even be worth existing in the EU market if it's enforced.

> Incorporating captions into video content, as well as providing audio descriptions and transcripts

Even proving you are compliant is a lot of cost, which includes audits and training staff. You can always trust the EU to regulate itself out of being competitive.

[1] https://www.wcag.com/compliance/european-accessibility-act/

ivan_gammel 7/2/2025|||
I don’t think either of the suggested options delivers the best possible UX. Copy of course depends on context, but „click here“ is never justified as the best alternative.

You can do:

• [Download X] - immediate download link.

• [Learn more about X] - go to webpage, discover other interactions there

• [Register to download X] - if registration required

Short and concise copy is generally better, extra information rarely makes content better.

bArray 7/2/2025||
I think it really depends on the context. In a news article it rarely makes the content better, but in a documentation wiki, the context can be everything. I think we are fooling ourselves to suggest that there is zero nuance and that there is a 100% correct approach always.
hnlmorg 7/2/2025||
Best:

> You can download the Amaya Browser from [Amaya’s download page]

It’s both explicit for sighted reader and screen readers too.

Yes there’s some duplicated words. But the point of that paragraph isn’t to be artistic, it’s to be informative. You can save the creative word play for your regular paragraphs.

LocalPCGuy 7/2/2025|||
I would even say you could go with if duplicated words is an issue:

  You can [get the Amaya Browser] from the download page
hnlmorg 7/2/2025||
Nice refinement there.
bArray 7/2/2025|||
I still think that the missing context is an issue. Imagine the page is some 10k words, by the time you get to the bottom, you might not remember what "Amaya" is. So just saying "Amaya's download page" tells the user that it is a download, but nothing about what it is a download for.

I wonder how successful the screen reader experience is for using the web. Without checking URLs, how can they be sure for example they don't enter this credit card details on http://bank.xyz/scam_page , rather than https://bank.com ?

Or how do they know whether the download page automatically downloads the file whilst they are on it?

I can only imagine that using the web is extremely difficult.

hnlmorg 7/2/2025||
Yeah, context matters. If it’s a Amaya product page then the context is already there. But if it’s a large article that meanders across a few topics, then your approach would be better. Though in that scenario I think you’re better still by directing people to a product page instead of a download page.
johnisgood 7/2/2025||
> To download W3C's editor/browser Amaya, click here.

"click here" should be a direct link to the latest version. You click on it, it should download the latest version.

guerrilla 7/2/2025||
Okay but it doesn't say why. Why should one leave verbs out?
DonHopkins 7/2/2025||
As ClickOps is to DevOps, ClickSplaining is to ManSplaining.

Nobody appreciates being talked down to with "click here" as if they can't figure out how to follow a link.

nikolayasdf123 7/2/2025||
I am found of Apple content design has "Learn more..." links at the end of paragraphs. Those look very consistent and look well
kevinsync 7/2/2025||
My stomach is churning already knowing I'm about to type a short-sighted hot take related to LLMs, but I do wonder what a screen reader would look like that could provide a "summarized" version of any given web page (assumingly via LLM). Basically allow the user to swap between the full page rendered with current methodology / presentation of content and links, and a version of the same page with a summarized version of the text content + a collated, deduped section of actions found in the content.

ex.

To download W3C's editor/browser Amaya, [click here].

[Download Amaya]

[Click here] to get Amaya for Windows

All collapse into something singular and sensible like [Download Amaya installer for Windows here] as an action inside the action section.

I don't know. I should probably put on a sleeping mask and navigate the web via a screen reader one of these days to really experience how things are.

lillecarl 7/2/2025|
When we can run our own models that are good enough on local hardware (practically) it'll really take off, I believe AI accelerators in end user electronics will revolutionize how we utilize computers.

> I don't know. I should probably put on a sleeping mask and navigate the web via a screen reader one of these days to really experience how things are. The difference is that it wouldn't be like experiencing it through a screen reader, it'd be like experiencing it with a screen reader that you can't use and will never be motivated enough to learn. Some blind people are known to listen to code in "reading speed" which is pretty incredible.

You'd be like standing on skis for the first time, or using Vim

rednafi 7/2/2025||
I’m reading the comments and thinking: only the HN crowd could get so worked up about something so trivial.
drellybochelly 7/2/2025||
It's a reasonable CTA for simple cases, but definitely makes assumptions and presupposes a bit.
theendisney 7/2/2025||
But my website is called go-here.nl
yard2010 7/2/2025|
Remember when googling "click here" led to the acrobat reader download page? I member!
More comments...