<?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: Google Chrome Browser Released with No Thoughts of Accessibility</title>
	<atom:link href="http://accessibility.net.nz/blog/google-chrome-browser-released-with-no-thoughts-of-accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://accessibility.net.nz/blog/google-chrome-browser-released-with-no-thoughts-of-accessibility/</link>
	<description>Your web accessibility expert</description>
	<pubDate>Fri, 30 Jul 2010 15:20:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Nicolas</title>
		<link>http://accessibility.net.nz/blog/google-chrome-browser-released-with-no-thoughts-of-accessibility/#comment-53</link>
		<dc:creator>Nicolas</dc:creator>
		<pubDate>Thu, 25 Sep 2008 04:27:11 +0000</pubDate>
		<guid isPermaLink="false">http://accessibility.net.nz/?p=77#comment-53</guid>
		<description>Hey there Brenda :)

We've discussed this quite a bit on the Guild of Accessible Web Designers' list.  The consensus is that we don't buy this "it's an early version" reason for being so thoroughly unusable by people with disabilities.  It's easy to say "it's only a beta version" to abdicate responsibilities.  How long has it been since gmail became available? 4, 5 years or so?  And it's still in beta!

The thing is, as long as accessibility is an afterthought, we'll see people unable to use things.  And then we are told that the reason more of an effort isn't made to include accessibility is that people with disabilities don't use the product!  Bit like Pete, my car mechanic back in Chicago.  I told him he should put a ramp to his office.  He asked "why should I put a ramp to my office, you're the only guy in a wheelchair that uses my services".  I asked something like "why do you think that is?".  Pete was an excellent mechanic, honest, quick, affordable.  A gem.  But as long as people couldn't get in, they were unlikely to go.  He put in a ramp, and within a month had 12 more regular customers.  It's a bit like that with software too.

As for turn up and help coding it, I would if I had the knowledge and time. 

Cheers :)</description>
		<content:encoded><![CDATA[<p>Hey there Brenda :)</p>
<p>We&#039;ve discussed this quite a bit on the Guild of Accessible Web Designers&#039; list.  The consensus is that we don&#039;t buy this &#034;it&#039;s an early version&#034; reason for being so thoroughly unusable by people with disabilities.  It&#039;s easy to say &#034;it&#039;s only a beta version&#034; to abdicate responsibilities.  How long has it been since gmail became available? 4, 5 years or so?  And it&#039;s still in beta!</p>
<p>The thing is, as long as accessibility is an afterthought, we&#039;ll see people unable to use things.  And then we are told that the reason more of an effort isn&#039;t made to include accessibility is that people with disabilities don&#039;t use the product!  Bit like Pete, my car mechanic back in Chicago.  I told him he should put a ramp to his office.  He asked &#034;why should I put a ramp to my office, you&#039;re the only guy in a wheelchair that uses my services&#034;.  I asked something like &#034;why do you think that is?&#034;.  Pete was an excellent mechanic, honest, quick, affordable.  A gem.  But as long as people couldn&#039;t get in, they were unlikely to go.  He put in a ramp, and within a month had 12 more regular customers.  It&#039;s a bit like that with software too.</p>
<p>As for turn up and help coding it, I would if I had the knowledge and time. </p>
<p>Cheers :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brenda</title>
		<link>http://accessibility.net.nz/blog/google-chrome-browser-released-with-no-thoughts-of-accessibility/#comment-52</link>
		<dc:creator>Brenda</dc:creator>
		<pubDate>Thu, 25 Sep 2008 03:24:54 +0000</pubDate>
		<guid isPermaLink="false">http://accessibility.net.nz/?p=77#comment-52</guid>
		<description>I hope they fix it up quickly too -- but they are following an opensource development model which means put the project out there, code and all, early.. people gets this confused with commercial products where it's all polished up clean and ready for use. Chrome instead is an ongoing continuously improving project with (hopefully) contributors outside google very soon. Still good to make some noise about accessibility -- I'm making noise about it only being for linux thus far. it's reasonable for them to release the windows only version as soon as it's ready, and the linux version what that is ready, and the accessibility get sorted as soon as poss. Perhaps you should turn up and volunteer to help code it?</description>
		<content:encoded><![CDATA[<p>I hope they fix it up quickly too &#8212; but they are following an opensource development model which means put the project out there, code and all, early.. people gets this confused with commercial products where it&#039;s all polished up clean and ready for use. Chrome instead is an ongoing continuously improving project with (hopefully) contributors outside google very soon. Still good to make some noise about accessibility &#8212; I&#039;m making noise about it only being for linux thus far. it&#039;s reasonable for them to release the windows only version as soon as it&#039;s ready, and the linux version what that is ready, and the accessibility get sorted as soon as poss. Perhaps you should turn up and volunteer to help code it?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
