I missed yet another meeting, sigh

kendell clark coffeekingms at gmail.com
Thu Mar 26 20:48:16 UTC 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

hi all
My name is kendell clark, and I just switched over to fedora a couple
of weeks ago. I keep meaning to show up at the documentation meetings
but I keep sleeping through them. I've been working on the abandoned
accessibility guide, and I've basically completed it. The problem is,
I've only modified the plain text version, not the docbook xml markup.
I'll attach it so that others can look at it. Would anyone here be
willing to help convert that into the docbook that the fedora
documentation expects? I'm trying to learn the language so I can
eventually do this myself but I'm not there yet.
Thanks for reading
Kendell clark
Sent from Fedora GNU/Linux
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJVFHCQAAoJEGYgJ5/kqBTdMR0QAJ7U+MlwOQZTuzmd9tt+yeZL
PNL6S7x3S7KMGWh1//MTSfHF/5rAutlPjVqAVVjVxFJXRJMm41wXbkrtjYTqsC7G
ew0k8wKULqRu8bboWMXoyhjRItG2oNTX6fEBQUa1bcWNO6I41RJXL93+UozCXOM7
i8lswgbh3AllmT67hSvMmtuDO+GNHT7cnXnRH+AzrBHc+5cKbcLKEb92DQL23lNo
SzAX3sRsT987ii8PHY/Chif5GILYMui19PRjNTsxlcO+tRB4R6iCFGdv5IwqoLvu
a/YrZIPOFKt/0pBEqH9DF0Nn2RML8smMj8XlHwtZrFw7V5YYq4twFI8Wa47Gnljy
rbuwqMsS31tcGmk7M1+c5ikeNbHsu/65osshGTSBeflSGq6RhIzYueoA/rgEr9jP
UC5H09EWJzsSIzafTlG0xqQhajjyU7/boBmijOSHSS+hc7flTLN1QXk0NIROwqwx
HzVweUKTyoR09b7ZuHBk0x+e2xa+nnFhBkUU1HayTC/zqxsiMTVoXtkPLgJ+kc0v
tfxgIQNt/uOXCv/1O5oMurqnbYVkNMrMwuAdpgtlny6jCmaworob84CwqhuvVp7B
elsQDizVCfZ4xGAU7lXFUdzySwU9/Fr5tBzTwgFWzBYT4rF67xdyEv8iTw5fdHoj
BfwiQDlfl0guIx37df5N
=kUdk
-----END PGP SIGNATURE-----
-------------- next part --------------
Accessibility Guide
-------------------


Using Fedora with a visual, hearing, or mobility impairment


Fedora Documentation Project

Copyright © 2011-2015 Fedora Project Contributors.

The text of and illustrations in this document are licensed by Red Hat
under a Creative Commons Attribution–Share Alike 3.0 Unported license
("CC-BY-SA"). An explanation of CC-BY-SA is available at
http://creativecommons.org/licenses/by-sa/3.0/. The original authors of
this document, and Red Hat, designate the Fedora Project as the
"Attribution Party" for purposes of CC-BY-SA. In accordance with
CC-BY-SA, if you distribute this document or an adaptation of it, you
must provide the URL for the original version.

Red Hat, as the licensor of this document, waives the right to enforce,
and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent
permitted by applicable law.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix,
Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc.,
registered in the United States and other countries.

For guidelines on the permitted uses of the Fedora trademarks, refer to
https://fedoraproject.org/wiki/Legal:Trademark_guidelines.

Linux® is the registered trademark of Linus Torvalds in the United States
and other countries.

Java® is a registered trademark of Oracle and/or its affiliates.

XFS® is a trademark of Silicon Graphics International Corp. or its
subsidiaries in the United States and/or other countries.

MySQL® is a registered trademark of MySQL AB in the United States, the
European Union and other countries.

All other trademarks are the property of their respective owners.

Abstract

This document describes some of the hardware devices, applications, and
utilities available to assist people with disabilities to use a computer
with the Fedora operating system.

------------------------------------------------------------------------


1. Introduction
---------------

There are approximately 500 million people worldwide with some kind of
visual, hearing, or mobility impairment. People with disabilities often
find it extremely difficult to effectively use existing and emerging
technologies which are often designed without regard to their needs.
Websites with inaccessible content can also be problematic for screen
readers and other specialized devices used by the disabled community.

Accessible features have been voluntarily integrated into operating
systems, web interfaces, and other technologies because of marketing
potential or because it has been "the right thing to do." Equal access to
educational, professional, and recreational technologies is rapidly
becoming a legal requirement. Federal agencies in numerous countries are
formulating accessibility standards.

Specialized hardware devices, applications, and utilities are available
which considerably increase the usability of Linux for individuals with
special needs. Screen readers and magnifiers, on-screen keyboards, mouse
tools, and other tools are available for Fedora users to help make their
computer usable.


2. Why should people choose Fedora as an accessibility solution?
----------------------------------------------------------------

Linux offers an inexpensive and efficient solution for the disabled
community. Open source software costs far less compared to tools that run
on other operating systems and Linux tools are often freely downloadable.

While the Graphical User Interface (GUI) is convenient for sighted users,
it is often inhibiting to those with visual impairments because of the
difficulty speech synthesizers have interpreting graphics. Linux is a
great operating system for users with visual limitations because the GUI
is an option, not a requirement. Most modern tools including email, news,
web browsers, calendars, calculators, and much more can run on Linux
without the GUI. The working environment can also be customized to meet
the hardware or software needs of the user.

Fedora is an extremely popular Linux distribution. Most industry
professionals are familiar with Fedora, making it relatively
straightforward to find assistance if necessary.

The Fedora Project issues regular and frequent updates and enhancements,
and computers that have Fedora installed can download and install these
automatically and without cost. It is therefore easy and economical to
keep computers secure and up to date.


2.1. The Section 508 Mandate

In the United States, the Section 508 Mandate is an addendum to the
Rehabilitation Act made in 1998 that requires federal agencies to use
accessible electronic and information technologies so that people with
special needs have the same opportunities as everyone else.

For detailed information about the requirements of the Section 508
Mandate, visit http://www.section508.gov/


2.2. The Voluntary Product Accessibility Template (VPAT)

The VPAT template details how a particular product or service conforms to
Section 508 criteria. The VPAT helps federal personnel adhere to Section
508 by helping them determine whether they are buying the most accessible
IT products and services available. The VPAT template participation by
private vendors is voluntary. These templates are hosted on the
individual vendor websites. The vendors maintain their own information
and the government does not endorse this information in any way.


3. Available open source tools, utilities and drivers
-----------------------------------------------------

Current development is focusing on visual and mobility impairments. There
are both software and hardware based solutions available. There are also
both console and graphical solutions available.


3.1. Hardware

The biggest advantage of the hardware speech solutions is that speech is
available before the operating system loads, which even makes it possible
for people with a visual impairment to install the operating system.
Hardware solutions include speech synthesizers, braille terminals,
braille printers, sip and puff systems, and eye gaze pointing devices.
These devices are usually very expensive and it is difficult to find
drivers for them. Drivers are being written (mostly for speech
synthesizers) for Linux but they need to be tested and integrated by the
community into "upstream" software projects before becoming part of
Fedora.


3.2. Software

This document focuses mostly on software tools and utilities that work
with Linux. Most of these tools have been developed by the Open Source
community and many have not yet been tested by the Fedora Project.


4. Screen Readers
-----------------

Screen readers are important accessibility tools that allow a person with
limited vision to have the computer read what is on the screen. There are
numerous solutions that provide this service. This section covers some of
the ones available to Fedora users.


4.1. Orca for GNOME

GNOME supplies its own screen reader, Orca. This package is installed by
default on all Fedora systems. Additional information on Orca may be
found by visiting http://live.gnome.org/Orca/.

Enabling orca
To enable orca, if you are on the workstation image of fedora, press alt+windows+s. You will shortly hear “Screen Reader on.” Orca will start from then on until it is disabled with alt+windows+s. Should you accidentally or purposely press alt+windows+s after orca has been enabled, you will hear “screen reader off.” Orca will no longer start up automatically and must be enabled again. It can also be run manually by pressing alt+f2 to open up the run dialog and typing orca. Should orca ever crash or become unresponsive, it can be restarted either by toggling orca off then on again, or by opening up the  run dialog and typing “orca –replace”. If You are using the mate spin of fedora, press alt+windows+s. You will shortly hear “Screen Reader on.” You will then need to go into system>preferences>assistive technologies and check the box labeled “enable assistive technologies.” Be sure to press the “preferred applications” button and make sure orca is set to launch at startup. No further action is required. You can set various settings of orca such as the speech synthesizer, rate, pitch, voice, volume, punctuation level, verbosity, etc by accessing orca's preferences. This can be done from anywhere while orca is running by pressing the “orca” key plus the space bar. If you are using the desktop layout (the default) this is either the insert key on your keyboard, which is normally to the left of the home key, or the numbpad insert key, which is at the bottom of the number pad, and looks like the shift key. If you are using the laptop keyboard layout, the “orca” key is the caps lock key, which is just above shift on most keyboards. You can change the keyboard layout by accessing orca's preferences and tabbing to the keyboard layout combo box on the general tab, which is the default tab opened when the preferences are opened. If you need more help on orca, press the “help” button in orca's preferences to access the orca manual in yelp, the gnome help application. 

4.1.1. Karet navigation.

 For many gnome applications that display web content, such as the gnome web browser, the evince document reader and the gnome help application, you cannot read contents with orca until the system karet is enabled. This is a blinking cursor that follows your progress as you scroll through the text with the arrow keys. To enable karet navigation, press the f7 key. You will be asked if you wish to enable karet navigation, followed by a “do not ask me again” option which makes the selection permanent. This must only be done once. After this, orca can be used to read the contents of those applications. This is not required in most other applications. However, if orca is ever unable to read the contents of an application which contains text content, such as a web browser or text editor, try pressing f7 to see if it might be turned off. 

4.2. Jovie for KDE

Jovie is the KDE system for Text-to-Speech, previously known as ktts.
Jovie consists of a Text-to-Speech Daemon, a Konqueror plugin, and an
extension for the Kate text editor. The Daemon provides text-to-speech
functionality to applications, such as KMouth and KNotify, via D-Bus. It
also provides an icon from the system tray, for additional features. From
this tray icon, Jovie can speak the contents of a text file, speak the
contents of the clipboard, and access the control module for
configuration. Comprehensive information on jovie can be found on the KDE
website: HTTP://docs.kde.org/stable/en/kdeaccessibility/jovie/index.html

To start Jovie in Fedora, run jovie from the command line. To start it
from the KDE graphical menus, select Applications > Utilities >
Text-to-Speech.


4.3. Using Emacspeak with Fedora

Emacspeak is a speech interface that allows visually impaired users to
interact independently and efficiently with the computer. Emacspeak has
dramatically changed how hundreds of blind and visually impaired users
around the world interact with the personal computer and the Internet. A
rich suite of task-oriented speech-enabled tools provides efficient
speech-enabled access to the evolving semantic world wide web. When
combined with Linux running on low-cost PC hardware, Emacspeak provides a
reliable, stable speech-friendly solution that opens up the Internet to
visually impaired users around the world.

Emacspeak is not installed on fedora by default. To install it, open a terminal and type sudo dnf install emacspeak. Answer y when you are asked if you wish to continue. Once this is complete you can launch emacspeak by typing “emacspeak” in a terminal. If all is working properly, you should hear emacspeak start up, and report “welcome to emacspeak. I am completely operational, and all my circuits are functioning perfectly!” Before using Emacspeak, you should familiarize yourself with some
documentation. Start with A Gentle Introduction to Emacspeak by Gary
Lawrence Murphy, which is available online at
http://tldp.org/LDP/espk-ug/html/index.html

The Emacspeak HOWTO written by Jim Van Zandt is also a very good
resource, although the document is limited to the Slackware distribution.
The Emacspeak HOWTO is available online at:
http://slackware.osuosl.org/slackware-3.3/docs/Emacspeak-HOWTO

The following sections describe how to perform various tasks using
Emacspeak and Fedora.


The Meta key

At various points, the following sections refer to the Meta key. This key
is fundamental to Emacs (and therefore Emacspeak) commands, but is very
seldom found on modern keyboards. Most keyboard layouts map the Alt key
to take the place of Meta.

4.3.1. Reading news using Fedora and Emacspeak

Gnus is the news reader included with Emacspeak. Gnus gets the
appropriate data from the .newsrc file in the user's home directory. To
post and read news through Emacspeak, refer to http://www.gnus.org/ for
manuals, tutorials, HOWTOs, and more. To start Gnus, press Meta+X, then
type gnus and press Enter.

This command displays all the newsgroups you are subscribed to. To select
a newsgroup, highlight your selection and press the space bar. Next,
specify how many articles you would like to open: type a number and press
Enter. This splits the screen into two buffers. The top section is the
summary buffer, the bottom section is the article buffer. You should now
be able to read your news.

4.3.2. Sending and reading email using Fedora and Emacspeak

There are several email clients available in Emacspeak. The Gnus utility
can actually be used for both email and news. Press Meta+X to start Gnus,
then press M to use the mail client.

The easiest tool to use is RMAIL. To send a message using RMAIL, press
Ctrl+X, then type rmail. When you are in RMAIL, press M. Fill in the To:
and Subject: fields. Put the body of the message below the line that
reads -text follows this line-. To send the message when you are
finished, press Ctrl+C twice in succession.

To read a message using RMAIL, press Meta+X, then type rmail and press
Enter.

For more information on using RMAIL visit
http://www.gnu.org/software/emacs/manual/html_node/emacs/Rmail.html

4.3.3. Using Emacspeak to execute Linux shell commands

It is not necessary to leave Emacspeak to execute a Linux command. To
execute a command within Emacspeak, press Esc, then type ! followed by
the name of the command when Emacspeak prompts you. To exit the command
output window, press Ctrl+X, followed by 1

This functionality is extremely useful. You can even print and compile
files you are working on within Emacspeak. For more information on Linux
shell commands refer to Josh's Linux Guide or any other comparable
command resource.

Josh's Linux Guide is available from
http://linuxguide.sourceforge.net/linux-commands.html


5. Screen Magnifiers
--------------------

Screen magnifiers are just what they sound like, programs that
considerably magnify portions of the computer screen so it can be more
easily read.


5.1. KMagnifier

In KDE, KMagnifier, or KMag, magnifies the area around the cursor or a
user-defined area. You can also save a magnified portion of the screen to
disk. Additional information can be found at http://kmag.sourceforge.net/

5.1.1. Installing KMagnifier

In Fedora, KMagnifier is packaged in the kdeaccessibility package. This
package also contains kmousetool, kmouth, and ktts, all of which are
discussed in other areas of this guide. To install kdeaccessibility you
can either select System > Administration > Add/Remove Software and then
type in kdeaccessibility in the screen that pops up or in a terminal
window type su -c "yum install kdeaccessibility".

5.2. Magnification in gnome shell.

There is a magnifier built into the gnome shell. It can be activated in the following ways. While in gnome shell, press control+alt+tab until you hear top bar. Release the keys. You will land on the “activities” button. Press tab until you get to the “accessibility” menu.  Press The down arrow to expand and enter into this menu. Press the down arrow until you get to “zoom” and press enter. This activates the magnifier. You can change preferences of the magnifier and gnome's other built in accessibility tools by  accessing the “universal access” settings. To do this, press the windows key to open up the activities overview and start typing universal access. Highlight the “universal access”  icon and press enter. Highlight the tool who's preferences you want to change and press enter. You can also turn various tools on and off from this dialog. 

6. Mouse Tools
--------------

Mouse tools allow the mouse to be used in different ways, and provide an
alternate solution to people with limited mobility.


6.1. KMouseTool

A program for KDE, KMouseTool, provides an alternate method for clicking
the mouse by clicking the mouse whenever the cursor pauses and even
provides a dragging capability. KMouseTool works with any mouse or
pointing device.

6.1.1. Installing KMouseTool

In Fedora, KMouseTool is packaged in the kdeaccessibility package. This
package also contains kmagnifier, kmouth, and ktts, all of which are
discussed in other areas of this guide. To install kdeaccessibility you
can either select System > Administration > Add/Remove Software and then
type in kdeaccessibility in the screen that pops up, or in a terminal
window type su -c "yum install kdeaccessibility".


6.2. Mousetweaks

Similar to KDE's KMouseTool, GNOME's Mousetweaks provides functions for
simulated secondary clicks, dwell clicks, and pointer capture. Additional
information on Mousetweaks can be found at
http://library.gnome.org/users/mousetweaks/

6.2.1. Using mousetweaks. 

Mousetweaks is installed by default in the fedora workstation image. To activate the mouse tools, open the top bar by pressing and holding control+alt+tab, and pressing the tab key until you hear “top bar”. Release the keys. Press tab until you land on the “accessibility” menu. Press the down arrow to expand and enter this menu. Press the down arrow key until you land on “mouse keys” Press enter to activate. From now on, you can operate your mouse by the numbpad on your keyboard. Keys 4 and 6 move the mouse left and right, 2 and 8 move up and down, and 5 clicks. You can change various options by  accessing the “universal access” dialog in gnome's settings and pressing enter on the “mouse keys” option.

7. On_Screen_Keyboards
----------------------

Many on screen keyboards have been created for environments with no
keyboards such as wearable computers or palm devices. They are also very
useful for accessibility enhancement when used with a mouse or no-hand
tools such as a head-mouse or an eye-tracker. Some of these tools included in
Fedora are described in this section.


7.1. Indic Onscreen Keyboard

iok is Indic Onscreen Keyboard. It provides virtual keyboard
functionality. It currently works with Inscript and xkb keymaps for
Indian languages. The following keymaps are currently available:
Assamese, Bengali, Gujarati, Hindi, Kannada, Marathi, Malayalam, Punjabi,
Oriya, Tamil, Telugu. iok can even try to parse and display non-inscript
keymaps. Visit http://sourceforge.net/projects/iok/ for more information
on iok.

7.1.1. Installing iok

To install iok in fedora, you can either open up the gnome software application by pressing the windows key to open up the activities overview and typing “software”. Press enter on the software icon. In the search box, type  iok. On the results screen, press enter on the “install” button, making sure you're installing iok. After a few minutes, you will get a notification that iok has been installed. Alternatively, you can open up a terminal and type “sudo dnf install iok”, answering y when you are asked if you wish to proceed.


 7.2. Florence

Florence is an extensible, scalable, virtual keyboard, whose sole
requirement is a pointing device.

Once enabled, Florence displays an icon in the notification area on the
GNOME Panel. Florence can be sent to the background when it is not
needed, making it a practical solution for screens of all sizes. To
toggle whether Florence is displayed or hidden, just click the icon.
Alternatively, Florence can be set to autohide until an editable area is
selected. Florence can also be configured easily to be transparent,
through the Preferences dialogue. To edit all available Preferences,
right-click on the icon on the GNOME Panel, and choose Preferences from
the dropdown list.

Additional information on Florence Virtual Keyboard can be found at the
project's homepage, http://florence.sourceforge.net. Once Florence is
installed, to view full documentation right-click on the icon on the
GNOME Panel, and choose Help from the dropdown menu.

7.2.1. Installing Florence

Florence is available in the fedora package repositories; to install
either  open up the gnome software application and then type “florence” in the search box that appears, or type “sudo dnf install florence” in a terminal window.


7.3. Dasher

Dasher is an information-efficient text-entry interface, driven by
natural continuous pointing gestures. Dasher is not really a "keyboard"
but instead uses a zooming interface and a predictive language model with
word completion. Dasher makes data entry easy by people utilizing a
joystick, touchscreen, trackball, or mouse for one-handed operations. It
can also be utilized by people using no-hand tools such as a head-mouse
or an eye-tracker. Additional information on Dasher can be found at
http://library.gnome.org/users/dasher/.

7.3.1. Installing Dasher

In Fedora, Dasher can be easily installed by either  opening up the gnome software application and typing “dasher” in the search box that appears, or in a terminal window type  “sudo dnf install dasher”.

7.3.2. Gnome on screen keyboard.

Gnome shell includes it's own on screen keyboard built in. To activate it, press and hold control+alt+tab, pressing tab repeatedly until you hear “top bar”. Press tab until you land on the “accessibility” menu, and press down arrow. Press down arrow until you land on “on screen keyboard” and press enter to turn it on.

8. Help for Linux Desktops
--------------------------

Certain desktops have their own internal settings that can help with
accessibility.


8.1. KDE

In KDE, keyboard and mouse settings can be configured in kcontrol. These
settings are available by selecting Personalization > Accessibility.
Additional information on Accessibility Tools in KDE can be found at
http://accessibility.kde.org/


8.2. GNOME

The GNOME 3 Universal Access menu

In GNOME, accessibility controls can be configured in the Universal
Access menu. By selecting Activities and then typing Universal Access a
menu will display that allows tweaking of all accessibility options
within the GNOME 3 desktop environment. Additional information on GNOME's
accessibility tools can be found at
http://library.gnome.org/users/gnome-access-guide/


8.3. XFCE

In XFCE, accessibility options for the keyboard and mouse can be
configured in the Accessibility Settings dialogue. To access these
settings from the graphical menus, select Preferences > Accessibility.
Alternative keyboard configurations, such as keyboard shortcuts, can be
set by selecting Preferences > Keyboard. Similarly, extra mouse related
settings are available by selecting Preferences > Mouse. Some minor
additional accessibility options for XFCE can be found through
Preferences > Window Manager Tweaks.


8.4. Sugar: Making computing accessible for children.

The Sugar Learning Platform is an innovative learning interface for
children, which encourages learning, critical thinking, and creativity.
Sugar was originally created for the OLPC (One Laptop Per Child)
initiative. The traditional "office-desktop" style computer interface can
be quite intimidating and is often not very accessible for children who
are learning to read and write. Sugar offers an alternative, more
child-friendly approach to learning and computing.

To install the Sugar platform in fedora, you can either  open up the gnome software application and type “sugar” in the  search box that appears; or alternatively type  “sudo dnf install sugar” in a terminal. There is also an alternate version of
Fedora featuring the Sugar Platform, known as Sugar on a Stick It is
available at http://spins.fedoraproject.org/soas/

Various Sugar Activities are also available through the Fedora package
repositories. To browse the available sugar activities through the GNOME
package manager, open up the gnome software application, and then type “sugar-” in the search box that appears; you
will be presented with a list of packages relating to Sugar.
Alternatively, type “sudo dnf install sugar-” in a terminal window.

More information on Sugar for learners, parents, teachers, and
contributors can be found at the official website, http://sugarlabs.org/


A. Revision History
-------------------

Revision History

Revision 0.15-2

Sun mar 22 2015

Kendell clark <coffeekingms at gmail.com>

Altered most of the sections to include information on installing software in gnome shell, as well as updated information on how orca is started in the gnome shell.

Revision 0.15-1 

Sun Mar 23 2014

Eric Christensen

Removed text for software not in Fedora.

Updated text to remove U.S.-specific text.

Revision 0.14-1

Wed Apr 21 2010

Gerard Ryan

Fixed Revision History

Added information on Indic Onscreen Keyboard.

Added information on Florence Virtual Keyboard.

Added information on Jovie for KDE.

Added information on XFCE and Sugar Desktops.

Revision 0.13-1

Wed Apr 21 2010

Gerard Ryan

Grammar updates.

Revision 0.12-1

Mon Mar 06 2010

Joseph Allen

Updated section 4.3.2 to fix inconsistent instructions.

Revision 0.11-1

Sat Nov 28 2009

Eric Christensen

Commented out Emacspeak sections that still need work.

Changed to be the official version for Fedora 12.

Revision 0.10-1

Sat Nov 28 2009

Susan Lauber

Made some minor readability, grammar, and style edits.

Added a number of markup additions for consistency.

Added information on enabling Orca in GNOME to the Screen_Readers
section.

Added information on GNOME Magnifier to the Screen_Magnifiers section.

Moved On Screen Keyboards to their own section to clean up Other Tools.

Added information on gok (GNOME On-Screen Keyboard).

Revision 0.9-1

Sun Nov 22 2009

Eric Christensen

Added Gnome features Dasher and Caribou.

Commented out dated information on how Red Hat and Fedora had or had not
tested some of the FOSS solutions.

Revision 0.8-1

Mon Nov 09 2009

Eric Christensen

Modified the "screen readers" section.

Removed link to KMouseTools and it was broken.

Revision 0.7-1

Sun Nov 08 2009

Susan Lauber

Various style edits (tense, spelling, etc.)

Added markup for menuitems

Revision 0.6-1

Sun Nov 08 2009

Eric Christensen

Created "Mouse Tools" section, moved KMouseTools to that section, and
added Mousetweaks.

Added GNOME information in the "Desktops" section.

Added comments to Tools.xml for further editing.

Revision 0.5-1

Wed Nov 07 2009

Eric Christensen

Created "Other Tools" section and added BRLTTY, KMouth, and KMouseTool to
that section.

Created "Screen Magnifiers" section and added KMagnifier.

Created "Desktops" section and added KDE. This section will include
specific Desktop accessibility controls.

Revision 0.4-1

Wed Nov 04 2009

Eric Christensen

Combined Speakup and Emacspeak into the Screen Readers section.

Revision 0.3-1

Thu Aug 20 2009

Rüdiger Landmann

Extra XML markup.

Revision 0.2-1

Thu Aug 20 2009

Eric Christensen

Updated links and added information on Emacspeak.

Revision 0.1-1

Thu Aug 6 2009

Eric Christensen

Publicanized all information in the Accessibility Guide


More information about the docs mailing list