ARRL Responds

In the person of Steve Ford, WB8IMY, QST’s editor, I have received a response to my email from Thursday evening. You can see that email in the previous post.

I forwarded the email I sent originally to Mr. Ford, along with aRRL’s, president, CEO, and first and second vice presidents, and received the below response about 20 minutes ago. Well, I read it about 20 minutes ago, I received it earlier than that.

Needless to say, I am truly angered by his response. SO accessibility was merely an unfortunate casualty of a cost cutting measure? Maybe it will be accessible in the future, because HTML5 is better than flash. Which it is, but HTML5 is not inherently inaccessible. The fact is that accessibility is not, and has never been on ARRL’s radar, in spite of the fact that the issue was brought to its attention.

I’m a lifetime member, but had I not been, I would definitely have to consider keeping my membership, even at the “blind” membership level. As I said before, if I had access to QST, the full QST, when everyone else gts it, I would definitely join at the full membership level and not the “blind” one. But now that I see exactly what my membership organization feels about me, well…

Here’s Steve Ford’s response:

Buddy: We made the transition to the PageSuite platform as a cost saving measure, and also because it offers us the ability to expand and upgrade our e-newsletter offerings, something we have been very eager to do. After careful research, we determined that PageSuite was the best choice to balance cost and features.

Unfortunately, there must always be compromises in a situation such as this. Compatibility with reading software for the visually impaired is just one of them. PageSuite could no doubt create a customized package to address every shortcoming, but the cost would be such that it would eliminate any savings. Unless ARRL wishes to divert the necessary financial resources to create a customized solution, I’m afraid we must work within the capabilities of the standard PageSuite package.

Since PageSuite is based on HTML5 rather than Flash, it is possible that compatible reading software may exist. If that doesn’t prove to be the case, there is still the possibility that such software may eventually be developed. HTML5 is becoming the standard and Flash is in decline, so I suspect we will see increasing software development in this area.

73…

Steve Ford, WB8IMY
ARRL Publications Manager

Audio Demo: Samsung TV With Accessibility Features

Recently, several people have been talking about TV’s, set top boxes, and the like, that have accessibility features built in. So far, the only major cable company who has implemented anything like this is Comcast, and they aren’t everywhere. Supposedly, the rules for this stuff to be accessible to people with disabilities kick in at the end of the year, but it sure doesn’t seem like anyone’s exactly scrambling to make it happen.

Enter Samsung. A couple years ago, they came out with some accessibility features on some larger televisions. These were well outside what I was willing to pay for a TV, given how little TV I watch. This week, however, I got wind of a 32-inch TV from Samsung with these accessibility features built in: talking menus, talking program guide, the whole ball of wax, and for under $300.

A call to Samsung was disappointing. The guy on the phone tried to sell me a 49-inch TV, and couldn’t find one smaller. Samsung doesn’t exactly go out of their way to highlight these features, that’s for sure, but eventually, a couple folks came up with a model number. Online chat with Samsung confirmed the accessibility features, as did the manual. So, thanks to Jeff Bishop and Randy the big R for alerting and tracking down model numbers.

So on to the show. Here we go through the setup of the Samsung UN32J550AFXZA. It went fairly smoothly, and I reckon it could have been done completely independently, though that may have taken some time if I got totally stuck. Backspace doesn’t tell you what characters you delete on the on-screen keyboard. That’s probably the biggest gotcha. Another thing. If you get this TV, you may get some nice music during the setup. I did, once. The talking menus duck the music down pretty nicely though.

Anyway, there is, no doubt, more to explore, like the apps in the Hub, but this should get people started. And maybe excited, because we have an accessible TV that’s actually affordable.

Amazon Kindle Accessibility: What?!

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 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. 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.

The day after Amazon’s announcement, I got an Email from this press release. 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 iBooks and the Nook reader from Barnes and Noble. I think, though haven’t looked in a while, that it may well be better than KNFB’s own Blio, which should probably embarrass somebody. So, specifically, what improvements would we suggest?

In this Email, I neglected to mention Kobo or Google Play books, both of which have at least some access features, or at least, work to some extent with commending of a far inferior implementation in 2009, this current press release almost sounds angry that Amazon did anything about the problem.

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.

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?

By way of full disclosure, I am an active member of the National Federation of the Blind. 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.

Update: The NFB’s technology center has published a review of the Kindle app, which you can read on the center’s blog. 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.

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.

Update #2: 05/07/2013:

Here’s a link to a different take 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.

The Budcast: Chromebook Accessibility

I haven’t done one of these in a while, so I figured it was about time.

In this episode of the Budcast, which is un-numbered because I can’t count that high, we look at the initial setup of the Chromebook and the state of its accessibility. Google has asked several people in the blind/VI community to assist with accessibility testing, and I was lucky enough to be one of those.

While there are a couple rough edges, and a show stopper or two (which we don’t get to in this episode), Google has a great start on making the Chromebook accessible. We do see a couple of those “rough edges” in this podcast, and I’m sure we’ll find more. Hopefully though, as time goes on and more of us have our hands on this stuff, things will improve.

As ever, you can contact me via Email or Twitter with any comments or questions.

Enjoy!

Amazon Responds

I just received the below Email. It sounds like Kindle might be slightly usable, but by no means does it appear to be anywhere close to being used for serious reading. It is also unclear whether one can browse the Kindle store, but it sounds like this won’t be possible.

 

Hello,

Thanks for writing to us with your comments.

Voice Guide lets you navigate your Kindle with spoken menus, selectable items, and descriptions. For example, when you open a book, Kindle speaks your current location and how far you’ve read.

Presently we don’t have the features like enabling the voice guide and TTS features without sighted assistance, navigate or read by smaller increments in text to speech, voice guide or text to speech work in the Web browser, enabling text to speech for the books which have text to speech option disabled.

I’ve sent your comments to the Kindle team for consideration. We’re regularly working on improvements to your Kindle experience. Customer feedback like yours helps us continue to improve the service we provide. 

I hope this helps. We look forward to seeing you again soon.

Did I solve your problem?

If yes, please click here:
http://www.amazon.com/rsvp-y?c=yagwhvtx3324198336

If no, please click here:
http://www.amazon.com/rsvp-n?c=yagwhvtx3324198336

Please note: this e-mail was sent from an address that cannot accept incoming e-mail. 

To contact us about an unrelated issue, please visit the Help section of our web site.

Best regards,

Madhu Y
Amazon.com
Your feedback is helping us build Earth’s Most Customer-Centric Company.
http://www.amazon.com/your-account

A Note to Amazon On Kindle 3

I just submitted the below to Amazon. I encourage others to submit their own concerns, especially for accessibility, to them as well. According to the manual, you can Email kindle@feedback@amazon.com so Email them early and often.

 

I’m very interested in the Kindle 3, but as a blind user, I have a few concerns. Before I outline those concerns, I would like to say that I, for one, am happy to purchase if Amazon can make a commitment to our community to make accessibility improvements where warranted. 

As you might suppose, my concerns directly relate to the text to speech and voice guide features:

1) Will voice guide speak as you type? Will it read options as they are navigated and selected? Can you select books with it? Documentation is definitely lacking in this area. With voice guide enabled, will it be possible to use Kindle as outlined in the rest of the manual, without looking at the screen at all?

2) Do menus wrap? Would it be possible to enable the voice guide and TTS features without sighted assistance? If not, I would recommend that it should be. 

3) With text to speech reading of Kindle ebooks, is it possible to navigate or read by smaller increments? In other words, can I navigate a book by word, or even by character? If I need to have an unfamiliar name or term spelled, is this possible? These features are essential if Kindle is to be used by a student in a classroom environment. 

4) Does voice guide or text to speech work in the Web browser? Can it be used, not only to read Web content but to navigate to that content? Is it possible to browse the Kindle store to purchase books, again, using only text to speech and voice guide? 

5) Will it be possible to enable text to speech for blind users on books where it is by default disabled? If not, is there some way to know whether a book is TTS-enabled before purchasing it? I would hate to buy a book, only to find I am unable to read it. 

In short, I would like some assurance that Amazon is working towrd real accessibility to the Kindle, and not just a token effort that amounts to little more than a toy.

Budcast #3: Random Musings And A Walk To Harbor Freight

In BudCast #3, take a walk with me to Harbor Freight to exchange an air pump. On the way (and on the way home), we meet neighbors and friends, stop in at Radio Shack, and of course, exchange the air pump. Today, we discuss lots of things in brief:

Also, it’s out! The new album from Those Who Dig, “Little Bitty Barley House”, recorded live this past fall, is out. Go andget your Mitochondria fix now, and tell ’em I sent you. OK?