<?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: Click here if you don&#8217;t know what a link is</title>
	<atom:link href="http://www.jeepstone.co.uk/2009/12/23/click-here-if-you-dont-know-what-a-link-is/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jeepstone.co.uk/2009/12/23/click-here-if-you-dont-know-what-a-link-is/</link>
	<description>The home of Pete Jones</description>
	<lastBuildDate>Sat, 28 Jan 2012 16:02:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Olly</title>
		<link>http://www.jeepstone.co.uk/2009/12/23/click-here-if-you-dont-know-what-a-link-is/comment-page-1/#comment-988</link>
		<dc:creator>Olly</dc:creator>
		<pubDate>Thu, 24 Dec 2009 10:53:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeepstone.co.uk/?p=79#comment-988</guid>
		<description>Yes, sometimes you do need &quot;click here&quot; - but it tends to be a workaround at best. It was born out of the old &quot;mystery meat&quot; navigation problem. Rather than fixing the core issue of making clickable items actually look clickable, people used a quick text fix.

My real issue with &quot;click here&quot; is that we&#039;re patronising users. For the most part, they&#039;re not idiots and we shouldn&#039;t treat them as such. They know how to use the internet. (The pedant in me wants to point out the input devices where you don&#039;t &quot;click&quot; as such too.)

If your link isn&#039;t being clicked, perhaps it doesn&#039;t look enough like a link? Convention says they should be underlined in most cases (etc). But if it&#039;s not in body text, or it&#039;s the main call to action on a page, perhaps you should make it look like a button? Maybe combine the two somehow? Maybe the language isn&#039;t strong enough?

You know the keyword advertising you see on some sites (usually with double-underlines)? That  sort of thing drives me up the wall because it actively puts people off clicking real links. But that&#039;s a whole other issue.</description>
		<content:encoded><![CDATA[<p>Yes, sometimes you do need &#8220;click here&#8221; &#8211; but it tends to be a workaround at best. It was born out of the old &#8220;mystery meat&#8221; navigation problem. Rather than fixing the core issue of making clickable items actually look clickable, people used a quick text fix.</p>
<p>My real issue with &#8220;click here&#8221; is that we&#8217;re patronising users. For the most part, they&#8217;re not idiots and we shouldn&#8217;t treat them as such. They know how to use the internet. (The pedant in me wants to point out the input devices where you don&#8217;t &#8220;click&#8221; as such too.)</p>
<p>If your link isn&#8217;t being clicked, perhaps it doesn&#8217;t look enough like a link? Convention says they should be underlined in most cases (etc). But if it&#8217;s not in body text, or it&#8217;s the main call to action on a page, perhaps you should make it look like a button? Maybe combine the two somehow? Maybe the language isn&#8217;t strong enough?</p>
<p>You know the keyword advertising you see on some sites (usually with double-underlines)? That  sort of thing drives me up the wall because it actively puts people off clicking real links. But that&#8217;s a whole other issue.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

