There are a number of projects in the open source community that address different accessibility issues. The Gnome accessibility project (http://developer.gnome.org/projects/gap/ ) is probably the most widely known and most publicized. However, most of the Linux accessibility projects are, by necessity, focused on the command line interface instead of the graphical desktops.
In general, there are several areas that accessibility focuses on: visual, hearing, mobility, and cognitive or learning impairments. Currently, visual impairment is getting a lot of attention, as many visually impaired users require a screen reader and speech synthesizer (either hardware or software) for output. There are a number of screen readers (Emacspeak, Speakup, and Jupiter, to name a few) available which use either hardware or software synthesizers, but currently all of them work only in console mode (except Emacspeak, which works from within the Emacs environment). The Gnome accessibility project is working on a screen reader for Gnome, called Gnopernicus ( http://developer.gnome.org/projects/gap/AT/Gnopern icus/index.html). Linux figureheads like Alan Cox are helping to write requirements for an adapter-ready kernel ( http://www.speechinfo.org/fdawg/). SuSE Linux automatically detects braille devices during installation, making it possible for visually impaired users to install Linux without sighted assistance. For users who do not require audio output, screen magnifiers, larger fonts, icons, and mouse pointers are available in both KDE and Gnome, in addition to other accessibility features.
For hearing impaired users, the ability to have visual cues, such a visual bell, is crucial. For those with mobility impairments, features like Sticky Keys, Toggle Keys, and Bounce Keys, as well as on-screen keyboards, can make it easier to type. It is also possible to configure a standard keyboard to take one-handed input. Voice recognition systems, such as Open Mind Speech or ViaVoice Dictation may be a more viable option for some. Users with epilepsy, which might be triggered by on-screen animations, must be able to turn off features like window opening/closing animation. For more information on these options, as well as those mentioned for visual impairments above, refer to the Linux Accessibility HOWTO ( http://www.linuxdoc.org/HOWTO/Accessibility-HOWTO/ index.html).
In June 2001, the US government enacted Section 508 ( http://www.section508.gov/), which requires that all government IT tools and services be accessible. This means that the government won't buy and IT tool or service unless it is compliant with the criteria outlined in Section 508. Thus, from a purely business perspective, it makes sense for the Linux community to address the accessibility issue. From the user's point of view, it makes even more sense. For example, a visually impaired Windows user might choose JAWS for Windows (a commonly-used Windows screenreader), which is $795 US. Alternative Windows screen reading applications are less expensive, but some require a hardware synthesizer, which can cost in excess of $1600 US. Users must also purchase the Windows OS. However, a Linux user can get the Emacspeak screenreader and ViaVoice software synthesizer (not to mention Linux), for FREE. This is one of the reasons that many visually impaired users, at least, are making the move to Linux.
Also consider those of us who wear glasses and use lower resolution and/or larger fonts/icons so that we can see the screen better - these are accessibility features. Someone with a broken arm could take advantage of dictation apps or a one-handed keyboard - also accessibility features. What about the next time you're in a noisy airport working on your laptop, and you can't hear the audio bell that alerts you to a new email? You'd turn on the viusal bell instead - again, an accessibility feature. Making Linux doesn't just benefit those who are "handicapped," it benefits everyone.
Slashdot Mirror
There are a number of projects in the open source community that address different accessibility issues. The Gnome accessibility project (http://developer.gnome.org/projects/gap/ ) is probably the most widely known and most publicized. However, most of the Linux accessibility projects are, by necessity, focused on the command line interface instead of the graphical desktops.
In general, there are several areas that accessibility focuses on: visual, hearing, mobility, and cognitive or learning impairments. Currently, visual impairment is getting a lot of attention, as many visually impaired users require a screen reader and speech synthesizer (either hardware or software) for output. There are a number of screen readers (Emacspeak, Speakup, and Jupiter, to name a few) available which use either hardware or software synthesizers, but currently all of them work only in console mode (except Emacspeak, which works from within the Emacs environment). The Gnome accessibility project is working on a screen reader for Gnome, called Gnopernicus ( http://developer.gnome.org/projects/gap/AT/Gnopern icus/index.html). Linux figureheads like Alan Cox are helping to write requirements for an adapter-ready kernel ( http://www.speechinfo.org/fdawg/). SuSE Linux automatically detects braille devices during installation, making it possible for visually impaired users to install Linux without sighted assistance. For users who do not require audio output, screen magnifiers, larger fonts, icons, and mouse pointers are available in both KDE and Gnome, in addition to other accessibility features.
For hearing impaired users, the ability to have visual cues, such a visual bell, is crucial. For those with mobility impairments, features like Sticky Keys, Toggle Keys, and Bounce Keys, as well as on-screen keyboards, can make it easier to type. It is also possible to configure a standard keyboard to take one-handed input. Voice recognition systems, such as Open Mind Speech or ViaVoice Dictation may be a more viable option for some. Users with epilepsy, which might be triggered by on-screen animations, must be able to turn off features like window opening/closing animation. For more information on these options, as well as those mentioned for visual impairments above, refer to the Linux Accessibility HOWTO ( http://www.linuxdoc.org/HOWTO/Accessibility-HOWTO/ index.html).
In June 2001, the US government enacted Section 508 ( http://www.section508.gov/), which requires that all government IT tools and services be accessible. This means that the government won't buy and IT tool or service unless it is compliant with the criteria outlined in Section 508. Thus, from a purely business perspective, it makes sense for the Linux community to address the accessibility issue. From the user's point of view, it makes even more sense. For example, a visually impaired Windows user might choose JAWS for Windows (a commonly-used Windows screenreader), which is $795 US. Alternative Windows screen reading applications are less expensive, but some require a hardware synthesizer, which can cost in excess of $1600 US. Users must also purchase the Windows OS. However, a Linux user can get the Emacspeak screenreader and ViaVoice software synthesizer (not to mention Linux), for FREE. This is one of the reasons that many visually impaired users, at least, are making the move to Linux.
Also consider those of us who wear glasses and use lower resolution and/or larger fonts/icons so that we can see the screen better - these are accessibility features. Someone with a broken arm could take advantage of dictation apps or a one-handed keyboard - also accessibility features. What about the next time you're in a noisy airport working on your laptop, and you can't hear the audio bell that alerts you to a new email? You'd turn on the viusal bell instead - again, an accessibility feature. Making Linux doesn't just benefit those who are "handicapped," it benefits everyone.