{"id":144,"date":"2013-05-03T14:41:55","date_gmt":"2013-05-03T19:41:55","guid":{"rendered":"https:\/\/buddy.brannan.name\/blog\/?p=144"},"modified":"2013-05-07T19:49:33","modified_gmt":"2013-05-08T00:49:33","slug":"amazon-kindle-accessibility-what","status":"publish","type":"post","link":"https:\/\/buddy.brannan.name\/blog\/2013\/05\/amazon-kindle-accessibility-what\/","title":{"rendered":"Amazon Kindle Accessibility: What?!"},"content":{"rendered":"

This week, the blind and visually impaired community got a surprise, one that we’ve been waiting for for a long time, and one that, it’s safe to say, most of us weren’t expecting. (This would be why it was a surprise, right?) Amazon<\/a> announced that its Kindle app for iOS now had new accessibility features, thus making the app usable by blind and visually impaired iPhone users. They also promise improvements to accessibility on their other platforms. You can read about it at this link.<\/a> I downloaded the app, with a great deal of excitement and anticipation I might add, and it appears to be everything they say it is, with access to not only the reading of books, but also highlighting, Emailing excerpts, notes, looking up words in the dictionary, and searches. In short, this app seems to have done it right, rather than doing it fast. <\/p>\n

The day after Amazon’s announcement, I got an Email from the National Federation of the Blind<\/a> with this this press release.<\/a> I thought I was responding to an Email list–it was early still, and I was still waking up, but I instead seem to have Emailed instead to either the NFB’s other PR person or to the guy that runs NFBNet<\/a> instead. I wrote:<\/p>\n

Continued improvement is needed to make the Kindle ap appropriate for educational settings, say us. <\/p>\n

While I haven’t used the app to read any scientific or mathematical texts, it looks like the app provides access that’s at least as good as that provided by both iBooks<\/a> and the Nook reader from Barnes and Noble.<\/a> I think, though haven’t looked in a while, that it may well be better than KNFB’s<\/a> own Blio,<\/a> which should probably embarrass somebody. So, specifically, what improvements would we suggest? <\/p>\n

In this Email, I neglected to mention Kobo<\/a> or Google Play books,<\/a> both of which have at least some access features, or at least, work to some extent with Voiceover.<\/a> Still, the point remains, as does the question: in what way does the Kindle app need improvement? <\/p>\n

While I agree completely that we should not and will not rest until all of the Kindle platforms are usable by print disabled people, this press release smacks of sour grapes to my ear. Nowhere did the NFB acknowledge that Amazon did good work on this app. Nowhere did we applaud their efforts, long in coming though they may be. In contrast to the NFB’s commending<\/a> of a far inferior implementation in 2009, this current press release almost sounds angry that Amazon did anything<\/b> about the problem. <\/p>\n

I’ve played a bit with this newly accessible Kindle app, and it’s good. It was done right. Where’s the acknowledgement of that? Why commend a half-baked effort that is unsuitable for more than the most casual reading on one hand, but practically spit at a stellar example of what can be done on the other? Could it be because Amazon did it without asking for the NFB’s blessing or input first? In fact, it looks like they may not have asked for anyone’s input, as this came as a real bombshell of an announcement with no leaks.<\/b> <\/p>\n

Really, those of y’all in the national office, would a “Good work, guys, thanks” and virtual pat on the back really be that difficult? Would it hurt you so much? It would certainly do a lot to raise your PR standing in the community. Absolutely do not back away from the stance that access to Kindle on other platforms is necessary, even vital. Please don’t. Such access is critical, and we should not rest until we have it. I have no quarrel with that. But would some recognition of a good effort in which you did not have a hand really be so bad? <\/p>\n

By way of full disclosure, I am an active member of the National Federation of the Blind.<\/a> I have been one for over 20 years. Until a more effective membership organization that mirrors my own philosophy of blindness comes along, I expect to continue to be thus affiliated. That said, I fully expect that this post will not make me very popular among the leadership.<\/p>\n

Update: The NFB’s technology center has published a review of the Kindle app, which you can read on the center’s blog.<\/a> I think that the justifications for grading are fair, and I also believe the criticisms are equally fair. As I haven’t tested all these features myself, I have no reason to argue with their findings. I may well have weighted things differently, and I might have been a bit more forgiving for this being their first run at it. I may not, too. At any rate, I have no quarrel with the review, and if Amazon endeavors to improve the accessibility features they’ve implemented, we’ll all be better for it. Watch this space, I guess. <\/p>\n

Even so, I stand by my opinion that the tone of the press release could have been more positive and supportive of these initial efforts on the iOS platform, long time in coming though they are.<\/p>\n

Update #2: 05\/07\/2013: <\/p>\n

Here’s a link to a different take<\/a> on how Amazon did with implementing accessibility features. This review is much more positive, and it doesn’t seem to have run into the same problems that the NFB technology center did in their review. While some might say I’m waffling, I also have no quarrel with this review, think its points are also valid, and believe that it was conducted in good faith and as objectively as possible, excitement over access to over a million titles notwithstanding. It’s certainly possible that the reading experience differs between iPad and iPhone, where bugs may exist in one and not the other, and there may also be problems with braille display driver implementations or conflicts. I think all of us will be interested to see how more hardware combinations do with the new Kindle app.<\/p>\n","protected":false},"excerpt":{"rendered":"

This week, the blind and visually impaired community got a surprise, one that we’ve been waiting for for a long time, and one that, it’s safe to say, most of us weren’t expecting. (This would be why it was a surprise, right?) the National Federation of the Blind with this this press release. I thought […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9,4,8],"tags":[22,35,23,34,33,85],"class_list":["post-144","post","type-post","status-publish","format-standard","hentry","category-assistive-technology","category-computing","category-opinion","tag-accessibility","tag-amazon","tag-computers","tag-ebooks","tag-kindle","tag-nfb"],"_links":{"self":[{"href":"https:\/\/buddy.brannan.name\/blog\/wp-json\/wp\/v2\/posts\/144","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/buddy.brannan.name\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/buddy.brannan.name\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/buddy.brannan.name\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/buddy.brannan.name\/blog\/wp-json\/wp\/v2\/comments?post=144"}],"version-history":[{"count":4,"href":"https:\/\/buddy.brannan.name\/blog\/wp-json\/wp\/v2\/posts\/144\/revisions"}],"predecessor-version":[{"id":148,"href":"https:\/\/buddy.brannan.name\/blog\/wp-json\/wp\/v2\/posts\/144\/revisions\/148"}],"wp:attachment":[{"href":"https:\/\/buddy.brannan.name\/blog\/wp-json\/wp\/v2\/media?parent=144"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/buddy.brannan.name\/blog\/wp-json\/wp\/v2\/categories?post=144"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/buddy.brannan.name\/blog\/wp-json\/wp\/v2\/tags?post=144"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}