<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Accessible Links</title>
	<atom:link href="http://curbcut.net/accessibility/accessible-links/feed/" rel="self" type="application/rss+xml" />
	<link>http://curbcut.net/accessibility/accessible-links/</link>
	<description>open and accessible</description>
	<lastBuildDate>Mon, 14 Jun 2010 11:07:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: David Spinar</title>
		<link>http://curbcut.net/accessibility/accessible-links/comment-page-1/#comment-96</link>
		<dc:creator>David Spinar</dc:creator>
		<pubDate>Thu, 18 Nov 2004 15:29:51 +0000</pubDate>
		<guid isPermaLink="false">http://curbcut.net/2004/11/accessible-links/#comment-96</guid>
		<description>I agree with Sergi. When using pop-ups, informing a user is not sufficient. You should use a proper content of href attribute.

And I would add 2 more rules:

1) Distinguish links from other text content with more than just color, so that users that cannot &quot;see&quot; the color (because of their visual impairment or hardware device) can recognize it. Underlining is of course the best way.

2) Do not use the same link text for various link targets. Use for each target unique and well destriptive link text and do not rely on context. When it is impossible to distinguish it in link text, distinguish it in title attribute.

(sorry for my poor english - I am not a native speaker)</description>
		<content:encoded><![CDATA[<p>I agree with Sergi. When using pop-ups, informing a user is not sufficient. You should use a proper content of href attribute.</p>
<p>And I would add 2 more rules:</p>
<p>1) Distinguish links from other text content with more than just color, so that users that cannot “see” the color (because of their visual impairment or hardware device) can recognize it. Underlining is of course the best way.</p>
<p>2) Do not use the same link text for various link targets. Use for each target unique and well destriptive link text and do not rely on context. When it is impossible to distinguish it in link text, distinguish it in title attribute.</p>
<p>(sorry for my poor english — I am not a native speaker)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sergi</title>
		<link>http://curbcut.net/accessibility/accessible-links/comment-page-1/#comment-95</link>
		<dc:creator>Sergi</dc:creator>
		<pubDate>Thu, 18 Nov 2004 09:32:23 +0000</pubDate>
		<guid isPermaLink="false">http://curbcut.net/2004/11/accessible-links/#comment-95</guid>
		<description>I&#039;d say most important is having a proper href pointing to a url. No javascript: pseudo-protocol, please.

If you ever feel like adding a popup, just use smth like onclick=&quot;window.open(this.href, options...);return false;&quot;

Most of the browsers will understand the onclick and open it, but those that dont, will at least follow the href. :)</description>
		<content:encoded><![CDATA[<p>I’d say most important is having a proper href pointing to a url. No javascript: pseudo-protocol, please.</p>
<p>If you ever feel like adding a popup, just use smth like onclick=“window.open(this.href, options…);return false;”</p>
<p>Most of the browsers will understand the onclick and open it, but those that dont, will at least follow the href. <img src='http://curbcut.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
