<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Curious?</title>
	<link>http://www.webword.com/wp/2006/04/27/curious/</link>
	<description>The usability blog of John S. Rhodes</description>
	<pubDate>Fri, 25 Jul 2008 06:17:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.3</generator>

	<item>
		<title>by: meg</title>
		<link>http://www.webword.com/wp/2006/04/27/curious/#comment-13063</link>
		<pubDate>Fri, 28 Apr 2006 22:41:37 +0000</pubDate>
		<guid>http://www.webword.com/wp/2006/04/27/curious/#comment-13063</guid>
					<description>Accessibility? What? I use large font settings and am an accessibility proponent so really really want to know how to make the alphabet blocks more accessible. 

What settings are you using? I'm low-vision only and can test on myself and deaf/HOH in the day job. Which part makes it not accessible? Are you using a screen reader? 

Please let me know (email). Please and thanks for any help on this one.</description>
		<content:encoded><![CDATA[<p>Accessibility? What? I use large font settings and am an accessibility proponent so really really want to know how to make the alphabet blocks more accessible. </p>
<p>What settings are you using? I&#8217;m low-vision only and can test on myself and deaf/HOH in the day job. Which part makes it not accessible? Are you using a screen reader? </p>
<p>Please let me know (email). Please and thanks for any help on this one.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: John Rhodes</title>
		<link>http://www.webword.com/wp/2006/04/27/curious/#comment-13052</link>
		<pubDate>Fri, 28 Apr 2006 15:26:26 +0000</pubDate>
		<guid>http://www.webword.com/wp/2006/04/27/curious/#comment-13052</guid>
					<description>Wolf, great point. It seems there's always a cost to pushing the envelope. Cutting edge...envelope cuts.

However, I will say that accessibility and CSS often go hand in hand.
http://www.naarvoren.nl/artikel/high_accessibility/
http://www.webaim.org/techniques/css/
http://www.clagnut.com/blog/1553/
http://staff.washington.edu/rells/xhtmlcss/accessibility/xhtml-css-acc.htm</description>
		<content:encoded><![CDATA[<p>Wolf, great point. It seems there&#8217;s always a cost to pushing the envelope. Cutting edge&#8230;envelope cuts.</p>
<p>However, I will say that accessibility and CSS often go hand in hand.<br />
<a href='http://www.naarvoren.nl/artikel/high_accessibility/' rel='nofollow'>http://www.naarvoren.nl/artikel/high_accessibility/</a><br />
<a href='http://www.webaim.org/techniques/css/' rel='nofollow'>http://www.webaim.org/techniques/css/</a><br />
<a href='http://www.clagnut.com/blog/1553/' rel='nofollow'>http://www.clagnut.com/blog/1553/</a><br />
<a href='http://staff.washington.edu/rells/xhtmlcss/accessibility/xhtml-css-acc.htm' rel='nofollow'>http://staff.washington.edu/rells/xhtmlcss/accessibility/xhtml-css-acc.htm</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Wolf Bogacz</title>
		<link>http://www.webword.com/wp/2006/04/27/curious/#comment-13032</link>
		<pubDate>Fri, 28 Apr 2006 13:03:06 +0000</pubDate>
		<guid>http://www.webword.com/wp/2006/04/27/curious/#comment-13032</guid>
					<description>I'll just mention that the alpha blocks show badly to anyone who uses any (or all) Accessibility options in Internet Explorer.
But then, any website employing special formatting or colorization can lose through user employment of those options.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll just mention that the alpha blocks show badly to anyone who uses any (or all) Accessibility options in Internet Explorer.<br />
But then, any website employing special formatting or colorization can lose through user employment of those options.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
