<?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: Crimes Against Hypertext</title>
	<atom:link href="http://www.sitepoint.com/blogs/2009/01/13/crimes-against-hypertext/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2009/01/13/crimes-against-hypertext/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<lastBuildDate>Sat, 07 Nov 2009 23:35:20 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Meitar</title>
		<link>http://www.sitepoint.com/blogs/2009/01/13/crimes-against-hypertext/comment-page-2/#comment-883154</link>
		<dc:creator>Meitar</dc:creator>
		<pubDate>Wed, 25 Feb 2009 06:52:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3882#comment-883154</guid>
		<description>&lt;blockquote cite=&quot;#comment-883012&quot;&gt;I am wondering what others think of the full URL links?&lt;/blockquote&gt;

I think we&#039;d all do well to remember the fact that in Tim Berners-Lee&#039;s original vision of the Web, &lt;strong&gt;the URI was never intended to be user-visible&lt;/strong&gt;! Naturally, my interpretation of this is that a link should be &lt;em&gt;natural language&lt;/em&gt;, not a URL. :)</description>
		<content:encoded><![CDATA[<blockquote cite="#comment-883012"><p>I am wondering what others think of the full URL links?</p></blockquote>
<p>I think we&#8217;d all do well to remember the fact that in Tim Berners-Lee&#8217;s original vision of the Web, <strong>the URI was never intended to be user-visible</strong>! Naturally, my interpretation of this is that a link should be <em>natural language</em>, not a URL. :)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: freddy</title>
		<link>http://www.sitepoint.com/blogs/2009/01/13/crimes-against-hypertext/comment-page-2/#comment-883030</link>
		<dc:creator>freddy</dc:creator>
		<pubDate>Tue, 24 Feb 2009 22:37:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3882#comment-883030</guid>
		<description>Blaming the user for being &quot;stupid&quot; or even poorly educated is not new to the web, developers have been doing this since GUI interfaces were invented. It&#039;s the developer&#039;s job to design interfaces that are usable. What&#039;s usable? Doesn&#039;t this depend on your target user base? If your client wants &#039;click here&#039; because the users are newbies or whatever the problem is, then so be it.  I&#039;m tired of seeing projects handed to smiling yes-ma&#039;am consultants while I argue for elegant code or doing it &#039;right&#039;.</description>
		<content:encoded><![CDATA[<p>Blaming the user for being &#8220;stupid&#8221; or even poorly educated is not new to the web, developers have been doing this since GUI interfaces were invented. It&#8217;s the developer&#8217;s job to design interfaces that are usable. What&#8217;s usable? Doesn&#8217;t this depend on your target user base? If your client wants &#8216;click here&#8217; because the users are newbies or whatever the problem is, then so be it.  I&#8217;m tired of seeing projects handed to smiling yes-ma&#8217;am consultants while I argue for elegant code or doing it &#8216;right&#8217;.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: LadyNama</title>
		<link>http://www.sitepoint.com/blogs/2009/01/13/crimes-against-hypertext/comment-page-2/#comment-883012</link>
		<dc:creator>LadyNama</dc:creator>
		<pubDate>Tue, 24 Feb 2009 21:45:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3882#comment-883012</guid>
		<description>Well let&#039;s also remember accessibility! &quot;Click here&quot; is not accessible for users using a screen reader. Many people use the scan setting which will scan all of the links. If the links are all &quot;click here&quot; how someone to know what the link is for?

I cannot stand lists of links that are full URL&#039;s either. I am wondering what others think of the full URL links?</description>
		<content:encoded><![CDATA[<p>Well let&#8217;s also remember accessibility! &#8220;Click here&#8221; is not accessible for users using a screen reader. Many people use the scan setting which will scan all of the links. If the links are all &#8220;click here&#8221; how someone to know what the link is for?</p>
<p>I cannot stand lists of links that are full URL&#8217;s either. I am wondering what others think of the full URL links?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: 5minuteargument</title>
		<link>http://www.sitepoint.com/blogs/2009/01/13/crimes-against-hypertext/comment-page-1/#comment-882860</link>
		<dc:creator>5minuteargument</dc:creator>
		<pubDate>Tue, 24 Feb 2009 12:11:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3882#comment-882860</guid>
		<description>@Yanni, @le sigh: However much you think your users understand &quot;Click here&quot; better, take into account what a screen full of &quot;click here&quot; links looks like - descriptive link text is good for scanning as well as careful reading.

There&#039;s a very fine balance between linking your existing text in such a way that it is obviously a link (so you don&#039;t need to write &quot;Click here&quot;) and not disrupting the reading flow by making the link &lt;em&gt;too&lt;/em&gt; distracting. Techniques to achieve the latter include shortening links (appropriately, of course) and using border-bottom instead of text-decoration.

Don&#039;t forget that an increasing number of users don&#039;t actually &quot;click&quot; either - if you really think your users are that stupid, you should probably reword all your &quot;click here&quot; links to &quot;activate this link&quot; or something equally ridiculous. Please don&#039;t adopt bad practises because you think some of your users are stupid - that&#039;s a sure-fire way of making &lt;em&gt;everyone&lt;/em&gt; stupid whether they like it or not.</description>
		<content:encoded><![CDATA[<p>@Yanni, @le sigh: However much you think your users understand &#8220;Click here&#8221; better, take into account what a screen full of &#8220;click here&#8221; links looks like &#8211; descriptive link text is good for scanning as well as careful reading.</p>
<p>There&#8217;s a very fine balance between linking your existing text in such a way that it is obviously a link (so you don&#8217;t need to write &#8220;Click here&#8221;) and not disrupting the reading flow by making the link <em>too</em> distracting. Techniques to achieve the latter include shortening links (appropriately, of course) and using border-bottom instead of text-decoration.</p>
<p>Don&#8217;t forget that an increasing number of users don&#8217;t actually &#8220;click&#8221; either &#8211; if you really think your users are that stupid, you should probably reword all your &#8220;click here&#8221; links to &#8220;activate this link&#8221; or something equally ridiculous. Please don&#8217;t adopt bad practises because you think some of your users are stupid &#8211; that&#8217;s a sure-fire way of making <em>everyone</em> stupid whether they like it or not.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: le sigh</title>
		<link>http://www.sitepoint.com/blogs/2009/01/13/crimes-against-hypertext/comment-page-1/#comment-867384</link>
		<dc:creator>le sigh</dc:creator>
		<pubDate>Fri, 23 Jan 2009 20:38:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3882#comment-867384</guid>
		<description>The eternal design dilemma: do I remove &quot;click here&quot; because leaving it in is stupid, or do I leave it in place because my users are stupid?

The only solution seems to be to sell everything I own and live in the woods. :(</description>
		<content:encoded><![CDATA[<p>The eternal design dilemma: do I remove &#8220;click here&#8221; because leaving it in is stupid, or do I leave it in place because my users are stupid?</p>
<p>The only solution seems to be to sell everything I own and live in the woods. :(</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Yanni</title>
		<link>http://www.sitepoint.com/blogs/2009/01/13/crimes-against-hypertext/comment-page-1/#comment-866090</link>
		<dc:creator>Yanni</dc:creator>
		<pubDate>Wed, 21 Jan 2009 11:43:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3882#comment-866090</guid>
		<description>I agree with the idea of right usage of links, but I am afraid you are missing out &quot;the average target visitor&quot; in the equation. 
Click Here is really a bad way of linking but it&#039;s so popular, because so many people are asking WHERE DO I CLICK while staring at a link. This is what moved most of designers to use this pointless click here link. One of my customers last week actually forced me to use CLICK HERE (of course I added at least a description of what you expect to get from the link) for his links because he knows what his customers are like with computers and internet.
The above instructions and comments all have a point but I am afraid only work best for more advanced users.
Then again, you may claim ok, let&#039;s educate the masses, but who is going to sacrifice first their usability of their site and eventually their online sales to educate the masses? Any volunteers? :)</description>
		<content:encoded><![CDATA[<p>I agree with the idea of right usage of links, but I am afraid you are missing out &#8220;the average target visitor&#8221; in the equation.<br />
Click Here is really a bad way of linking but it&#8217;s so popular, because so many people are asking WHERE DO I CLICK while staring at a link. This is what moved most of designers to use this pointless click here link. One of my customers last week actually forced me to use CLICK HERE (of course I added at least a description of what you expect to get from the link) for his links because he knows what his customers are like with computers and internet.<br />
The above instructions and comments all have a point but I am afraid only work best for more advanced users.<br />
Then again, you may claim ok, let&#8217;s educate the masses, but who is going to sacrifice first their usability of their site and eventually their online sales to educate the masses? Any volunteers? :)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: mgaigg</title>
		<link>http://www.sitepoint.com/blogs/2009/01/13/crimes-against-hypertext/comment-page-1/#comment-865663</link>
		<dc:creator>mgaigg</dc:creator>
		<pubDate>Tue, 20 Jan 2009 19:41:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3882#comment-865663</guid>
		<description>In the beginning was the link... PLEASE (pleeaaasssse) make links meaningful, not because this article or WCAG tells you, no, for your own good.

I suggest the following blog entry &lt;a href=&quot;http://www.mgitsolutions.com/blog/2008/10/design-guidelines-links/&quot; rel=&quot;nofollow&quot;&gt;Design Guidelines: Links&lt;/a&gt; that outlines important rules for creating links.

Personally I still cannot understand that - like Andrew says - links are so easy to create but still not done right.</description>
		<content:encoded><![CDATA[<p>In the beginning was the link&#8230; PLEASE (pleeaaasssse) make links meaningful, not because this article or WCAG tells you, no, for your own good.</p>
<p>I suggest the following blog entry <a href="http://www.mgitsolutions.com/blog/2008/10/design-guidelines-links/" rel="nofollow">Design Guidelines: Links</a> that outlines important rules for creating links.</p>
<p>Personally I still cannot understand that &#8211; like Andrew says &#8211; links are so easy to create but still not done right.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Stevie D</title>
		<link>http://www.sitepoint.com/blogs/2009/01/13/crimes-against-hypertext/comment-page-1/#comment-865478</link>
		<dc:creator>Stevie D</dc:creator>
		<pubDate>Tue, 20 Jan 2009 12:45:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3882#comment-865478</guid>
		<description>@chaoley
&lt;blockquote&gt;The title attribute is not optional, it’s there for accesibility reasons. Visually impaired users with screen readers for example.&lt;/blockquote&gt;
The &lt;code&gt;title&lt;/code&gt; attribute &lt;strong&gt;is&lt;/strong&gt; optional. It should only be used where additional text, over and above the link text and surrounding context, may be needed for users to understand the link destination/purpose.

Adding a &lt;code&gt;title&lt;/code&gt; attribute to help accessibility won&#039;t always help. Screen readers may or may not read the title attribute, depending on type and configuration - you can&#039;t rely on the title being read, so you should make sure that the link makes sense even without the title. But if all you&#039;re doing with the title is adding redundancy or repetition, &lt;strong&gt;don&#039;t&lt;/strong&gt;! People using screen readers don&#039;t want to hear &quot;Link: Contact us. Visit our contact page&quot; - they know what &quot;Link: Contact us&quot; means, and having it repeated is irritating, unnecessary, time-wasting and insulting.</description>
		<content:encoded><![CDATA[<p>@chaoley</p>
<blockquote><p>The title attribute is not optional, it’s there for accesibility reasons. Visually impaired users with screen readers for example.</p></blockquote>
<p>The <code>title</code> attribute <strong>is</strong> optional. It should only be used where additional text, over and above the link text and surrounding context, may be needed for users to understand the link destination/purpose.</p>
<p>Adding a <code>title</code> attribute to help accessibility won&#8217;t always help. Screen readers may or may not read the title attribute, depending on type and configuration &#8211; you can&#8217;t rely on the title being read, so you should make sure that the link makes sense even without the title. But if all you&#8217;re doing with the title is adding redundancy or repetition, <strong>don&#8217;t</strong>! People using screen readers don&#8217;t want to hear &#8220;Link: Contact us. Visit our contact page&#8221; &#8211; they know what &#8220;Link: Contact us&#8221; means, and having it repeated is irritating, unnecessary, time-wasting and insulting.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Wynnefield</title>
		<link>http://www.sitepoint.com/blogs/2009/01/13/crimes-against-hypertext/comment-page-1/#comment-865107</link>
		<dc:creator>Wynnefield</dc:creator>
		<pubDate>Mon, 19 Jan 2009 23:41:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3882#comment-865107</guid>
		<description>oh well, just ignore me ... just like these posts have ignored my paragraph and break tags ... :-(</description>
		<content:encoded><![CDATA[<p>oh well, just ignore me &#8230; just like these posts have ignored my paragraph and break tags &#8230; :-(</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Wynnefield</title>
		<link>http://www.sitepoint.com/blogs/2009/01/13/crimes-against-hypertext/comment-page-1/#comment-865106</link>
		<dc:creator>Wynnefield</dc:creator>
		<pubDate>Mon, 19 Jan 2009 23:40:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3882#comment-865106</guid>
		<description>Please ignore my nasty spacing. I accidentally removed the break tags thinking they were adding an additional line in the wrong places. Should look more like this:

&lt;code&gt;
&lt;strong&gt;Job Title of the Position or Role&lt;/strong&gt;
This is a one or two line summary of the job description and/or requirements of the position ... &lt;a href=&quot;http://www.recruitingsite.com/longdescription.html&quot; rel=&quot;nofollow&quot;&gt;More &gt;&gt;&lt;/a&gt;
&lt;strong&gt;Job Title of the Position or Role&lt;/strong&gt;
&lt;a href=&quot;http://www.recruitingsite.com/longdescription.html&quot; rel=&quot;nofollow&quot;&gt;More &gt;&gt;&lt;/a&gt;
&lt;strong&gt;Job Title of the Position or Role&lt;/strong&gt;
&lt;a href=&quot;http://www.recruitingsite.com/longdescription.html&quot; rel=&quot;nofollow&quot;&gt;More &gt;&gt;&lt;/a&gt;
&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>Please ignore my nasty spacing. I accidentally removed the break tags thinking they were adding an additional line in the wrong places. Should look more like this:</p>
<code>
<strong>Job Title of the Position or Role</strong>
This is a one or two line summary of the job description and/or requirements of the position ... <a href="http://www.recruitingsite.com/longdescription.html" rel="nofollow">More &gt;&gt;</a>
<strong>Job Title of the Position or Role</strong>
<a href="http://www.recruitingsite.com/longdescription.html" rel="nofollow">More &gt;&gt;</a>
<strong>Job Title of the Position or Role</strong>
<a href="http://www.recruitingsite.com/longdescription.html" rel="nofollow">More &gt;&gt;</a>
</code>]]></content:encoded>
	</item>
</channel>
</rss>
