<?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: Hidden barriers - out of sight</title>
	<atom:link href="http://www.rnib.org.uk/wacblog/css/hidden-barriers-out-of-sight/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rnib.org.uk/wacblog/css/hidden-barriers-out-of-sight/</link>
	<description></description>
	<pubDate>Wed, 20 Aug 2008 13:09:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Bim</title>
		<link>http://www.rnib.org.uk/wacblog/css/hidden-barriers-out-of-sight/#comment-60990</link>
		<dc:creator>Bim</dc:creator>
		<pubDate>Mon, 07 Apr 2008 12:28:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-out-of-sight/#comment-60990</guid>
		<description>You're absolutely right, "display: none"  does prevent most screen reader from announcing hidden content .

You aren't quite right in thinking that  this is only used for image replacement though.  It's also used to display and collapse menus where, if screen readers ignored the "display: none" command, their users would have the dubious treat of having to read every second and third level link on a page, even though they aren't visible.  It's also used for showing and hiding FAQ answers on some pages, and because that technique is used, rather than in-page links, the creen reader would need to read through all unwanted answers until they reach the one they want.</description>
		<content:encoded><![CDATA[<p>You&#8217;re absolutely right, &#8220;display: none&#8221;  does prevent most screen reader from announcing hidden content .</p>
<p>You aren&#8217;t quite right in thinking that  this is only used for image replacement though.  It&#8217;s also used to display and collapse menus where, if screen readers ignored the &#8220;display: none&#8221; command, their users would have the dubious treat of having to read every second and third level link on a page, even though they aren&#8217;t visible.  It&#8217;s also used for showing and hiding FAQ answers on some pages, and because that technique is used, rather than in-page links, the creen reader would need to read through all unwanted answers until they reach the one they want.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyler</title>
		<link>http://www.rnib.org.uk/wacblog/css/hidden-barriers-out-of-sight/#comment-59907</link>
		<dc:creator>Tyler</dc:creator>
		<pubDate>Sun, 30 Mar 2008 21:00:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-out-of-sight/#comment-59907</guid>
		<description>As someone who designs CSS-based web-pages, I make frequent use of "display: none" to replace text with background graphics.  I've recently learned that this is supposedly not a good practice because of issues with screen readers, which may obey the CSS command by not reading the link.

Since then, though, I've been wondering -- WHY do screen reader applications even look at the CSS file?  

It seems to me that CSS files are intended for visual formatting, and carry no content.  So why isn't the default setting on screen readers to ignore the CSS file altogether?

(And, anticipating one possible answer -- that people who are visually impaired but not entirely blind may want stylesheets to load -- then in that case why not have a built-in option to ignore the "display: none" specification in the stylesheet?  It is rarely used for anything BUT image replacement.)</description>
		<content:encoded><![CDATA[<p>As someone who designs CSS-based web-pages, I make frequent use of &#8220;display: none&#8221; to replace text with background graphics.  I&#8217;ve recently learned that this is supposedly not a good practice because of issues with screen readers, which may obey the CSS command by not reading the link.</p>
<p>Since then, though, I&#8217;ve been wondering &#8212; WHY do screen reader applications even look at the CSS file?  </p>
<p>It seems to me that CSS files are intended for visual formatting, and carry no content.  So why isn&#8217;t the default setting on screen readers to ignore the CSS file altogether?</p>
<p>(And, anticipating one possible answer &#8212; that people who are visually impaired but not entirely blind may want stylesheets to load &#8212; then in that case why not have a built-in option to ignore the &#8220;display: none&#8221; specification in the stylesheet?  It is rarely used for anything BUT image replacement.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.rnib.org.uk/wacblog/css/hidden-barriers-out-of-sight/#comment-57932</link>
		<dc:creator>John</dc:creator>
		<pubDate>Tue, 11 Mar 2008 12:30:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-out-of-sight/#comment-57932</guid>
		<description>Further to my last comment about using transparent images, it was pointed out to me, that as this isn't controlled via CSS, it will remain hidden when CSS is disabled. However, with Bim's CSS example, it becomes visible while CSS is disabled.

Also IE treats alt text as tool tips where as other browsers rightly don't.</description>
		<content:encoded><![CDATA[<p>Further to my last comment about using transparent images, it was pointed out to me, that as this isn&#8217;t controlled via CSS, it will remain hidden when CSS is disabled. However, with Bim&#8217;s CSS example, it becomes visible while CSS is disabled.</p>
<p>Also IE treats alt text as tool tips where as other browsers rightly don&#8217;t.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.rnib.org.uk/wacblog/css/hidden-barriers-out-of-sight/#comment-57058</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 03 Mar 2008 22:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-out-of-sight/#comment-57058</guid>
		<description>Just a thought, for hidden text would a transparent image say 1px with the alt text give the desired effect?

I know when people use such transparant images for layout spacing, their alt-text is read out.</description>
		<content:encoded><![CDATA[<p>Just a thought, for hidden text would a transparent image say 1px with the alt text give the desired effect?</p>
<p>I know when people use such transparant images for layout spacing, their alt-text is read out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Tew</title>
		<link>http://www.rnib.org.uk/wacblog/css/hidden-barriers-out-of-sight/#comment-31797</link>
		<dc:creator>Steven Tew</dc:creator>
		<pubDate>Fri, 17 Aug 2007 10:25:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-out-of-sight/#comment-31797</guid>
		<description>Access Matters has tested this. They have published a table showing the results for different methods of hiding information from visual display.

http://www.access-matters.com/screen-reader-test-results/

Window Eyes 4.5 and 5 with IE 6 seem to be the most problematic with all the methods tested. Methods 8, 9 and 11 seem to have the broadest screen reader reach.</description>
		<content:encoded><![CDATA[<p>Access Matters has tested this. They have published a table showing the results for different methods of hiding information from visual display.</p>
<p><a href="http://www.access-matters.com/screen-reader-test-results/" rel="nofollow">http://www.access-matters.com/screen-reader-test-results/</a></p>
<p>Window Eyes 4.5 and 5 with IE 6 seem to be the most problematic with all the methods tested. Methods 8, 9 and 11 seem to have the broadest screen reader reach.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben 'Cerbera' Millard</title>
		<link>http://www.rnib.org.uk/wacblog/css/hidden-barriers-out-of-sight/#comment-31271</link>
		<dc:creator>Ben 'Cerbera' Millard</dc:creator>
		<pubDate>Tue, 14 Aug 2007 10:16:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-out-of-sight/#comment-31271</guid>
		<description>When you say "most screen reader users will benefit" does that mean some won't? If so, could you be more specific about this?</description>
		<content:encoded><![CDATA[<p>When you say &#8220;most screen reader users will benefit&#8221; does that mean some won&#8217;t? If so, could you be more specific about this?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
