<?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: The biggest barrier to accessibility and inclusive design is us</title>
	<atom:link href="http://scriptingenabled.org/2008/07/the-biggest-barrier-to-accessibility-and-inclusive-design-is-us/feed/" rel="self" type="application/rss+xml" />
	<link>http://scriptingenabled.org/2008/07/the-biggest-barrier-to-accessibility-and-inclusive-design-is-us/</link>
	<description>Hacking the web to be more accessible</description>
	<pubDate>Thu, 20 Nov 2008 20:45:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Bookmarks about Layouts</title>
		<link>http://scriptingenabled.org/2008/07/the-biggest-barrier-to-accessibility-and-inclusive-design-is-us/#comment-330</link>
		<dc:creator>Bookmarks about Layouts</dc:creator>
		<pubDate>Sat, 18 Oct 2008 23:45:33 +0000</pubDate>
		<guid isPermaLink="false">http://scriptingenabled.org/?p=19#comment-330</guid>
		<description>[...] - bookmarked by 5 members originally found by ProfCDwyer on 2008-10-01  The biggest barrier to accessibility and inclusive design is us  [...]</description>
		<content:encoded><![CDATA[<p>[...] - bookmarked by 5 members originally found by ProfCDwyer on 2008-10-01  The biggest barrier to accessibility and inclusive design is us  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iheni :: making the web worldwide &#187; Blog Archive &#187; Scripting Enabled: accessibility gets &#8220;a swift kick up the backside&#8221;</title>
		<link>http://scriptingenabled.org/2008/07/the-biggest-barrier-to-accessibility-and-inclusive-design-is-us/#comment-220</link>
		<dc:creator>iheni :: making the web worldwide &#187; Blog Archive &#187; Scripting Enabled: accessibility gets &#8220;a swift kick up the backside&#8221;</dc:creator>
		<pubDate>Mon, 22 Sep 2008 15:55:28 +0000</pubDate>
		<guid isPermaLink="false">http://scriptingenabled.org/?p=19#comment-220</guid>
		<description>[...] certainly achieved in the two days what he set out to do: to give the accessibility community a swift kick up the backside. The overall message is loud and clear: keep talking, keep hacking and most of all keep sharing. [...]</description>
		<content:encoded><![CDATA[<p>[...] certainly achieved in the two days what he set out to do: to give the accessibility community a swift kick up the backside. The overall message is loud and clear: keep talking, keep hacking and most of all keep sharing. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diogo Vincenzi</title>
		<link>http://scriptingenabled.org/2008/07/the-biggest-barrier-to-accessibility-and-inclusive-design-is-us/#comment-65</link>
		<dc:creator>Diogo Vincenzi</dc:creator>
		<pubDate>Thu, 24 Jul 2008 19:50:23 +0000</pubDate>
		<guid isPermaLink="false">http://scriptingenabled.org/?p=19#comment-65</guid>
		<description>@Chris: I agree, and perhaps I didn't express myself correctly. Tomasz said that worrying about compatibility with IE6 should not be a problem anymore, and we should just use the famous IE7.js to make your site work correctly in IE6. While that stands true for some cases, in others, and specially in Brazil where support for certain technologies is a bit complicated in some places, making a website work in IE6 using only HTML and CSS is very important.

I always build for Opera/Firefox/Safari first, and then see about getting the website to work in IE6 though. If there are small visual differences, it's not a problem as long as it works. I just did a rant today on my website on how IE6 is so outdated by now and that users should upgrade as soon as possible exactly for the same reasons you are describing here, so I'm with you 100% on this.</description>
		<content:encoded><![CDATA[<p>@Chris: I agree, and perhaps I didn&#8217;t express myself correctly. Tomasz said that worrying about compatibility with <span class="caps">IE6 </span>should not be a problem anymore, and we should just use the famous <span class="caps">IE7.</span>js to make your site work correctly in <span class="caps">IE6.</span> While that stands true for some cases, in others, and specially in Brazil where support for certain technologies is a bit complicated in some places, making a website work in <span class="caps">IE6 </span>using only <span class="caps">HTML </span>and <span class="caps">CSS </span>is very important.</p>
<p>I always build for Opera/Firefox/Safari first, and then see about getting the website to work in <span class="caps">IE6 </span>though. If there are small visual differences, it&#8217;s not a problem as long as it works. I just did a rant today on my website on how <span class="caps">IE6 </span>is so outdated by now and that users should upgrade as soon as possible exactly for the same reasons you are describing here, so I&#8217;m with you 100% on this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://scriptingenabled.org/2008/07/the-biggest-barrier-to-accessibility-and-inclusive-design-is-us/#comment-63</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 24 Jul 2008 13:41:58 +0000</pubDate>
		<guid isPermaLink="false">http://scriptingenabled.org/?p=19#comment-63</guid>
		<description>@Diogo that is a pretty irrelevant statement in this context though. Nobody claimed not to support IE6, I just said that it is time we acknowledge other platforms, too, especially when they are free. Jaws + Windows + IE is an expensive setup, OSX comes with Voiceover. 

Coming from your web development world: yes, supporting IE6 is still very important, especially in emerging markets and South East Asia, but building *for* IE6 only or optimizing for it will keep us from evolving as a market, as a profession and hinder great user experience.</description>
		<content:encoded><![CDATA[<p>@Diogo that is a pretty irrelevant statement in this context though. Nobody claimed not to support <span class="caps">IE6,</span> I just said that it is time we acknowledge other platforms, too, especially when they are free. Jaws + Windows + IE is an expensive setup, <span class="caps">OSX </span>comes with Voiceover. </p>
<p>Coming from your web development world: yes, supporting <span class="caps">IE6 </span>is still very important, especially in emerging markets and South East Asia, but building <strong>for</strong> <span class="caps">IE6 </span>only or optimizing for it will keep us from evolving as a market, as a profession and hinder great user experience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diogo Vincenzi</title>
		<link>http://scriptingenabled.org/2008/07/the-biggest-barrier-to-accessibility-and-inclusive-design-is-us/#comment-62</link>
		<dc:creator>Diogo Vincenzi</dc:creator>
		<pubDate>Thu, 24 Jul 2008 13:14:30 +0000</pubDate>
		<guid isPermaLink="false">http://scriptingenabled.org/?p=19#comment-62</guid>
		<description>I loved the part about IE6...here in brazil I'd say 80% of internet users still use it, so not having compatibility with it is shooting yourself in both feet.</description>
		<content:encoded><![CDATA[<p>I loved the part about <span class="caps">IE6&#8230;</span>here in brazil I&#8217;d say 80% of internet users still use it, so not having compatibility with it is shooting yourself in both feet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Links for 2008-07-24 - tonyscott.org.uk</title>
		<link>http://scriptingenabled.org/2008/07/the-biggest-barrier-to-accessibility-and-inclusive-design-is-us/#comment-61</link>
		<dc:creator>Links for 2008-07-24 - tonyscott.org.uk</dc:creator>
		<pubDate>Thu, 24 Jul 2008 00:29:02 +0000</pubDate>
		<guid isPermaLink="false">http://scriptingenabled.org/?p=19#comment-61</guid>
		<description>[...] The biggest barrier to accessibility and inclusive design is us [Chris Heilmann] [...]</description>
		<content:encoded><![CDATA[<p>[...] The biggest barrier to accessibility and inclusive design is us [Chris Heilmann] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Teare</title>
		<link>http://scriptingenabled.org/2008/07/the-biggest-barrier-to-accessibility-and-inclusive-design-is-us/#comment-59</link>
		<dc:creator>Phil Teare</dc:creator>
		<pubDate>Wed, 23 Jul 2008 18:38:43 +0000</pubDate>
		<guid isPermaLink="false">http://scriptingenabled.org/?p=19#comment-59</guid>
		<description>"Screw blind people!"? Crikey :) Yes I would put that in the controversial pile. But you're right, a gem of a post.</description>
		<content:encoded><![CDATA[<p>&#8220;Screw blind people!&#8221;? Crikey <img src='http://scriptingenabled.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> Yes I would put that in the controversial pile. But you&#8217;re right, a gem of a post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Lee</title>
		<link>http://scriptingenabled.org/2008/07/the-biggest-barrier-to-accessibility-and-inclusive-design-is-us/#comment-54</link>
		<dc:creator>Steve Lee</dc:creator>
		<pubDate>Wed, 23 Jul 2008 08:28:46 +0000</pubDate>
		<guid isPermaLink="false">http://scriptingenabled.org/?p=19#comment-54</guid>
		<description>Excellent.</description>
		<content:encoded><![CDATA[<p>Excellent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wait till I come! &#187; Blog Archive &#187; Yet another rant on accessibility and usability</title>
		<link>http://scriptingenabled.org/2008/07/the-biggest-barrier-to-accessibility-and-inclusive-design-is-us/#comment-53</link>
		<dc:creator>Wait till I come! &#187; Blog Archive &#187; Yet another rant on accessibility and usability</dc:creator>
		<pubDate>Wed, 23 Jul 2008 03:23:11 +0000</pubDate>
		<guid isPermaLink="false">http://scriptingenabled.org/?p=19#comment-53</guid>
		<description>[...] a long blog post over at Scripting Enabled entitled The biggest barrier to accessibility and inclusive design is us I am myself venting some of the frustrations I encountered in my years of standing in the [...]</description>
		<content:encoded><![CDATA[<p>[...] a long blog post over at Scripting Enabled entitled The biggest barrier to accessibility and inclusive design is us I am myself venting some of the frustrations I encountered in my years of standing in the [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
