I came across this video at the top of CNN last night and thought it was a pretty sweet story. A group of gamers carefully cataloged every sound and every move needed to beat a game – which seems to be Legend of Zelda: Ocarina of Time – and gave the info to a blind player they’d met on an online discussion forum so that he could beat the game. Check it out:

Blindness and video games is actually an issue that gets talked about fairly often, whether in the context of a master’s thesis about how to make more accessible video games or blind players discussing the ways that they navigate World of Warcraft.

One interesting element of the Zelda case above is how rich the audio is in Zelda, with very specific cues for specific attacks and in-game events, like opening a treasure chest –

Cues like these are undoubtedly important for people with vision impairments, and I know that I rely on them to keep me on track and entertained in my own gameplay. These sounds, then, seem like an important element of universal design in games, as they may provide helpful information for large numbers of players. Yet, overreliance on audio information can also be a problem, as deaf players may find themselves excluded from Warcraft raids in which players are all using headsets and voice chat instead of text chat.

The mismatches in audio and visual needs only highlight the continued need for improvement in text-to-speech and speech-to-text technology. These technologies are getting a lot of attention this week, with Roger Ebert debuting his text-to-speech voice (compiled from old video clips of Ebert’s actual voice) on Oprah and YouTube announcing the full roll-out of its autocaptioning service, which I blogged about during its initial stages last fall.

But, I think the human, community element of this particular story is also fascinating – I don’t know if perfect code-driven accessibility will ever be possible without some degree of human interpretation of language and meaning, and I like seeing instances in which people can pool their resources to make a more accessible world (at least for this one Ocarina player). Plus, the fact that this occurred in a gamer community around Zelda is a fun connection to my partner, whose dissertation was partially about the activities on Zelda forums, and who sent me the video in the first place!

Just a quick hit to say happy birthday to Louis Braille and the written system he pioneered. There are a number of articles out there lately focused on how e-readers are supplanting Braille. E-readers, Kindles and screenreaders for the web are all exciting and useful technologies, and from a universal design standpoint, they do a lot of good crossover work as both assistive devices for people with visual impairments and as enhancing technologies for those with vision.

But, as is pointed out in FWD’s link round-up, these technologies are only useful for visually impaired people with normal hearing abilities. Even more troubling, from some research I did on screenreader technology a few years ago, these audio technologies are difficult to learn, synthesized speech is still imperfect, and the temporal element of having written material read aurally means that progress and comprehension can be very slow. Thus, a number of people still prefer screenreaders that create Braille output – it can be skimmed, revisited, and stored much more easily than audio formats.

So, hooray for Braille and ongoing advances in making the written word available to all! Blogging will continue to be light around here, as I’m travelling more in January, so here’s a thematically appropriate web comic from XKCD to wrap things up!

A stick figure reads a sign in Braille - the Braille does not match the written text, but begins to say "Sighted People Suck"

YouTube official logoYesterday, Google announced that it would deploying several new options for increasing the number and quality of closed captioned videos on the site. The New York Times reported on this as a first step to making videos available to deaf and hearing-impaired audiences, but it seems clear that there are a lot of potential beneficiaries – foreign language audiences (captions can be translated to 51 languages), those of us who can’t turn on the speakers at work, and anyone who wants to search the verbal content of a video.

So, how are they doing it? First, speech-to-text technology currently used by Google Voice is being applied to a small number of videos on the site (largely educational content) to produce captions automatically.

“Because the tools are not perfect, we want to make sure that we get feedback from the video owners and the viewers before we roll it out for the whole world,” Mr. Harrenstien said. “Sometimes the auto-captions are good. Sometimes they are not great, but they are better than nothing if you are hearing-impaired or don’t know the language.”

Presumably, if this works, speech-to-text will be rolled out more broadly. For now, you can take a look at how this works below. To see the captions, Google/YouTube explains – “Click on the menu button at the bottom right of the video player, then click CC and the arrow to its left, then click the new “Transcribe Audio” button.” I’ve picked a clip of PBS’s upcoming series This Emotional Life, focusing on Asperger’s.

Obviously, it’s not perfect – “Asperger’s syndrome” is transcribed as “Mister Gerson” – so I hope that speech-to-text improves before this initial stage is extended to other videos. This, however, leads to the second option that Google/YouTube have made available, which is to provide your own captions for videos you upload.

Now, after you upload a video, you can also upload a text file  – YouTube will combine the video and the text to create captions. Through “auto-timing,” YouTube will match a transcript (a file with only verbal content) to the video using speech recognition, or will match a caption file (which includes time codes for the text to appear) to the video. The help file on this seems fairly clear, and also includes tips like including bracketed information about non-verbal sounds [whistling], or using >> to indicate changing speakers inthe captions.

I gave it a try – not the easiest experience. They weren’t kidding when they said that clear speech works best, as my transcript file (no time code) was not able to be matched and displayed as captions. People singing to cats didn’t translate well. Thus, to get a captioned video, I had to try the old fashioned way, creating a .sub file with time codes. This quickly got me in a bit over my head – while I could do it, given the time, there’s a reason most people don’t caption their YouTube videos. It’s time intensive, there’s a learning curve involved, and the results may not seem important enough to justify the work.

This, of course, is exactly why forays into speech-to-text and auto-timing are so exciting. If captions could be created automatically, or from a simple text file, captions on user-created video would certainly become more common and make the world more accessible. While the tools as they are today aren’t anywhere near perfect, it’s certainly a first step in creating automatic accessibility features for participatory media.

As someone who studies accessibility and internet media, I’m constantly torn between getting excited about social/participatory media and being disappointed in their access options. This WordPress blog I’m using is notoriously terrible in its implementation of image alt text, for instance. Blogging has given so many people an outlet to write and connect, but if they want to make a blog accessible, it takes additional research and effort. Attempts to build accessibility features in automatically are, in my opinion, game-changers when they’re done well. I’ll withhold judgment on this YouTube move for now – it has potential – but I’ll be watching to see whether it develops .

Blind Stenographer using DictaphoneRecently I’ve been thinking about social networks as a space for self-representation and/or artistic expression. This is largely a result of taking an art history and new media course this semester, and trying to figure out how to bring in media studies and my own interests. But, I’ve found Flickr to be a really interesting place to start thinking about PWD using online services and digital media to create art/representation and to share it in a pseudo-gallery space.

Several Flickr groups have been interesting jumping-off points – Blind Photographers, for instance, is a small group, but one that explicitly asks “How does having a different visual experience affect our photography?” !Rock That Disability! is another interesting (and much larger) group. Photos here include both those taken by PWD and those taken of PWD and assistive devices. The group also seems to have an active community forming. And, of course, there are tons of gorgeous, interesting and moving photos to browse through. Wheelchairs, Disability Arts Around the Globe and Disability History all also offer some interesting images and communities. The photo with this post is from the Disability History pool, posted by the Library of Congress, and depicts a turn-of-the-century woman using a dictaphone – in a written caption, she’s identified as a “blind stenographer.” Just another reminder of how assistive devices have always been with us and served both PWD and others who needed dictation machinery.

I woke up early yesterday to listen in on the National Broadband Plan’s workshop on access for people with disabilities (PWD).  It’s a long session, but with a lot of really interesting people from government, advocacy/non-profit, industry and academia. As I’ve gone in and out, I’ve heard a lot of discussion about how accessibility can be better funded and supported within the government, and how that might affect outcomes and outreach about accessible online content. There’s been a lot of talk about the ADA, Section 508, the Rehabilitation Act more broadly, of course; seems there’s still some uncertainty about which of these laws’ definitions of disability should be used in things like the Census supplement.

I was surprised, though, to hear Eric Bridges from the American Council of the Blind praise Apple for the development of the iPhone, “the first accessible PDA, with no buttons on it.” He didn’t get a chance to elaborate, but I’m planning to explore my iPhone a little more and see if I can’t take its accessibility features for a ride. Is it voice activated? Alternate touch interface? So. Curious.

I didn’t get a chance to listen to the full session, so I’m looking forward to getting the public record and seeing how this develops. The FCC’s blog, blogband, is a great resource for keeping on top of the National Broadband Plan, whether your interest is disability, rural access, policy, or broadband access more generally.