<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Accessing the Touch</title>
	<atom:link href="http://www.timobrienphotos.com/2008/12/accessing-the-touch/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.timobrienphotos.com/2008/12/accessing-the-touch/</link>
	<description>A blind photographer's exploration of his vision through photography and accessibility.</description>
	<lastBuildDate>Mon, 09 Jan 2012 21:07:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tim</title>
		<link>http://www.timobrienphotos.com/2008/12/accessing-the-touch/comment-page-1/#comment-122</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Sun, 14 Dec 2008 02:34:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.timobrienphotos.com/?p=1134#comment-122</guid>
		<description>I may not know what maemo is, but I know the feeling. This is an upcoming theme on my blog. Why are there so many small things that folks could do to make everyone&#039;s lives easier (especially the disabled), but do not bother? Why the QWERTY keyboard? Why are subtitles so poorly implemented? Why are not more visual digital interfaces light-on-dard instead of dark-on-light? The lists goes on. Some of it is inertia, some active resistance. All of it is a waste.</description>
		<content:encoded><![CDATA[<p>I may not know what maemo is, but I know the feeling. This is an upcoming theme on my blog. Why are there so many small things that folks could do to make everyone&#8217;s lives easier (especially the disabled), but do not bother? Why the QWERTY keyboard? Why are subtitles so poorly implemented? Why are not more visual digital interfaces light-on-dard instead of dark-on-light? The lists goes on. Some of it is inertia, some active resistance. All of it is a waste.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lodrorigdzin</title>
		<link>http://www.timobrienphotos.com/2008/12/accessing-the-touch/comment-page-1/#comment-118</link>
		<dc:creator>lodrorigdzin</dc:creator>
		<pubDate>Sat, 13 Dec 2008 14:21:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.timobrienphotos.com/?p=1134#comment-118</guid>
		<description>The strange thing is: the iPod Nano &lt;em&gt;is&lt;/em&gt; accessible, and it&#039;s done beautifully. I can fully see a sleeve + a screenreader iPod app work, perhaps numerous iPod apps, for different sets of functionalities. I can&#039;t understand why there is obviously (?) so much resistance against making the iPod accessible to the blind. If voiceover were to be ported to the iPod, that would be wonderful, but I simply don&#039;t see it happen. What would &quot;we&quot; have to do to draw attention to this? (btw I have the same difficulties regarding the maemo community&#039;s resistance against porting Orca to maemo)</description>
		<content:encoded><![CDATA[<p>The strange thing is: the iPod Nano <em>is</em> accessible, and it&#8217;s done beautifully. I can fully see a sleeve + a screenreader iPod app work, perhaps numerous iPod apps, for different sets of functionalities. I can&#8217;t understand why there is obviously (?) so much resistance against making the iPod accessible to the blind. If voiceover were to be ported to the iPod, that would be wonderful, but I simply don&#8217;t see it happen. What would &#8220;we&#8221; have to do to draw attention to this? (btw I have the same difficulties regarding the maemo community&#8217;s resistance against porting Orca to maemo)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

