<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Quiz 4.1.3: How do CSS layout variations affect assistive technology - part 2</title>
	<link>http://www.access-matters.com/2005/07/02/quiz-412-how-do-css-layout-variations-affect-assistive-technology-part-2/</link>
	<description>Seeking Best Accessibility Practices</description>
	<pubDate>Thu, 11 Mar 2010 19:05:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Roger Johansson</title>
		<link>http://www.access-matters.com/2005/07/02/quiz-412-how-do-css-layout-variations-affect-assistive-technology-part-2/#comment-510</link>
		<pubDate>Sun, 31 Jul 2005 18:15:11 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/02/quiz-412-how-do-css-layout-variations-affect-assistive-technology-part-2/#comment-510</guid>
					<description>C. Tested with Safari 2 + VoiceOver.</description>
		<content:encoded><![CDATA[<p>C. Tested with Safari 2 + VoiceOver.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: pam</title>
		<link>http://www.access-matters.com/2005/07/02/quiz-412-how-do-css-layout-variations-affect-assistive-technology-part-2/#comment-501</link>
		<pubDate>Mon, 18 Jul 2005 20:52:19 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/02/quiz-412-how-do-css-layout-variations-affect-assistive-technology-part-2/#comment-501</guid>
					<description>Opera 8 also follows the order of the markup in the HTML document.</description>
		<content:encoded><![CDATA[<p>Opera 8 also follows the order of the markup in the HTML document.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: pam</title>
		<link>http://www.access-matters.com/2005/07/02/quiz-412-how-do-css-layout-variations-affect-assistive-technology-part-2/#comment-499</link>
		<pubDate>Mon, 18 Jul 2005 14:30:12 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/02/quiz-412-how-do-css-layout-variations-affect-assistive-technology-part-2/#comment-499</guid>
					<description>I also tested with Foxy Voice, another extension for Firefox, and the result was the same. For some reason though, Foxy Voice pauses in the third item in the column three list. I'm not sure why.</description>
		<content:encoded><![CDATA[<p>I also tested with Foxy Voice, another extension for Firefox, and the result was the same. For some reason though, Foxy Voice pauses in the third item in the column three list. I&#8217;m not sure why.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: pam</title>
		<link>http://www.access-matters.com/2005/07/02/quiz-412-how-do-css-layout-variations-affect-assistive-technology-part-2/#comment-498</link>
		<pubDate>Mon, 18 Jul 2005 14:25:09 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/02/quiz-412-how-do-css-layout-variations-affect-assistive-technology-part-2/#comment-498</guid>
					<description>I tested with Fire Vox, the free screen reader for Firefox. It read them all the same way. It followed the order of the source HTML.</description>
		<content:encoded><![CDATA[<p>I tested with Fire Vox, the free screen reader for Firefox. It read them all the same way. It followed the order of the source HTML.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Anup Shah</title>
		<link>http://www.access-matters.com/2005/07/02/quiz-412-how-do-css-layout-variations-affect-assistive-technology-part-2/#comment-474</link>
		<pubDate>Mon, 04 Jul 2005 09:32:25 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/02/quiz-412-how-do-css-layout-variations-affect-assistive-technology-part-2/#comment-474</guid>
					<description>A. Just looking at the source code of the HTML I know that the major screen readers (e.g. Jaws, Windows Eyes, IBM Home Page Reader) will read them all the same. While I have not tested these ones (in a rush, that's why!), I have tested similar things in the past many times. The source HTML is almost always what counts.

The only thing with CSS that I have come across that might be a major issue is display:none. But we have various techniques like off-left, and off-top to address this. This is not so much for image replacement, but more useful to hide things like headings and important sentences that are useful for such readers, or when CSS is not available.</description>
		<content:encoded><![CDATA[<p>A. Just looking at the source code of the HTML I know that the major screen readers (e.g. Jaws, Windows Eyes, IBM Home Page Reader) will read them all the same. While I have not tested these ones (in a rush, that&#8217;s why!), I have tested similar things in the past many times. The source HTML is almost always what counts.</p>
<p>The only thing with CSS that I have come across that might be a major issue is display:none. But we have various techniques like off-left, and off-top to address this. This is not so much for image replacement, but more useful to hide things like headings and important sentences that are useful for such readers, or when CSS is not available.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
