Why Your Links Should Never Say “Click Here”
31–40 of 93 posts
Re: Why Your Links Should Never Say “Click Here”
#32The only thing I don't entirely agree with is:
1) Wrong: "first Falling Bear gets run over" 2) Right: "first Falling Bear gets run over"
I think they're just different. In the first case, I expect a link to to a photo of Falling Bear as he's getting run over. In the second case, I expect a link to a page on Falling Bear, that may have nothing to do with when he was run over.
But I think the distinction is important to make.
Re: Why Your Links Should Never Say “Click Here”
#33I believe people process text faster than they process visual cues like fancy icons or underlined anchor links. "Click here to view demo" seems to be faster to process, and more explicit than a fancy "View demo" hyperlink (CSS re-styling of links does not help in that respect). This is pure speculation of course, but one might try to do the reaction-time experiment.
Re: Why Your Links Should Never Say “Click Here”
#34D Curtis' A/B testing data does not support this: http://www.dustincurtis.com/you_should_follow_me_on_twitter....
Re: Why Your Links Should Never Say “Click Here”
#35Re: Why Your Links Should Never Say “Click Here”
#36It's more than just links. Anything you want the user to interact with should be self-explanatory. Buttons shouldn't say yes/no or ok/cancel. They should describe the actual action. "Leave this page" or "stay on this page", "Remove from cart" or "keep in cart", and so on.
I'm not convinced -- I find the Vista dialogs really confusing for that reason. First, I read the question, "Do you want to save this file?" Then I naturally expect "Yes", "No", "Cancel" -- effortless to understand. If I see "Save this file", "Don't save this file", "Return to application", it takes a lot longer, because I have to parse each button, which is redundant and annoying since I' already parsed the question…
Also, yes/no/cancel are only "effortless" to understand if you read the question first (not everyone does that) and if the question is simple.
An example of doing it wrong: my classroom had an unstable piece of software that would occasionally pop up a long error message that asked "do you wish to continue?" at the end; students wouldn't read the whole thing, but would just click "no", which closed the software.
If the same popup had the error message and then buttons marked "continue" or "close program", it would have been far more straightforward.
Re: Why Your Links Should Never Say “Click Here”
#37Does anyone actually have strong evidence supporting it (i.e. quantifiable UX studies)?
I've always found the reasons given for this kind of thing rather vague and arguable:
- Don't use click: I really doubt users care
- Don't use 'here': fine, being specific is good where you can
- Link to nouns: seems arguable. Surely if you're linking to a bear then use the noun. If you're linking to a bear getting run over, 'getting run over' is the action here, and should be the link, especially if you have more than one action to link to.
- Link to specifics: yeah, you already said that one.
- End on a link. Hmm.. I'd need to see numbers to believe it
Re: Why Your Links Should Never Say “Click Here”
#38The article gives some good advice, but I think it's always worth considering that links should be emphasized in the context of both HTML and CSS (and static images and any JS magic).
Although I think the word "click" should not be a part of any link in 2012, you shouldn't follow this guide unquestioningly in other regards.
Re: Why Your Links Should Never Say “Click Here”
#39Re: Why Your Links Should Never Say “Click Here”
#40At very least if you are planning to change around your links based on this article give a look to Dustin Curtis' data-driven experiment on changing link names:
www.dustincurtis.com/you_should_follow_me_on_twitter.html