<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Don&#8217;t say &#8216;click here&#8217; on link text</title>
	<atom:link href="http://www.goodusability.co.uk/2009/01/dont-say-click-here-on-link-text/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.goodusability.co.uk/2009/01/dont-say-click-here-on-link-text/</link>
	<description></description>
	<lastBuildDate>Thu, 11 Mar 2010 15:55:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Matthijs</title>
		<link>http://www.goodusability.co.uk/2009/01/dont-say-click-here-on-link-text/comment-page-1/#comment-2444</link>
		<dc:creator>Matthijs</dc:creator>
		<pubDate>Fri, 06 Nov 2009 09:35:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=484#comment-2444</guid>
		<description>Thanks for the advice, I must admit that I immediatly started scanning my own design for any of these usability errors.</description>
		<content:encoded><![CDATA[<p>Thanks for the advice, I must admit that I immediatly started scanning my own design for any of these usability errors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hamill</title>
		<link>http://www.goodusability.co.uk/2009/01/dont-say-click-here-on-link-text/comment-page-1/#comment-980</link>
		<dc:creator>David Hamill</dc:creator>
		<pubDate>Mon, 30 Mar 2009 07:57:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=484#comment-980</guid>
		<description>Hi Marc, thanks for the comment. I&#039;m sorry that you find it so difficult to take this advice. After all, it is good advice.

By alt attributes, I take it you actually mean title attributes. Alt attributes are used for elements like images. The text in an alt attribute is used for when the element itself is not available (because it hasn&#039;t loaded or it can&#039;t be seen by the user). The title attribute on the other hand is used on anchor tags to provide a little more information about where the link goes. In a perfect world you would never need to use a title attribute on a link. This is because the link text itself would be descriptive enough. 

However I take your point, there are some links on my site that might benefit from a title attribute. I&#039;ll make a point of going through it and adding them where they would be helpful. Thanks for the feedback.</description>
		<content:encoded><![CDATA[<p>Hi Marc, thanks for the comment. I&#8217;m sorry that you find it so difficult to take this advice. After all, it is good advice.</p>
<p>By alt attributes, I take it you actually mean title attributes. Alt attributes are used for elements like images. The text in an alt attribute is used for when the element itself is not available (because it hasn&#8217;t loaded or it can&#8217;t be seen by the user). The title attribute on the other hand is used on anchor tags to provide a little more information about where the link goes. In a perfect world you would never need to use a title attribute on a link. This is because the link text itself would be descriptive enough. </p>
<p>However I take your point, there are some links on my site that might benefit from a title attribute. I&#8217;ll make a point of going through it and adding them where they would be helpful. Thanks for the feedback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Brooks</title>
		<link>http://www.goodusability.co.uk/2009/01/dont-say-click-here-on-link-text/comment-page-1/#comment-979</link>
		<dc:creator>Marc Brooks</dc:creator>
		<pubDate>Mon, 30 Mar 2009 04:28:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=484#comment-979</guid>
		<description>I find it hard to take advice on anchors from someone who doesn&#039;t bother to put alt attributes on them that describe where the link goes...</description>
		<content:encoded><![CDATA[<p>I find it hard to take advice on anchors from someone who doesn&#8217;t bother to put alt attributes on them that describe where the link goes&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ronÃ©/di/kristu</title>
		<link>http://www.goodusability.co.uk/2009/01/dont-say-click-here-on-link-text/comment-page-1/#comment-978</link>
		<dc:creator>ronÃ©/di/kristu</dc:creator>
		<pubDate>Fri, 27 Mar 2009 12:59:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=484#comment-978</guid>
		<description>Click here is a promise that often isn&#039;t backed up. I kinda feel cheated if the promise turns out to be a misleading offer or content.

In contrast &quot;shy links&quot; - I think I coined a sexy term: a gentle click here link that doesn&#039;t appear like a click here link - feel more like a recommendation and not an offer that you might regret.

So maybe from that point of view it is save to say that &quot;cold linking&quot; (mash up consisting of &quot;click here&quot; and &quot;cold call&quot;) deserves the boot. ;)

PS: shy linking/cold linking - I already love these terms. ;)</description>
		<content:encoded><![CDATA[<p>Click here is a promise that often isn&#8217;t backed up. I kinda feel cheated if the promise turns out to be a misleading offer or content.</p>
<p>In contrast &#8220;shy links&#8221; &#8211; I think I coined a sexy term: a gentle click here link that doesn&#8217;t appear like a click here link &#8211; feel more like a recommendation and not an offer that you might regret.</p>
<p>So maybe from that point of view it is save to say that &#8220;cold linking&#8221; (mash up consisting of &#8220;click here&#8221; and &#8220;cold call&#8221;) deserves the boot. <img src='http://www.goodusability.co.uk/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>PS: shy linking/cold linking &#8211; I already love these terms. <img src='http://www.goodusability.co.uk/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karen</title>
		<link>http://www.goodusability.co.uk/2009/01/dont-say-click-here-on-link-text/comment-page-1/#comment-954</link>
		<dc:creator>Karen</dc:creator>
		<pubDate>Fri, 20 Mar 2009 15:56:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=484#comment-954</guid>
		<description>I had to tweet about this article today.
I notice the problem developing with small businesses who try to do their website on their own (&quot;have blog, will make website&quot; and &quot;no money&quot;). They have seen &quot;click here&quot; for years, so they think that is what they should do. It will take lots of patience to weed out these problems. Now, thanks to you, we can now just point offenders to this article. :)</description>
		<content:encoded><![CDATA[<p>I had to tweet about this article today.<br />
I notice the problem developing with small businesses who try to do their website on their own (&#8220;have blog, will make website&#8221; and &#8220;no money&#8221;). They have seen &#8220;click here&#8221; for years, so they think that is what they should do. It will take lots of patience to weed out these problems. Now, thanks to you, we can now just point offenders to this article. <img src='http://www.goodusability.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hamill</title>
		<link>http://www.goodusability.co.uk/2009/01/dont-say-click-here-on-link-text/comment-page-1/#comment-926</link>
		<dc:creator>David Hamill</dc:creator>
		<pubDate>Thu, 12 Mar 2009 16:03:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=484#comment-926</guid>
		<description>Fair enough, it was worth a try.</description>
		<content:encoded><![CDATA[<p>Fair enough, it was worth a try.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yves</title>
		<link>http://www.goodusability.co.uk/2009/01/dont-say-click-here-on-link-text/comment-page-1/#comment-925</link>
		<dc:creator>Yves</dc:creator>
		<pubDate>Thu, 12 Mar 2009 07:48:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=484#comment-925</guid>
		<description>Hm, I don&#039;t like the German cooking book style... it&#039;s &quot;Man nehme 3 Eier&quot; which translates to something like &quot;You take 3 eggs&quot;, or more explicitly &quot;One takes 3 eggs.&quot; Strange wording they have there... That style is sometimes used for fun in other contexts just to indicate a recipe/steps to do.

As for the imperative form, I&#039;m very much used to and would like to compare it with menu commands in common applications. Take &quot;edit/copy/paste&quot; for example: It&#039;s &quot;Bearbeiten/Kopieren/EinfÃ¼gen&quot; - all infinitive forms. In English you can&#039;t tell because it&#039;s the same. &quot;Sehen Sie alle 25 Fotos (an)&quot; sounds strange to my ears. Whereas &quot;Registrieren Sie sich jetzt!&quot; (&quot;Register now!&quot;; notice the exclamation mark) fits perfectly into advertisement talk.</description>
		<content:encoded><![CDATA[<p>Hm, I don&#8217;t like the German cooking book style&#8230; it&#8217;s &#8220;Man nehme 3 Eier&#8221; which translates to something like &#8220;You take 3 eggs&#8221;, or more explicitly &#8220;One takes 3 eggs.&#8221; Strange wording they have there&#8230; That style is sometimes used for fun in other contexts just to indicate a recipe/steps to do.</p>
<p>As for the imperative form, I&#8217;m very much used to and would like to compare it with menu commands in common applications. Take &#8220;edit/copy/paste&#8221; for example: It&#8217;s &#8220;Bearbeiten/Kopieren/EinfÃ¼gen&#8221; &#8211; all infinitive forms. In English you can&#8217;t tell because it&#8217;s the same. &#8220;Sehen Sie alle 25 Fotos (an)&#8221; sounds strange to my ears. Whereas &#8220;Registrieren Sie sich jetzt!&#8221; (&#8220;Register now!&#8221;; notice the exclamation mark) fits perfectly into advertisement talk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hamill</title>
		<link>http://www.goodusability.co.uk/2009/01/dont-say-click-here-on-link-text/comment-page-1/#comment-922</link>
		<dc:creator>David Hamill</dc:creator>
		<pubDate>Wed, 11 Mar 2009 09:26:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=484#comment-922</guid>
		<description>Fantastic question Yves! Personally my knowledge of German isn&#039;t good enough to have tested with German users. However I&#039;ll try to answer your question. There are 2 things to consider here. What you&#039;re talking about appears to be a call to action. This takes the imperative form in English and French i.e &quot;Find a friend&quot;, &quot;Trouvez un ami&quot;. In German you should use the equivalent for a call to action. 

Look in a German cook book. How does it phrase the instructions? In an English cook book it would have numbered instructions, &quot;Mix the sauce together&quot; for example. I would suggest following whatever structure you see there. Your call to action is after all an instruction.

But not all links need to be a call to action. The example you give &quot;Alle 25 Fotos in dieser Sammlung anzeigen&quot; is still frontloaded with important information. &quot;Alle 25 Fotos&quot; makes it clear what the link is for at the very start of the link. So is quicker to scan than if &quot;anzeigen&quot; was at the front. In any case I would opt for a verb that described what the user wanted to do. This would be the German equvalents for &quot;See&quot; of &quot;View&quot;. But that&#039;s a minor point.</description>
		<content:encoded><![CDATA[<p>Fantastic question Yves! Personally my knowledge of German isn&#8217;t good enough to have tested with German users. However I&#8217;ll try to answer your question. There are 2 things to consider here. What you&#8217;re talking about appears to be a call to action. This takes the imperative form in English and French i.e &#8220;Find a friend&#8221;, &#8220;Trouvez un ami&#8221;. In German you should use the equivalent for a call to action. </p>
<p>Look in a German cook book. How does it phrase the instructions? In an English cook book it would have numbered instructions, &#8220;Mix the sauce together&#8221; for example. I would suggest following whatever structure you see there. Your call to action is after all an instruction.</p>
<p>But not all links need to be a call to action. The example you give &#8220;Alle 25 Fotos in dieser Sammlung anzeigen&#8221; is still frontloaded with important information. &#8220;Alle 25 Fotos&#8221; makes it clear what the link is for at the very start of the link. So is quicker to scan than if &#8220;anzeigen&#8221; was at the front. In any case I would opt for a verb that described what the user wanted to do. This would be the German equvalents for &#8220;See&#8221; of &#8220;View&#8221;. But that&#8217;s a minor point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yves</title>
		<link>http://www.goodusability.co.uk/2009/01/dont-say-click-here-on-link-text/comment-page-1/#comment-921</link>
		<dc:creator>Yves</dc:creator>
		<pubDate>Wed, 11 Mar 2009 08:14:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=484#comment-921</guid>
		<description>You write &quot;Good link text is front-loaded, so the most important words are at the front.&quot; I can well imagine that a link of &quot;Show all 25 photos from this collection&quot; is easy to see as it begins with &quot;show&quot; which is something the user wants to do. But this is in English and probably also French. In German for example it would be &quot;Alle 25 Fotos in dieser Sammlung anzeigen&quot;. (anzeigen = engl. show; also it&#039;s infinitive form, not imperative.) Here, the action word comes at the very end. This is common in the German language. Do you think it&#039;s a problem or are German users maybe used to find those trigger words near the end of the link text? Or does it not matter for such short link texts?</description>
		<content:encoded><![CDATA[<p>You write &#8220;Good link text is front-loaded, so the most important words are at the front.&#8221; I can well imagine that a link of &#8220;Show all 25 photos from this collection&#8221; is easy to see as it begins with &#8220;show&#8221; which is something the user wants to do. But this is in English and probably also French. In German for example it would be &#8220;Alle 25 Fotos in dieser Sammlung anzeigen&#8221;. (anzeigen = engl. show; also it&#8217;s infinitive form, not imperative.) Here, the action word comes at the very end. This is common in the German language. Do you think it&#8217;s a problem or are German users maybe used to find those trigger words near the end of the link text? Or does it not matter for such short link texts?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Fox</title>
		<link>http://www.goodusability.co.uk/2009/01/dont-say-click-here-on-link-text/comment-page-1/#comment-210</link>
		<dc:creator>Andy Fox</dc:creator>
		<pubDate>Sun, 22 Feb 2009 13:09:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=484#comment-210</guid>
		<description>Good point and this was what was going through my mind when taking the decision. The site is a training tool where people are specifically pointed to log on and use for their job so they wouldn&#039;t go through any other hyperlinks to get there.

It is an exception!</description>
		<content:encoded><![CDATA[<p>Good point and this was what was going through my mind when taking the decision. The site is a training tool where people are specifically pointed to log on and use for their job so they wouldn&#8217;t go through any other hyperlinks to get there.</p>
<p>It is an exception!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
