 




<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments for Blind Access Journal</title>
	<atom:link href="http://blindaccessjournal.com/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://blindaccessjournal.com</link>
	<description>This blog and podcast is all about the blind and our quest for the greatest possible access to all the information available in the world around us. Karen and I chronicle our experiences dealing with a variety of issues as a blind couple, show how we have dealt with various blindness situations and seek comments on ways to constructively address the concrete concerns of accessibility and transportation we face on a daily basis.</description>
	<lastBuildDate>Wed, 01 Sep 2010 14:45:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on Kindle Accessibility Review: How Far Has Amazon Opened the Door to the Blind? by Kindle Accessibility Review: How Far Has Amazon Opened the Door to the Blind? &#171; The BAT Channel</title>
		<link>http://blindaccessjournal.com/?p=949&#038;cpage=1#comment-2408</link>
		<dc:creator>Kindle Accessibility Review: How Far Has Amazon Opened the Door to the Blind? &#171; The BAT Channel</dc:creator>
		<pubDate>Wed, 01 Sep 2010 14:45:29 +0000</pubDate>
		<guid isPermaLink="false">http://blindaccessjournal.com/?p=949#comment-2408</guid>
		<description>[...] Kindle Accessibility Review: How Far Has Amazon Opened the Door to the Blind? Darrell Shandrow Wed, 01 Sep 2010 05:52:51 GMT [...]</description>
		<content:encoded><![CDATA[<p>[...] Kindle Accessibility Review: How Far Has Amazon Opened the Door to the Blind? Darrell Shandrow Wed, 01 Sep 2010 05:52:51 GMT [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Kindle Accessibility Review: How Far Has Amazon Opened the Door to the Blind? by Kindle Accessibility Review: How Far Has Amazon Opened the Door to &#8230; &#124; Discount Kindle Books</title>
		<link>http://blindaccessjournal.com/?p=949&#038;cpage=1#comment-2402</link>
		<dc:creator>Kindle Accessibility Review: How Far Has Amazon Opened the Door to &#8230; &#124; Discount Kindle Books</dc:creator>
		<pubDate>Wed, 01 Sep 2010 11:21:22 +0000</pubDate>
		<guid isPermaLink="false">http://blindaccessjournal.com/?p=949#comment-2402</guid>
		<description>[...] Original post by Darrell Shandrow [...]</description>
		<content:encoded><![CDATA[<p>[...] Original post by Darrell Shandrow [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Mobile TV Provider Plans Release of Accessible iPhone App by Dan</title>
		<link>http://blindaccessjournal.com/?p=935&#038;cpage=1#comment-2378</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Mon, 30 Aug 2010 18:38:12 +0000</pubDate>
		<guid isPermaLink="false">http://blindaccessjournal.com/?p=935#comment-2378</guid>
		<description>Keep in mind that moble speak uses the .net frame owrk to gane accessiblility to apps.  so if they can incorpiate the .net frame work it would bee accessible on the windows moble plate from.</description>
		<content:encoded><![CDATA[<p>Keep in mind that moble speak uses the .net frame owrk to gane accessiblility to apps.  so if they can incorpiate the .net frame work it would bee accessible on the windows moble plate from.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessible Instant Messaging iPhone App Hits the iTunes Store by Jeff</title>
		<link>http://blindaccessjournal.com/?p=945&#038;cpage=1#comment-2163</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Wed, 18 Aug 2010 08:26:36 +0000</pubDate>
		<guid isPermaLink="false">http://blindaccessjournal.com/?p=945#comment-2163</guid>
		<description>Great to hear of an accessible IM app for the iphone for those who want it. I love that their are so many accessible apps for the IOS products out their already.</description>
		<content:encoded><![CDATA[<p>Great to hear of an accessible IM app for the iphone for those who want it. I love that their are so many accessible apps for the IOS products out their already.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apple Needs to Refund VoiceOver Users for Inaccessible Apps by Derrick Moreland</title>
		<link>http://blindaccessjournal.com/?p=947&#038;cpage=1#comment-2138</link>
		<dc:creator>Derrick Moreland</dc:creator>
		<pubDate>Tue, 17 Aug 2010 02:29:38 +0000</pubDate>
		<guid isPermaLink="false">http://blindaccessjournal.com/?p=947#comment-2138</guid>
		<description>I don&#039;t believe that apple should refund anything. If  I buy an app I&#039;m taking my chances on that and that is something I&#039;m alright with. I do have a price point that I&#039;d be willing to eat though.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t believe that apple should refund anything. If  I buy an app I&#8217;m taking my chances on that and that is something I&#8217;m alright with. I do have a price point that I&#8217;d be willing to eat though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apple Needs to Refund VoiceOver Users for Inaccessible Apps by Kelly Pierce</title>
		<link>http://blindaccessjournal.com/?p=947&#038;cpage=1#comment-2124</link>
		<dc:creator>Kelly Pierce</dc:creator>
		<pubDate>Mon, 16 Aug 2010 13:34:49 +0000</pubDate>
		<guid isPermaLink="false">http://blindaccessjournal.com/?p=947#comment-2124</guid>
		<description>There’s a reason why shareware took off in the PC world in the 1980s and 1990s.  People may find that software may not work for them and a trial use period offers the ability to learn if something works for a particular end user.  I wonder if contacting ap developers about VoiceOver compatibility yields much useful information.</description>
		<content:encoded><![CDATA[<p>There’s a reason why shareware took off in the PC world in the 1980s and 1990s.  People may find that software may not work for them and a trial use period offers the ability to learn if something works for a particular end user.  I wonder if contacting ap developers about VoiceOver compatibility yields much useful information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apple Needs to Refund VoiceOver Users for Inaccessible Apps by Kevin Chao</title>
		<link>http://blindaccessjournal.com/?p=947&#038;cpage=1#comment-2113</link>
		<dc:creator>Kevin Chao</dc:creator>
		<pubDate>Sun, 15 Aug 2010 20:03:51 +0000</pubDate>
		<guid isPermaLink="false">http://blindaccessjournal.com/?p=947#comment-2113</guid>
		<description>I don&#039;t believe that Apple should be forced to refund apps that are inaccessible. It&#039;s not Apple&#039;s fault that they are inaccessible, they provide the Accessibility API&#039;s, guidelines and it&#039;s up to the developers to do the right thing. Apple does state in terms of service that all sales are final. 
What I do think should be done is a trial period for apps. They have made the first step in that direction by having a free app section in App Store. However, these are only lite versions of app, which don&#039;t apply to all apps and don&#039;t have all the features of the full paid apps. If Android was able to initially setup a 24 hour period, where one can try out an app, later extending it to 48 hours, Apple can certainly do the same. THis would benefit everyone, would steer people away from jailbreaking and using pirated apps to find out if one likes the app or not. 
This method will be a win win for sighted, blind and other users of Apps in the iOS App Store. 
Since Apple already has an approval process for Apps a check for accessibility for those apps that could be accessible, a rating of some sort would be great.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t believe that Apple should be forced to refund apps that are inaccessible. It&#8217;s not Apple&#8217;s fault that they are inaccessible, they provide the Accessibility API&#8217;s, guidelines and it&#8217;s up to the developers to do the right thing. Apple does state in terms of service that all sales are final.<br />
What I do think should be done is a trial period for apps. They have made the first step in that direction by having a free app section in App Store. However, these are only lite versions of app, which don&#8217;t apply to all apps and don&#8217;t have all the features of the full paid apps. If Android was able to initially setup a 24 hour period, where one can try out an app, later extending it to 48 hours, Apple can certainly do the same. THis would benefit everyone, would steer people away from jailbreaking and using pirated apps to find out if one likes the app or not.<br />
This method will be a win win for sighted, blind and other users of Apps in the iOS App Store.<br />
Since Apple already has an approval process for Apps a check for accessibility for those apps that could be accessible, a rating of some sort would be great.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apple Needs to Refund VoiceOver Users for Inaccessible Apps by Justin Mann</title>
		<link>http://blindaccessjournal.com/?p=947&#038;cpage=1#comment-2112</link>
		<dc:creator>Justin Mann</dc:creator>
		<pubDate>Sun, 15 Aug 2010 17:04:12 +0000</pubDate>
		<guid isPermaLink="false">http://blindaccessjournal.com/?p=947#comment-2112</guid>
		<description>The power of the purse can be an encredible thing.  Therefore, I think apple *should* give refunds if an app is not accessible.  Anybody who is developing an app that is in the app store has to comply with apple&#039;s various standards.  Maybe having the prospect of loosing money over this would make accessibility part of apple&#039;s quality control</description>
		<content:encoded><![CDATA[<p>The power of the purse can be an encredible thing.  Therefore, I think apple *should* give refunds if an app is not accessible.  Anybody who is developing an app that is in the app store has to comply with apple&#8217;s various standards.  Maybe having the prospect of loosing money over this would make accessibility part of apple&#8217;s quality control</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apple Needs to Refund VoiceOver Users for Inaccessible Apps by Brandon armstrong</title>
		<link>http://blindaccessjournal.com/?p=947&#038;cpage=1#comment-2110</link>
		<dc:creator>Brandon armstrong</dc:creator>
		<pubDate>Sun, 15 Aug 2010 16:36:21 +0000</pubDate>
		<guid isPermaLink="false">http://blindaccessjournal.com/?p=947#comment-2110</guid>
		<description>I spoke with apple about this on going issue a couple of days ago about another app called wae gps and i also emailed the company about it.
I informed apple that they should implement a policy that asks not demands that developers make their apps voiceover accessible with their apps.
I believe this would have an advantage of getting more customers.</description>
		<content:encoded><![CDATA[<p>I spoke with apple about this on going issue a couple of days ago about another app called wae gps and i also emailed the company about it.<br />
I informed apple that they should implement a policy that asks not demands that developers make their apps voiceover accessible with their apps.<br />
I believe this would have an advantage of getting more customers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apple Needs to Refund VoiceOver Users for Inaccessible Apps by Gabe Vega</title>
		<link>http://blindaccessjournal.com/?p=947&#038;cpage=1#comment-2109</link>
		<dc:creator>Gabe Vega</dc:creator>
		<pubDate>Sun, 15 Aug 2010 15:51:23 +0000</pubDate>
		<guid isPermaLink="false">http://blindaccessjournal.com/?p=947#comment-2109</guid>
		<description>The free version of palringo works fine, all protocoles are accesibly usable for the instant messaging functions.</description>
		<content:encoded><![CDATA[<p>The free version of palringo works fine, all protocoles are accesibly usable for the instant messaging functions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
