<?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:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"

	>
<channel>
	<title>
	Comments on: SeroTalk Podcast 134: The Cheese Stands Alone	</title>
	<atom:link href="/2012/12/11/serotalk-podcast-134-the-cheese-stands-alone/feed/" rel="self" type="application/rss+xml" />
	<link>/2012/12/11/serotalk-podcast-134-the-cheese-stands-alone/</link>
	<description>A podcast and interactive blog on the accessible digital lifestyle, produced by Serotek, the Accessibility Anywhere people</description>
	<lastBuildDate>Thu, 13 Dec 2012 15:19:14 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.5.3</generator>
	<item>
		<title>
		By: Russ Kiehne		</title>
		<link>/2012/12/11/serotalk-podcast-134-the-cheese-stands-alone/comment-page-1/#comment-4838</link>

		<dc:creator><![CDATA[Russ Kiehne]]></dc:creator>
		<pubDate>Thu, 13 Dec 2012 15:19:14 +0000</pubDate>
		<guid isPermaLink="false">/?p=2068#comment-4838</guid>

					<description><![CDATA[&lt;p&gt;Doing some research, I found the following from NFB.  I can&#039;t see buying a Kindle
 Fire at this point in time.  I&#039;ll continue to use my Kindle Keyboard to reae Kindle books.&lt;/p&gt;

&lt;p&gt;Amazon, Why Do You Keep Burning Blind Readers?
Submitted by cvangerven on Fri, 12/07/2012 - 13:00
Blog Date:
Friday, December 7, 2012
By Amy Mason&lt;/p&gt;

&lt;p&gt;According to ZDNet and Engadget the Kindle Fire will be getting Explore by
Touch and Voice Guide to provide
accessibility features to blind and visually impaired customers.
These features were first introduced in Google&#039;s Android, Ice Cream Sandwich
operating system. (This is the basis of the OS for the Kindle Fire and Fire HD
which has been heavily skinned by Amazon for the device.)  Google has since
released Jelly Bean which has improved markedly on accessibility.  If this
were Amazon&#039;s only weakness,
an out-of-date OS, I would be disappointed, but I would understand. This is
not, however, Amazon&#039;s only problem.
Their weakness instead, appears to be a disregard for the wishes of its blind
consumers.
Blind people want Kindle books. We want them badly enough that I know several
blind people who have chosen to buy the Kindle Keyboard, despite being unable
to do anything more than start and stop text-to-speech on their books.  The
PC edition (with accessibility plug-in) is slightly better.  If a user is
willing to sit at a PC, they can read by navigational elements as small as a
sentence at a time, and as large as a page (seriously, you have to sit at the
computer and turn every page.  What a thrilling way to read a book!)
I hear a few of you saying, &quot;Ok, Amy, so you are upset about the past, but now
Amazon is offering this additional accessibility in the Fire&quot;.  I am sorry to
disappoint
you, but for all intents and purposes it did not improve on their existing efforts.
We purchased a Kindle Fire HD, and received it last Friday.  We read on
Amazon&#039;s website that there were accessibility features, so we felt that we
had to do our due diligence and test their work. First of all, when you get
the device,
you have to have a sighted person turn on the accessibility features because
there is no way for a blind person to turn them on independently.
Secondly, access is limited to the device settings, the collection of books in
a user&#039;s library, the primary navigation buttons (back, home, and more) and
allowing you to start and stop text-to-speech on a book.  A sighted reader on
this tablet has the capability to browse the Web, play music, play audio
books, download and read magazines and newspapers, buy Android apps, read
e-mail, view documents (this ay be accessible, I didn&#039;t get a chance to check),
browse photos, voice chat, and read books.  We are limited to access to the
settings, navigating our library, and using the digitized speech equivalent of
a cassette tape.  We can play and pause speech, and it will read continuously,
just like on the Kindle Keyboard, but we cannot navigate accessibly.  No
headings, paragraphs, pages, sentences, words or characters can be
distinguished, nor can you go back accessibly. Tables of contents and social
media integration are likewise unavailable to blind users.
We were concerned by these conclusions, and decided that perhaps we were
missing some details, so we called the company. (Accessibility was a very
small part of the help page after all.)  We spoke with two different customer
service reps, and indeed, the reps verified that yes, this is the extent of
the accessibility of the device.
It is hard to see the accessibility features in the Kindle Fire as a gesture
of goodwill.
Amazon is familiar enough with what true accessibility looks like, both
directly from us, from the work their competition has done, and even from the
screen access packages it requires to allow a PC user to read with text to
speech on a computer.
It cannot claim ignorance when Google, Apple, and Microsoft all offer far more
accessible devices (they all have their problems, but let&#039;s be honest, these
guys are all making a legitimate effort.). Furthermore, both the iPad and the
Nexus 7 are confirmed to offer accessible eReaders from other creators (several
of which can be used with Braille) while no access to Kindle books is available on any of these platforms.
Amazon needs to stop burning blind readers with these half-hearted attempts at
accessibility in all versions of the Kindle, including the Fire. What is
needed now is for it to implement real accessibility, rather than expecting
blind readers to accept a cassette tape equivalent in an era of multi-purpose
tablets.&lt;/p&gt;
]]></description>
			<content:encoded><![CDATA[<p>Doing some research, I found the following from NFB.  I can&#8217;t see buying a Kindle<br />
 Fire at this point in time.  I&#8217;ll continue to use my Kindle Keyboard to reae Kindle books.</p>
<p>Amazon, Why Do You Keep Burning Blind Readers?<br />
Submitted by cvangerven on Fri, 12/07/2012 &#8211; 13:00<br />
Blog Date:<br />
Friday, December 7, 2012<br />
By Amy Mason</p>
<p>According to ZDNet and Engadget the Kindle Fire will be getting Explore by<br />
Touch and Voice Guide to provide<br />
accessibility features to blind and visually impaired customers.<br />
These features were first introduced in Google&#8217;s Android, Ice Cream Sandwich<br />
operating system. (This is the basis of the OS for the Kindle Fire and Fire HD<br />
which has been heavily skinned by Amazon for the device.)  Google has since<br />
released Jelly Bean which has improved markedly on accessibility.  If this<br />
were Amazon&#8217;s only weakness,<br />
an out-of-date OS, I would be disappointed, but I would understand. This is<br />
not, however, Amazon&#8217;s only problem.<br />
Their weakness instead, appears to be a disregard for the wishes of its blind<br />
consumers.<br />
Blind people want Kindle books. We want them badly enough that I know several<br />
blind people who have chosen to buy the Kindle Keyboard, despite being unable<br />
to do anything more than start and stop text-to-speech on their books.  The<br />
PC edition (with accessibility plug-in) is slightly better.  If a user is<br />
willing to sit at a PC, they can read by navigational elements as small as a<br />
sentence at a time, and as large as a page (seriously, you have to sit at the<br />
computer and turn every page.  What a thrilling way to read a book!)<br />
I hear a few of you saying, &#8220;Ok, Amy, so you are upset about the past, but now<br />
Amazon is offering this additional accessibility in the Fire&#8221;.  I am sorry to<br />
disappoint<br />
you, but for all intents and purposes it did not improve on their existing efforts.<br />
We purchased a Kindle Fire HD, and received it last Friday.  We read on<br />
Amazon&#8217;s website that there were accessibility features, so we felt that we<br />
had to do our due diligence and test their work. First of all, when you get<br />
the device,<br />
you have to have a sighted person turn on the accessibility features because<br />
there is no way for a blind person to turn them on independently.<br />
Secondly, access is limited to the device settings, the collection of books in<br />
a user&#8217;s library, the primary navigation buttons (back, home, and more) and<br />
allowing you to start and stop text-to-speech on a book.  A sighted reader on<br />
this tablet has the capability to browse the Web, play music, play audio<br />
books, download and read magazines and newspapers, buy Android apps, read<br />
e-mail, view documents (this ay be accessible, I didn&#8217;t get a chance to check),<br />
browse photos, voice chat, and read books.  We are limited to access to the<br />
settings, navigating our library, and using the digitized speech equivalent of<br />
a cassette tape.  We can play and pause speech, and it will read continuously,<br />
just like on the Kindle Keyboard, but we cannot navigate accessibly.  No<br />
headings, paragraphs, pages, sentences, words or characters can be<br />
distinguished, nor can you go back accessibly. Tables of contents and social<br />
media integration are likewise unavailable to blind users.<br />
We were concerned by these conclusions, and decided that perhaps we were<br />
missing some details, so we called the company. (Accessibility was a very<br />
small part of the help page after all.)  We spoke with two different customer<br />
service reps, and indeed, the reps verified that yes, this is the extent of<br />
the accessibility of the device.<br />
It is hard to see the accessibility features in the Kindle Fire as a gesture<br />
of goodwill.<br />
Amazon is familiar enough with what true accessibility looks like, both<br />
directly from us, from the work their competition has done, and even from the<br />
screen access packages it requires to allow a PC user to read with text to<br />
speech on a computer.<br />
It cannot claim ignorance when Google, Apple, and Microsoft all offer far more<br />
accessible devices (they all have their problems, but let&#8217;s be honest, these<br />
guys are all making a legitimate effort.). Furthermore, both the iPad and the<br />
Nexus 7 are confirmed to offer accessible eReaders from other creators (several<br />
of which can be used with Braille) while no access to Kindle books is available on any of these platforms.<br />
Amazon needs to stop burning blind readers with these half-hearted attempts at<br />
accessibility in all versions of the Kindle, including the Fire. What is<br />
needed now is for it to implement real accessibility, rather than expecting<br />
blind readers to accept a cassette tape equivalent in an era of multi-purpose<br />
tablets.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Russ Kiehne		</title>
		<link>/2012/12/11/serotalk-podcast-134-the-cheese-stands-alone/comment-page-1/#comment-4786</link>

		<dc:creator><![CDATA[Russ Kiehne]]></dc:creator>
		<pubDate>Wed, 12 Dec 2012 14:57:43 +0000</pubDate>
		<guid isPermaLink="false">/?p=2068#comment-4786</guid>

					<description><![CDATA[&lt;p&gt;I was wondering, will the Serotalk team be doing An Accessibility Review of
The Amazon Kindle Fire 8.9 tablet like they did with the Kindle 3?&lt;/p&gt;
]]></description>
			<content:encoded><![CDATA[<p>I was wondering, will the Serotalk team be doing An Accessibility Review of<br />
The Amazon Kindle Fire 8.9 tablet like they did with the Kindle 3?</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
