<?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: What&#8217;s the key to Accessibility?</title>
	<atom:link href="http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/</link>
	<description>Tips and Commentary on Web Accessibility, Usability, and Search Marketing best practices.</description>
	<pubDate>Fri, 08 Aug 2008 01:17:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Hip Hop Klamotten</title>
		<link>http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-23790</link>
		<dc:creator>Hip Hop Klamotten</dc:creator>
		<pubDate>Thu, 17 Jan 2008 09:19:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-23790</guid>
		<description>I once responded to someone on the WSG list who wanted to know if they had done well with their site in regards to accessibility. They hadn’t in my opinion so I told them as much. They provided all sorts of available user options was their argument. The trouble is that the default state was pretty unfriendly, and all the provided options where hard to get to (links at the end of the page).

In this case the text was tiny and the contrast extremely low. A person with a vision handicap would have had a heck of a time even finding the optional styles. I’d venture to guess they wouldn’t have even hunted for them and would have just left the site.</description>
		<content:encoded><![CDATA[<p>I once responded to someone on the WSG list who wanted to know if they had done well with their site in regards to accessibility. They hadn’t in my opinion so I told them as much. They provided all sorts of available user options was their argument. The trouble is that the default state was pretty unfriendly, and all the provided options where hard to get to (links at the end of the page).</p>
<p>In this case the text was tiny and the contrast extremely low. A person with a vision handicap would have had a heck of a time even finding the optional styles. I’d venture to guess they wouldn’t have even hunted for them and would have just left the&nbsp;site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: No name provided.</title>
		<link>http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-21020</link>
		<dc:creator>No name provided.</dc:creator>
		<pubDate>Thu, 13 Sep 2007 20:16:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-21020</guid>
		<description>This article is what I was looking for...thanks!

&lt;ins&gt;Comment edited to replace name keywords.&lt;/ins&gt;</description>
		<content:encoded><![CDATA[<p>This article is what I was looking for&#8230;thanks!</p>
<p><ins>Comment edited to replace name keywords.</ins></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Accessibility and Client Expectations: Selling Accessibility &#124; streaminterviews.com</title>
		<link>http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-17682</link>
		<dc:creator>Accessibility and Client Expectations: Selling Accessibility &#124; streaminterviews.com</dc:creator>
		<pubDate>Sat, 21 Jul 2007 03:44:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-17682</guid>
		<description>[...] by taking their existing design and throwing in accesskeys, tabindex, and/or a Javascript-based text resizing widget. This is less an issue of taking advantage of the consumer as it is one of developer [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] by taking their existing design and throwing in accesskeys, tabindex, and/or a Javascript-based text resizing widget. This is less an issue of taking advantage of the consumer as it is one of developer&nbsp;[&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Accessibility and Client Expectations: Selling Accessibility &#124; Joe Dolson Accessible Web Design</title>
		<link>http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-17673</link>
		<dc:creator>Accessibility and Client Expectations: Selling Accessibility &#124; Joe Dolson Accessible Web Design</dc:creator>
		<pubDate>Fri, 20 Jul 2007 23:04:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-17673</guid>
		<description>[...] by taking their existing design and throwing in accesskeys, tabindex, and/or a Javascript-based text resizing widget. This is less an issue of taking advantage of the consumer as it is one of developer [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] by taking their existing design and throwing in accesskeys, tabindex, and/or a Javascript-based text resizing widget. This is less an issue of taking advantage of the consumer as it is one of developer&nbsp;[&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cre8tive Flow &#187; Blog Archive &#187; I&#8217;m a Web Browsing Expert &#8212; aren&#8217;t you?</title>
		<link>http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-13284</link>
		<dc:creator>Cre8tive Flow &#187; Blog Archive &#187; I&#8217;m a Web Browsing Expert &#8212; aren&#8217;t you?</dc:creator>
		<pubDate>Mon, 19 Mar 2007 21:27:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-13284</guid>
		<description>[...] What&#8217;s the Key to Accessibility?, I wrote about providing options. In it, I emphasized striking a balance and researching your [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] What&#8217;s the Key to Accessibility?, I wrote about providing options. In it, I emphasized striking a balance and researching your&nbsp;[&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson Accessible Web Design &#124; The Accessibility Silver Bullet</title>
		<link>http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-6096</link>
		<dc:creator>Joe Dolson Accessible Web Design &#124; The Accessibility Silver Bullet</dc:creator>
		<pubDate>Mon, 22 Jan 2007 16:26:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-6096</guid>
		<description>[...] Most importantly, accessibility is not a cleanly definable field. You can&#8217;t easily say that a site is &#8220;more&#8221; accessible than another, at a certain point. One site may have chosen the path of offering site options to allow the user to customize their experience. Another may have elected for spare use of images and a simple structure, but allows the user to use knowledge of their own tools to enhance their experience. Is it necessarily a better or more accessible experience to visit the first site? It depends on implementation, it depends on how complex the options are to implement - and ultimately it&#8217;s a subjective question. The whole question lies in the hands of the user. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Most importantly, accessibility is not a cleanly definable field. You can&#8217;t easily say that a site is &#8220;more&#8221; accessible than another, at a certain point. One site may have chosen the path of offering site options to allow the user to customize their experience. Another may have elected for spare use of images and a simple structure, but allows the user to use knowledge of their own tools to enhance their experience. Is it necessarily a better or more accessible experience to visit the first site? It depends on implementation, it depends on how complex the options are to implement - and ultimately it&#8217;s a subjective question. The whole question lies in the hands of the user.&nbsp;[&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-5586</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Fri, 12 Jan 2007 00:24:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-5586</guid>
		<description>Saw your post, in fact, Tom...already commented on it! :)  Thanks!</description>
		<content:encoded><![CDATA[<p>Saw your post, in fact, Tom&#8230;already commented on it! :)&nbsp;Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-5585</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Thu, 11 Jan 2007 23:39:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-5585</guid>
		<description>Hi Joe,

great post. This is a bit of a manual trackback, possibly a trekback since the computer didn't do it automagically for me :)

After reading I wrote &lt;a href="http://www.kid666.com/blog/2007/01/11/inaccessible-web-site-it-may-not-be-entirely-your-fault/"&gt;a post this exploring this a bit further&lt;/a&gt; on my blog.

Cheers,

Tom</description>
		<content:encoded><![CDATA[<p>Hi Joe,</p>
<p>great post. This is a bit of a manual trackback, possibly a trekback since the computer didn&#8217;t do it automagically for me <img src='http://www.joedolson.com/articles/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>After reading I wrote <a href="http://www.kid666.com/blog/2007/01/11/inaccessible-web-site-it-may-not-be-entirely-your-fault/">a post this exploring this a bit further</a> on my blog.</p>
<p>Cheers,&nbsp;Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kid666 Blog &#187; Blog Archive &#187; Inaccessible web site? It may not be entirely your fault</title>
		<link>http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-5582</link>
		<dc:creator>Kid666 Blog &#187; Blog Archive &#187; Inaccessible web site? It may not be entirely your fault</dc:creator>
		<pubDate>Thu, 11 Jan 2007 20:22:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-5582</guid>
		<description>[...] I was reading through some posts of the excellent Joe Dolson. This one particularly struck me, &#8220;What&#8217;s the key to Accessibility?&#8220;. In it Joe says: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I was reading through some posts of the excellent Joe Dolson. This one particularly struck me, &#8220;What&rsquo;s the key to Accessibility?&#8220;. In it Joe says:&nbsp;[&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-2868</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Tue, 28 Nov 2006 21:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/11/whats-the-key-to-accessibility/#comment-2868</guid>
		<description>Thanks for pointing that out, Jared - it's a slightly different perspective. If you try and expand the options set to provide whatever the visitor &lt;em&gt;might want&lt;/em&gt;, you're definitely going to far for effective accessibility.  Providing options should be limited to what a visitor &lt;em&gt;might need&lt;/em&gt; if you choose to provide them.</description>
		<content:encoded><![CDATA[<p>Thanks for pointing that out, Jared - it&#8217;s a slightly different perspective. If you try and expand the options set to provide whatever the visitor <em>might want</em>, you&#8217;re definitely going to far for effective accessibility.  Providing options should be limited to what a visitor <em>might need</em> if you choose to provide&nbsp;them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
