<?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"
	>
<channel>
	<title>Comments on: Linked Text</title>
	<atom:link href="http://www.meryl.net/2007/04/linked-text/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.meryl.net/2007/04/linked-text/</link>
	<description>Content on writing, tech, business, marketing, web design.</description>
	<pubDate>Tue, 02 Dec 2008 00:17:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Working with Link Styles</title>
		<link>http://www.meryl.net/2007/04/linked-text/#comment-231993</link>
		<dc:creator>Working with Link Styles</dc:creator>
		<pubDate>Fri, 27 Apr 2007 12:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://meryl.net/2007/04/02/linked-text/#comment-231993</guid>
		<description>&lt;p&gt;[...] Linked text is another story. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Linked text is another story. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steve</title>
		<link>http://www.meryl.net/2007/04/linked-text/#comment-190561</link>
		<dc:creator>steve</dc:creator>
		<pubDate>Tue, 03 Apr 2007 20:20:42 +0000</pubDate>
		<guid isPermaLink="false">http://meryl.net/2007/04/02/linked-text/#comment-190561</guid>
		<description>&lt;p&gt;Meryl:&lt;/p&gt;

&lt;p&gt;Nice post as always. Do I know you? are you Meryl the Famous Content Maven???? (if so - don't click here)&lt;/p&gt;

&lt;p&gt;I think it may be good to use both.  Why? Because some readers are adept and some aren't. Some are savvy. Some aren't.&lt;/p&gt;

&lt;p&gt;Some content platforms display hyper-linked text - some muck it up. Especially news distribution sites. For example - Morningstar does- Yahoo does - others don't - like http://lasalle.yellowbrix.com/pages/lasalle/Story.nsp?story_id=104755910&#38;type=sfb&#38;ID=lasalle&#38;scategory=Business+and+Finance&#38;&lt;/p&gt;

&lt;p&gt;Anyway - nice post!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Meryl:</p>
<p>Nice post as always. Do I know you? are you Meryl the Famous Content Maven???? (if so - don&#8217;t click here)</p>
<p>I think it may be good to use both.  Why? Because some readers are adept and some aren&#8217;t. Some are savvy. Some aren&#8217;t.</p>
<p>Some content platforms display hyper-linked text - some muck it up. Especially news distribution sites. For example - Morningstar does- Yahoo does - others don&#8217;t - like <a href="http://lasalle.yellowbrix.com/pages/lasalle/Story.nsp?story_id=104755910&amp;type=sfb&amp;ID=lasalle&amp;scategory=Business+and+Finance&#038;amp" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/lasalle.yellowbrix.com/pages/lasalle/Story.nsp?story_id=104755910_amp_type=sfb_amp_ID=lasalle_amp_scategory=Business+and+Finance_038_amp&amp;referer=');">http://lasalle.yellowbrix.com/pages/lasalle/Story.nsp?story_id=104755910&amp;type=sfb&amp;ID=lasalle&amp;scategory=Business+and+Finance&#038;amp</a>;</p>
<p>Anyway - nice post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Meryl</title>
		<link>http://www.meryl.net/2007/04/linked-text/#comment-189598</link>
		<dc:creator>Meryl</dc:creator>
		<pubDate>Mon, 02 Apr 2007 14:34:18 +0000</pubDate>
		<guid isPermaLink="false">http://meryl.net/2007/04/02/linked-text/#comment-189598</guid>
		<description>&lt;p&gt;Excellent points, Michael. Thank you for taking the time to provide an insightful comment. I don't want to make it difficult for those relying on text-to-speech and that reason alone is enough to make me change my habit.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Excellent points, Michael. Thank you for taking the time to provide an insightful comment. I don&#8217;t want to make it difficult for those relying on text-to-speech and that reason alone is enough to make me change my habit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Sauers</title>
		<link>http://www.meryl.net/2007/04/linked-text/#comment-189595</link>
		<dc:creator>Michael Sauers</dc:creator>
		<pubDate>Mon, 02 Apr 2007 14:30:51 +0000</pubDate>
		<guid isPermaLink="false">http://meryl.net/2007/04/02/linked-text/#comment-189595</guid>
		<description>&lt;p&gt;I strongly discourage the use of "click here" as a link for accessibility reasons. Some text-to-speech browsers read back to the user just a list of the links available on a page. A user hearing "click here" totally out of context will have no idea what will happen when they click on that link. If the link text makes no sense out of context, it's not a good link.&lt;/p&gt;

&lt;p&gt;As for "click here for..." I tend to view that as laziness as there's always a better way from a grammatical standpoint. Also, I don't by the "users need instruction" argument. It's been more than a decade and people know to click. (But what about the people using keyboards, they're not clicking, they're pressing enter.) That's like saying "forward slash" when reading out a URL. It's just not necessary any more.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I strongly discourage the use of &#8220;click here&#8221; as a link for accessibility reasons. Some text-to-speech browsers read back to the user just a list of the links available on a page. A user hearing &#8220;click here&#8221; totally out of context will have no idea what will happen when they click on that link. If the link text makes no sense out of context, it&#8217;s not a good link.</p>
<p>As for &#8220;click here for&#8230;&#8221; I tend to view that as laziness as there&#8217;s always a better way from a grammatical standpoint. Also, I don&#8217;t by the &#8220;users need instruction&#8221; argument. It&#8217;s been more than a decade and people know to click. (But what about the people using keyboards, they&#8217;re not clicking, they&#8217;re pressing enter.) That&#8217;s like saying &#8220;forward slash&#8221; when reading out a URL. It&#8217;s just not necessary any more.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
