All About Access

Yesterday when I read Peter Korn’s announcement that OpenDocument v1.1 is now an OASIS standard, I almost whipped out a quick entry. Now I’m glad I waited because there’s even more good news thanks to the accessibility guys at OpenOffice.org: Version 2.2 for Linux/UNIX, currently in development, now exposes tons of text attributes to assistive technologies, which means screen readers such as Orca can now provide those details to the user. And that, of course, means that users who are blind can identify exactly how the text in their documents is formatted and be confident that what they have produced looks the way they intended. Thanks guys!!!

I suppose after looking their gift horse in the mouth, suggesting that evil is as evil does regardless of what your mission statement may claim, and, oh yeah, that whole call to action business, I should give Google some credit. Or at least the benefit of the doubt. Google will be presenting at CSUN this year:

• Accessibility at Google: An Overview


• Audio CAPTCHA at Google

I hope to hear not only a strong committment to accessibility from the Mountain View delegation, but also a strong willingness to learn. Don’t talk to us; talk with us.

With any luck, their second session will be well-attended by members of the Deaf-Blind community (for whom Audio CAPTCHA is as accessible as the visual version).

I was just glancing over the list of General Sessions for the upcoming CSUN conference. OpenDocument Format and open source solutions are certainly well-represented this year:

• Collaboration and Web Access using the Orca Screen Reader


• Creating Accessible Documents in OpenOffice.org


• DAISY: Free, Open-source Tools from the Urakawa Project for Authoring Accessible Multimedia


• IBM’s Accessible Open Computing Strategy: Usable Access of Emerging Technologies and Platforms


• Obtaining and Installing Ubuntu Linux Using the Orca Screen Reader*


• Opening Doors with Open Source: Screen Reader Access to Linux/UNIX*


• OpenOffice Document Access using the Orca Screen Reader


• Remote Access Bridge: Cross-Platform Accessible Remote Access to the Linux Desktop


• Sakai: A Case Study of Accessibility in Open Source Applications


• Tools for Improving OpenDocument Format (ODF) Accessibility


• Topics in Java, UNIX, and Open Document Format Accessibility

*Disclosure: I am one of the co-presenters in this session.

There are at least two additional presentations addressing the barriers posed by the high cost of commercial assistive technology products, including:

• A Review of Lite Tech Low Cost Communication Devices (Those under $1500)


• Accommodating Seniors on $100/Computer or Less

(The fact that “low cost” and “under $1500” are used synonymously speaks volumes, doesn’t it? )

Should be an excellent conference for folks interested in finding ways to bridge the “digital divide.”

Sun’s first Corporate Social Responsibility Report was published yesterday. The report highlights—and rightfully so—Sun’s contributions in the area of access to information and technology for people with disabilities. Weighing in at 36 pages, the report highlights a number of other things as well. Fortunately, Peter Korn has quoted the accessibility-related section for the time-impaired.

In his entry Peter also makes the comment:

Working on accessibility is often a lot of hard, less-than-pleasurable work. A lot of it is convincing other engineers that they have to change how they do things (after first painstaking tracking down bugs and misbehaviors in other folks’ code). [....]

I had to chuckle. I probably shouldn’t admit this, but guess how I spent my weekend—and a few evenings last week.  It certainly wasn’t easy work, yet the entire time I kept thinking how absolutely wonderful it is to be able to track down issues and to talk to the engineers who can fix them.  It’s turning into a hobby of mine, actually.  In no small part my enjoyment comes from having spent a decade on the outside, unable to look in—forced to be a consumer rather than a contributor.  I have the added luxury that no one gets cranky at me because I have no impact on shipping deadlines.

In all seriousness though, I cannot tell you how many times I’ve come across an accessibility regression in the Windows environment and have been powerless to do anything about it.  I mean, where do you even begin?  It would be nice to know where the breakage occurred, but you have no way of knowing: All there is are vague symptoms.  On a good day you can at least narrow it down to the product which is at fault, but you’re not always that lucky.  So there is pretty much only one option left: complain. But to whom?  At least the manufacturers of the assistive technology products can be reached. In the mainstream world you have to send off an email to some generic support address and hope that someone somewhere takes some notice, and that at some point somebody will do something about the problem—all the while suspecting that you’d have a better shot at winning the lottery.  Winning the lottery wouldn’t be such a bad thing to attempt either, because in all likelihood the only way you’re going to get the fix—should a fix be made—is by purchasing a software upgrade.

In a perfect world, accessibility issues would not exist. And admittedly there are things I’d rather be doing than reading source code and ChangeLogs and trying to track down where something broke and/or could be improved.  But the fact that I, a mere mortal user, have access to that code and can track such things down and can communicate directly with the engineers pleases me to no end.  Open source solutions enable you to shape and refine the tools you need yourself.  It may at times be hard work, but it is incredibly empowering work.

The thing that strikes me most about accessibility in the “participation age,” however, is the collaborative spirit of the community.  Six months ago, I didn’t know what a ChangeLog was or where to get source code, let alone how make sense of either.   The direction and encouragement of other community members enabled me to do these things for myself;  I in turn do what I can to enable others.  The personal growth of individuals within the community is valued—  not just for the contributions that will result from the growth, but for the growth itself.  A theme running throughout Sun’s report is that enabling participation does not merely bring about economic value, but social value as well.  ‘Tis true, ‘tis true:  The end result of participating is not merely the development of the tools that you need, but the personal development and satisfaction derived along the way.

Rich Burridge has worked out how to run Orca from a thumb drive. Excellent!

I’m currently “on the road” doing a training, but I will definitely give this a try when I get back.

Thanks Rich!!

In the spirit of openness, Rich Burridge (with my full support) has decided to move a conversation he and I were having into the open.

The conversation had started out innocently enough around the redesign of an Orca feature, but it eventually led to a bit of a rant on my part. What was I ranting about (this time) you ask? Lack of user participation.

You see, once in a blue moon you come across something that seems too good to be true, but actually isn’t: There really are free operating systems (Linux and Open Solaris), there really is a free office suite (OpenOffice.org), and there really is a free screen reader (Orca) which shows the potential of rivaling its $1000 commercial equivalents.

But it doesn’t end there; on the contrary: At the risk of repeating myself, the Orca team is actively soliciting user input and basing their design upon the feedback they receive. There have been times (I’m starting to lose track of how many) where I’ve filled an RFE suggesting that “such-and-such feature would be helpful for the end user” and the response has been “okay”—often it’s not “okay, thanks for the suggestion, we’ll take it under advisement”, but “okay, we’ve implemented it, please give it a try and see if it meets your needs.” If it can be easily and reasonably done, Will, Rich, and Mike do it; if it cannot, they start looking for what it will take to pull it off the needed functionality. In other words, there is a free operating system, a free office suite, and a free screen reader whose design we can contribute to so that it best suits our needs. All we have to do is participate.

Yet people are not participating. That is what I was ranting to Rich about.

Of course, I am exaggerating a bit (as friends, colleagues, and regular readers of All About Access know all too well that I am wont to do)—but only a bit. Some people are participating. Some people are sharing their needs and wants with the Orca team. Most, however, are not. Why is that?

Rich had some thoughts on that matter:

Why this is all strange to the blind users who are now trying out Orca is that they are so used to paying a large sum of money to a commercial organization and dealing with the way that support is handled in such a company, that they don’t realize that alternatives exist.

Used to “dealing with the way that support is handled in such a (commercial) company”: check. “Don’t realize that alternatives exist”: check. “Used to paying a large sum of money”: I don’t think so. The average blind user doesn’t pay a large sum of money for their screen reader. The average blind user is provided with their screen reader through their local school district, vocational rehabilitation agency, employer, charitable organization, etc. It’s like medical care: Some of us pay large sums of money because we do not have health insurance; some of us pay large sums of money because we need a screen reader but for one reason or another can not obtain funding. But in both cases, that is not the majority of the respective populations. Far from it. Most of us are provided with what we need—or we do without.

So why am I nitpicking on this one point when Rich’s observations are, on the whole, spot on? Because I think the medical model of rehabilitation services is largely to blame for the limited participation of persons with disabilities in open source communities.

If everyone really were used to paying large sums of money for their screen reader, I think they’d be beating down the proverbial door to check out, and contribute to the development of, Orca. And that would be good for everyone who cares about affordable assistive technology for computer users who are blind. Does that mean I think we should immediately dump the model we currently use for providing assistive technology services? No, not any more than I think we should immediately dump the model we currently use for providing health care services. In either case, such a drastic measure would put far too many folks in a position more unsatisfactory than the status quo.

So what then do we do? To be honest, I’m not sure.

All I can think of doing is what I’m already doing, namely making people aware of the free, open source alternatives to the commercial products they currently use—or would use if they could afford to do so—and encouraging them to participate.

I also hope that as more and more members of the Independent Living community become aware of free, open source solutions for computer users with disabilities, we’ll see a significant increase in participation. After all, the FOSS movement has a lot in common with the IL movement.

I’m certainly open to other suggestions.

This past Friday, I had the great pleasure of attending the first of what will hopefully be a regularly-occurring event: The Orca users group in Boston. Thanks so much to Joe Lazzaro of ITD for hosting it! And thanks to Will Walker of Sun Microsystems for presenting not just Orca, but also the “big picture” of Linux/UNIX. I think we all came away with a FAR better understanding than we arrived with.

The turnout was great: 22 individuals, 17 of whom are blind or visually impaired; the constructive feedback even better! At the end of the day, we had compiled a list of “request for enhancements” which, as promised, I entered in Bugzilla that evening.

The subsequent response from the Orca team to the RFEs amazed me. I suppose by now it shouldn’t have. In the past couple of months, I’ve come to realize that the Orca team members truly care about creating compelling access to Linux/UNIX for users who are blind, and that they put in the long hours and effort required to ensure they accomplish no less. Still…. It was, after all, Friday night. So I don’t think it’s unreasonable for me to have been at least a little bit surprised to discover Rich examining each RFE I entered more or less in real time, in many cases responding that it would be easy to implement and describing how he would go about doing so. For a guy who claims to like science fiction, Rich has clearly learned nothing from Scotty on Star Trek. By Saturday morning, Rich was beginning to implement the solutions to the straightforward RFEs and soliciting feedback from users and the team on the rest. Will joined in the discussion, and work on the Boston RFEs continued throughout Saturday. Sunday was no different. Like I said, these guys take their work—and user feedback—VERY seriously.

If you’re wondering how I know that the Orca team doesn’t take weekends off, it’s thanks in large part to Bugzilla. Any time someone comments on an item you have entered, you are notified via email. I also periodically browse the RFEs and bugs that others have entered, adding myself to the CC list of the ones I care about so that I can follow their progress as well. Bugzilla even has RSS support. Unlike commercial software development, what goes on in the open source community is incredibly transparent: If you want to know how things are progressing, all you have to do is look. If you want to influence that progress, participate. Bugzilla is a great resource: Again, it’s users and developers partying together!

And then there is Rich’s blog. Rich blogs about all sorts of interesting things—one of which is Orca. That’s how I found out that this weekend he also added support for a pronunciation dictionary. Very cool! (And yes, Rich, I should admittedly read the changelogs more often than I do. Please keep blogging about Orca! )

Finally, there is the Orca web site (http://live.gnome.org/Orca) and the mailing list (see http://mail.gnome.org/mailman/listinfo/orca-list for more information). If you’re interested in Orca—and I do hope that you are!—I encourage you to check out both so that you can learn more about, and contribute to the development of, what is becoming a really great screen reader.