Slashdot Mirror
What Accessibility Options Exist for Unix?
pll asks: "My wife is getting a Masters in Human Factors and Information Design.
Tonight she attended a session on Handicapped Accessibility in Technology. Evidently MS has spent years studying this area, and the
options one has under Windows is supposedly quite impressive (provided you install the accessibility packages). According to the lecturer, there are over 50 million handicapped people in the United States alone, and obviously even more worldwide. This got me thinking...the Free/Open software communities pay an awful lot of attention to i18n, but other than Emacspeak, what kind of attention have we paid to handicapped accessibility? I'm not aware of anything, other than Emacspeak, and that doesn't do much to enable the use of Gnome or KDE to a handicapped person." While Emacspeak does have some uses in this area, it's primarily only useful for the blind. What about people without the use of their hands, or features for the deaf, and so on?
Take a look at the GNOME accessibility project to see what is being done under GNOME.
/Janne
Trust the Computer. The Computer is your friend.
kit to enable speech and speech recognition in various Linux projects. See here.
-- The Sage does nothing, and nothing is left undone. --Lao Tzu
As mentioned in a side discussion on the window-less office article, open source developers only develop stuff to scratch their own itch. If there isn't handicapped open source developers, you won't find much open source handicap software packages.
I don't agree that this is the way Open Source should go, but that's the reality of it.
Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
Windows XP ships with a decent magnifying utility (called "magnifier") but even they recommend in the opening dialog box getting something more robust. Popular packages to increase the entire desktop start around $19.99, but more "professional" ones can scale all the way up to $700!
Another problem is that, despite "anti-discriminatory practices", handicapped people simply aren't hired for too many computer-literate positions. Many IT managers don't want to foot the bill for high-end accessibility utilities. That's why something more robust than Gnome's project (and KDE's paltry magnifying utility) are so needed.
I did some tutoring for blind students in college and UNIX systems were much easier to use than Windows for blind students just because you could do everything without a GUI. The braille displays or auditory displays work best with text and with UNIX type systems you can do pretty much anything at the command prompt and text only... even web browsing.
There are 10 types of people in this world, those who can count in binary and those who can't.
285,663,670 / 50,000,000 = 5.71.
So more than 1 in 6 people is handicapped. *Looks around the room.* I know of one person out of the 110 or so in my workplace that is "handicapped" to the point that they use accessibility options. Admittedly, there are reasons why my workplace would be lower than average on the number of handicapped people, but I was wondering just what the criteria used were.
Note that I'm _not_ saying that there aren't a lot of handicapped people around, or that accessibilty options aren't important (they're very important to that one individual, who is in turn very important to us). I'm just curious about how those statistics were arrived at, since it feels like an astoundingly high number to me.
After all, 95% of statistics are made up on the spot.
-Puk
p.s. If you're going to flame me about my use of the word handicapped or claiming I'm downplaying the importance of accessibility tools, please don't even bother.
I'd say that 6 out of 6 people could benefit from accessibility technology. You see, even though the disabled need accessibility, but we all benefit when it's included. If you make a program speech enabled, then it's possible to use that program over a telephone. If a program can be configured to use large fonts, it can be used on an LCD display. If a program has keyboard shortcuts for mousable operations, then we can use the program without taking our fingers off the keyboard.
Anyway Ive started looking at Voice Reccognition:
IBM have made there Via Voice SDK freely available, which is being made use of in the rather interesting looking XVoice, though its been passed between developers, the most current page is here ang the mailing list here. However training hasnt been implimented yet, but Via Voice Dictation for Linux compares rather favourably at ~ $50 compared to several hundred for the windows version.
Alternately, there is the Freespeach/Open Mind Speach project, gpl and makes use of the Overflow language/enviroment.
Not really aware of any active projects beyond such, hopefully this ask slashdot will prove to be interesting reading.
troodon.net
I've been working quite extensively within section508 guidelines which outlines electronic accesibility within government systems - from webpages, to software, to the photocopiers in the office. The statistics that are used in cases like this are misleading to those unfamilar with accesibility. You may not think that 1/6 people are 'handicap', but this term is fairly broad when used in this contex. The term also refers to the color blind, people with carpel tunnel syndrome, people with hearing-impairments (but not completely deaf), and the like - anyone who may require any assistance at all or may have difficulty navigating the web or a software product.
At the rate many of us are going, we're going to have weakened eyesight and carpel tunnel syndrome from so many hours on the computer. So we will be relying on many of these advances in accessibility options in the future.
I really recommend section508.gov which is a really great resource for accessibility.
http://leb.net/blinux/
Complete with FAQ, docs and mailing lists.
I have a congenital birth defect that rendered my left ear all but useless and my right ear severely impaired. This means that (1) I do not have stereo hearing; (2) I have a difficult time in situation where there is a lot of background noise; (3) computer software and/or games that depend on audible alerts to signal the user are nearly useless to me.
... but it'd be nice to enjoy them. Diablo II has none, though the Collector's Edition DVD fortunately had subtitles on its versions of the cutscenes.
First off, let me say that I'm glad that there are some provisions for the deaf in Windows; I recently installed XP and used 98SE before that. (At this point, the applications I use basically require Windows, though I have several Linux boxes in the house for applications where free software exists; I also use MacOS X). I will concentrate on Windows because that's (unfortunately) what most people use.
The accessibility options for the deaf are relatively scant. Yes, it's true that those who are hard of hearing don't need a lot in the way of assistance because we can see just fine (aside from sometimes wearing glasses, like me). But there are two major issues with the built-in accessibility tools: (1) They aren't installed by default (I don't think they are; I had to check the box for them when custom installing XP and I believe I did for 98SE as well), so if you don't know that they exist, you won't get them. (2) They don't do a heck of a lot. I've checked the boxes for having applications flash a visual alert, but I've yet to see one do this outside built-in (for that app) options. (I use SecureCRT for telnet; it too has a "visual bell" setting.)
Now, I do a lot of chatting over the Net (you don't know how empowering it is to sit in a group of two dozen people and not miss a word and be part of the conversation until that is denied you in the real world) and I use MUSHClient and mIRC to do it. Both of those applications have built into them options to flash the taskbar button if new text arrives while the program is not the foremost window. All well and good. However, again there is the problem of obscurity: while the options are of course installed with the software, they are not turned on by default and are usually somewhat hard to notice. MUSHclient's is buried deep within the preferences for a specific connection and isn't program-wide, so I can't check "Flash visual alert on activity" in global preferences -- I have to do it one at a time. mIRC is much the same: I have to right-click on a channel's mIRC-Taskbar button and select "Flashing" (not too descriptive an option name; Flash on Activity would be better) and it seems to be rather sporadic at times regarding whether or not it does it in query windows.
Games. I'm a gamer. And a lot of games these days have options for subtitles (Wing Commander III-V stand out here, having options for French and German as well as English subtitles) and a lot don't (why is Starlancer, also made by Chris Roberts, missing them?!). I can't play Thief because it doesn't put up any visual cues. Return to Castle Wolfenstein has none in its cutscenes but since it's a first person shooter game, I can get by without the cutscenes
It is not that hard to add subtitles; fan petitions got some added to at least one of the Zork games. Movie theaters don't have them yet because people claim they're intrusive, but as long as they can be toggled (with a control in a plain, obvious place!), that's not an issue.
So what does Unix need, then?
It needs built-in alert options, which are part of the default install, as part of window managers. KDE, GNOME, Enlightenment, whatever. A standard needs to exist for how applications will address it. Apps need to use it.
The controls to turn these on need to be in an obvious place and marked with clear symbology (the white-on-blue wheelchair symbol is a good start.)
Applications need to be marked as captioned for the hearing impaired on their web sites and on packaging. Develop a standardized symbol for this.
If I sound rather platform-independent, then that's a good thing. If I use all sorts of OSes, then other people out there like me do, too.
i am a soviet space shuttle
Mac OS X 10.1 has a lot of accessibility features, which are all installed by default. The user just has to configure them to taste in System Preferences. It's not entirely free, but the core OS is free and open source, and UNIX compatibility is built-in. You can still install and use all the same software as on any UNIX system, while also having access to Mac software that has a long history of accessibility features. I have a good friend who doesn't have the use of his hands and uses a Mac OS X Mac every day all day.
... if you work with this for a short while, you can get very fast in Mac OS X without taking your hands off the keyboard.
... applications know about them and developers have adapted their software to work with them. Text-to-speech has been around even longer, and it's common for Mac applications to read stuff to people.
The Universal Access System Preference offers enhancements to keyboard and mouse input. Sticky Keys makes modifier keys stick so that a person can type with one finger or with a mouthstick. It has great on-screen feedback, with translucent icons that float over a corner of the desktop showing what modifiers are currently active without blocking your work. Mouse Keys makes the numeric keypad into a mouse substitute. Mac OS has long had standard key shortcuts that work everywhere (Command+F is always Find if Find is available, Command+G is Find Again, Command+Q always quits an app, etc) so a person who is using the keyboard can count on those things working in every application. Macs also have keys on the keyboard for volume up/down, mute audio, brightness up/down, and the eject key for removable media is also on the keyboard, which helps a lot of users. You can also eject disks from the GUI by dragging and dropping or using a menu or key command.
In the Keyboard System Preference, you can enable Full Keyboard Access, which enables you to navigate the entire Aqua GUI with the keyboard. Key shortcuts highlight the menus or Dock so you can move through them from the keyboard, and you can move through dialog boxes and similar things of course. This is an option that many people use outside of whether they have a special need
Speech recognition is and text-to-speech are also built into Mac OS X. It's trivial to open applications and run scripts using your voice. It's easy to have text read back to you in a variety of voices, from almost any application. If the built-in speech recognition isn't enough, then IBM's ViaVoice is available, and enables you to navigate the GUI and dictate into almost any application.
In Finder, you can set icons to be displayed at 128x128, which is large enough that even on a 1600x1024 display, a person with vision difficulties can still have honking great icons. Icon labels are large and bold as well. You can also navigate and perform all kinds of file management tasks using only the keyboard. There is an Undo feature in Finder so that if you make a mistake while you're learning these features, you can easily go back a step, even if you Trashed a file. Those kinds of safeguards benefit every user, of course.
Another aspect to consider is that the Mac UI itself is considered to be much simpler to learn (a bonus when you also have to learn the accessibility features on top of what everyone else has to do), and these kinds of accessibility features have been around since System 6 on the Mac
The downside is that there is currently a transition going on between Mac OS 9 and Mac OS X, so for now and for about six more months, most users have an extra layer of complexity as they work with a mix of native and Classic apps. I don't know how that affects accessibility, but it makes sense that the slight differences between how native and Classic apps react to certain things are going to have to be managed a bit by the user. Window controls are slightly different on new and old -style windows, for example. This is temporary, though. There's a new native "marquee" app coming out about every week. The most recent were Microsoft Office, IBM ViaVoice, and Adobe Illustrator. Also, most Mac freeware and shareware is already native, and there are UNIX and Java2 apps up the ying yang.
AppleScript is another technology that can really help out a person with special needs. You can encapsulate an entire workflow in AppleScript, essentially turning a user task into a script task. So you can make a script such that you drop a file on it, and the file is opened in five or six applications and modified in certain ways and passed onto the next application and then finally uploaded and made live on the Web. This benefits all users, but if I were using a mouthstick, I'd probably have twice the AppleScript collection that I have now, because extra keystrokes are even more precious. Also, it's trivial to add languages so that you can script the Aqua GUI with JavaScript if you want. The component for that is free.