You raise very valid points, Raman. Perhaps we might consider a challenge to Nielsen. Perhaps we could point out that their presuppositions are unfair and lead to unhelpful conclusions? As you point out, it's the task, not the particular web site for that task, which matters. And, the performance of users with minimal skills and inadequate tools is certainly a questionable measure. Janina T. V. Raman writes: > The Nielsen Norman Group has made available a detailed report on > accessibility, which includes the results of several usability tests > --- see Going Beyond Alt Text. It's a very good read, and though its > conclusions might be depressing to people coming to this area from the > outside --- they should be no surprize to users who have been trying to > use the Web via spoken output over the last 10 years. From the > perspective of the Emacspeak user who lives in a specialized browsing > environment that is optimized for performing oft-repeated tasks, there > are several interesting take-aways from this report: > > - Though so-called Web Accessibility Standards have attempted to focus > on the behavior observed when using screenreaders with mainstream > browsers, that thread of work appears to be achieving little with > respect to the real metric of task completion. As technologists, we > would all do well to remember that users come to the Web, and Web > Access solutions not to use the browser but rather to complete one or > other task. > - As described in Specialized Browsers and The Web The Way You Want It, > task-oriented access and specialized user-optimized web tools have been > around since the inception of the Web. > - Though the Nielsen study asked users to carry out each of the given > tasks by going to a given Web site, it would be interesting to see how > such tasks work out in the Emacspeak environment. It's a given that an > emacspeak user trying to buy a music CD at an online store would run > into a brick wall fairly quickly (see, even online stores are made of > brick and mortar;-)). However, as an Emacspeak user I'd never do that > I'd either go to Amazon's highly efficient Amazon Accessible Store or > faster yet, type an appropriate query at Google and click on the > relevant Ad that sports a Google Checkout badge. > - And more interestingly, it would be interesting to carry out a > follow-up user study to compare the rate of task completion as well as > observed efficiencies/inefficiencies between users of Emacspeak and > generic browser/screenreader combinations for tasks such as: > - Play NPR news from the last hour. > - Play your local NPR station. > - Play BBC News from the last hour. > - Skim the top stories from CNN. > - Look up today's stock market numbers for the major indices. > - And items too numerous to enumerate in this margin. > > -- > Posted By T. V. Raman to emacspeak The Complete Audio Desktop at > 12/20/2007 02:49:00 PM -- Janina Sajka, Phone: +1.202.595.7777; sip:firstname.lastname@example.org Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility email@example.com Linux Foundation http://a11y.org ----------------------------------------------------------------------------- To unsubscribe from the emacspeak list or change your address on the emacspeak list send mail to "firstname.lastname@example.org" with a subject of "unsubscribe" or "help"
If you have questions about this archive or had problems using it, please send mail to:email@example.com No Soliciting!
Emacspeak List Archive | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | 1998 | Pre 1998
Emacspeak Files | Emacspeak Blog | Search the archive