<?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: Class Equals Screen Reader Info</title>
	<atom:link href="http://www.last-child.com/class-equals-screen-reader-info/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.last-child.com/class-equals-screen-reader-info/</link>
	<description>CSS Toys for Professional Web Developers</description>
	<lastBuildDate>Mon, 15 Feb 2010 21:51:36 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nate Klaiber</title>
		<link>http://www.last-child.com/class-equals-screen-reader-info/comment-page-1/#comment-27462</link>
		<dc:creator>Nate Klaiber</dc:creator>
		<pubDate>Tue, 24 Jul 2007 14:43:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.last-child.com/class-equals-screen-reader-info/#comment-27462</guid>
		<description>I have done the same thing for many sites. I see no problem with it, as you are progressively enhancing for each user. For the user on the screen, you are hiding the content they don&#039;t need to see - but the screen readers can get the content they need. It is the same as if you hide/show content with JavaScript depending on the browser capabilities. You are providing a better experience for the available technology.

However, as you mentioned, the biggest drawback is that the links will be selected via the keyboard and tabbing through the page. Other than that, I think it works out well.</description>
		<content:encoded><![CDATA[<p>I have done the same thing for many sites. I see no problem with it, as you are progressively enhancing for each user. For the user on the screen, you are hiding the content they don&#8217;t need to see &#8211; but the screen readers can get the content they need. It is the same as if you hide/show content with JavaScript depending on the browser capabilities. You are providing a better experience for the available technology.</p>
<p>However, as you mentioned, the biggest drawback is that the links will be selected via the keyboard and tabbing through the page. Other than that, I think it works out well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max Design - standards based web design, development and training &#187; Some links for light reading (24/7/07)</title>
		<link>http://www.last-child.com/class-equals-screen-reader-info/comment-page-1/#comment-27461</link>
		<dc:creator>Max Design - standards based web design, development and training &#187; Some links for light reading (24/7/07)</dc:creator>
		<pubDate>Tue, 24 Jul 2007 09:23:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.last-child.com/class-equals-screen-reader-info/#comment-27461</guid>
		<description>[...] Class Equals Screen Reader Info [...]</description>
		<content:encoded><![CDATA[<p>[...] Class Equals Screen Reader Info [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 1.174 seconds -->
