<?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: Defining Links in Web Documents</title>
	<atom:link href="http://blog.noizeramp.com/2005/12/15/defining-links-in-web-documents/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.noizeramp.com/2005/12/15/defining-links-in-web-documents/</link>
	<description>Am I a finished product -- or a work in progress?</description>
	<lastBuildDate>Mon, 07 Jun 2010 22:13:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Aleksey Gureev</title>
		<link>http://blog.noizeramp.com/2005/12/15/defining-links-in-web-documents/comment-page-1/#comment-300</link>
		<dc:creator>Aleksey Gureev</dc:creator>
		<pubDate>Fri, 16 Dec 2005 08:26:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.noizeramp.com/2005/12/15/defining-links-in-web-documents/#comment-300</guid>
		<description>Yes, totally valid point. Also I was thinking about text browsers with a list of links below or above the page given as a summary.

There are still tricky situations out there, like when you have a page where you give several links to various RSS feeds. It&#039;s obviously better to name such links as &quot;RSS&quot; (not &quot;click&quot; I mean), but they will be all the same &quot;RSS, RSS, RSS ...&quot;. The &quot;title&quot; attribute can do the trick I hope without adding extra visual weight to the document.</description>
		<content:encoded><![CDATA[<p>Yes, totally valid point. Also I was thinking about text browsers with a list of links below or above the page given as a summary.</p>
<p>There are still tricky situations out there, like when you have a page where you give several links to various RSS feeds. It&#8217;s obviously better to name such links as &#8220;RSS&#8221; (not &#8220;click&#8221; I mean), but they will be all the same &#8220;RSS, RSS, RSS &#8230;&#8221;. The &#8220;title&#8221; attribute can do the trick I hope without adding extra visual weight to the document.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Yank</title>
		<link>http://blog.noizeramp.com/2005/12/15/defining-links-in-web-documents/comment-page-1/#comment-299</link>
		<dc:creator>Kevin Yank</dc:creator>
		<pubDate>Thu, 15 Dec 2005 23:50:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.noizeramp.com/2005/12/15/defining-links-in-web-documents/#comment-299</guid>
		<description>This is also an important issue for Web accessibility. That&#039;s why it&#039;s covered in the W3C&#039;s Web Content Accessibility Guidelines (WCAG 1.0):

http://www.w3.org/TR/WCAG10-HTML-TECHS/#link-text

For screen reader users, the text within hyperlinks is very important, because these users often navigate using a list of links of the page. With links like your first example, the list will sound like this: &quot;Click, click here, click, ...&quot; With links like your second example, the list is more useful: &quot;downloads page, Java API refernce, email me&quot;.</description>
		<content:encoded><![CDATA[<p>This is also an important issue for Web accessibility. That&#8217;s why it&#8217;s covered in the W3C&#8217;s Web Content Accessibility Guidelines (WCAG 1.0):</p>
<p><a href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#link-text" rel="nofollow">http://www.w3.org/TR/WCAG10-HTML-TECHS/#link-text</a></p>
<p>For screen reader users, the text within hyperlinks is very important, because these users often navigate using a list of links of the page. With links like your first example, the list will sound like this: &#8220;Click, click here, click, &#8230;&#8221; With links like your second example, the list is more useful: &#8220;downloads page, Java API refernce, email me&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
