gnome2-accessibility-guide/C/ats.xml

2007-09-20  Joachim Noreiko  <jnoreiko@yahoo.com>

	* gnome2-accessibility-guide/C/ats.xml
	* gnome2-accessibility-guide/C/dtconfig.xml
	* gnome2-accessibility-guide/C/keynav.xml
	* gnome2-accessibility-guide/C/themes.xml:
	  removed
	* gnome2-accessibility-guide/C/enable.xml
	* gnome2-accessibility-guide/C/general.xml
	* gnome2-accessibility-guide/C/low-vision.xml
	* gnome2-accessibility-guide/C/mobility.xml:
	  added
	* gnome2-accessibility-guide/C/accessintro.xml
	* gnome2-accessibility-guide/C/gnome-access-guide.xml
	* gnome2-accessibility-guide/C/sysadmin.xml:
	  Rearranged the different accessibility technologies by 
	  the different type of disability they apply to.
	  #475110 Patch from Ubuntu documentation team
	* Makefile.am: done the necessary changes for removed & new files

svn path=/trunk/; revision=757

5 files changed, 45 insertions, 655 deletions

diff --git a/gnome2-accessibility-guide/C/ChangeLog b/gnome2-accessibility-guide/C/ChangeLog
index 7b11828..a18e490 100644
--- a/gnome2-accessibility-guide/C/ChangeLog
+++ b/gnome2-accessibility-guide/C/ChangeLog
@@ -1,3 +1,23 @@
+2007-09-20  Joachim Noreiko  <jnoreiko@yahoo.com>
+
+	* gnome2-accessibility-guide/C/ats.xml
+	* gnome2-accessibility-guide/C/dtconfig.xml
+	* gnome2-accessibility-guide/C/keynav.xml
+	* gnome2-accessibility-guide/C/themes.xml:
+	  removed
+	* gnome2-accessibility-guide/C/enable.xml
+	* gnome2-accessibility-guide/C/general.xml
+	* gnome2-accessibility-guide/C/low-vision.xml
+	* gnome2-accessibility-guide/C/mobility.xml:
+	  added
+	* gnome2-accessibility-guide/C/accessintro.xml
+	* gnome2-accessibility-guide/C/gnome-access-guide.xml
+	* gnome2-accessibility-guide/C/sysadmin.xml:
+	  Rearranged the different accessibility technologies by 
+	  the different type of disability they apply to.
+	  #475110 Patch from Ubuntu documentation team
+	* Makefile.am: done the necessary changes for removed & new files
+
 2006-08-18  Don Scorgie  <dscorgie@cvs.gnome.org>
 
 	* gnome-access-guide.xml: 
diff --git a/gnome2-accessibility-guide/C/accessintro.xml b/gnome2-accessibility-guide/C/accessintro.xml
index 30ceb8b..e5bd65e 100644
--- a/gnome2-accessibility-guide/C/accessintro.xml
+++ b/gnome2-accessibility-guide/C/accessintro.xml
@@ -1,12 +1,10 @@
 <chapter id="accessintro-1">
 <title>Introduction to Accessibility</title>
-<para>This chapter introduces you to accessibility in the GNOME
-Desktop.</para>
-<sect1 id="accessintro-2">
-<title>Overview of Accessibility</title>
 <indexterm>
 <primary>Section 508</primary>
 </indexterm>
+<para>This chapter introduces you to accessibility in the GNOME
+Desktop.</para>
 <para>All software products
 should incorporate accessibility features to enable people with disabilities
 to use the software easily and efficiently. Recent legislation such as Section
@@ -21,5 +19,4 @@ the desktop.</para>
 <para>The ability to easily customize the GNOME Desktop contributes greatly to the accessibility of the desktop.
 This guide describes the various customization options that you can use to
 tailor the desktop to suit your particular needs.</para>
-</sect1>
 </chapter>
diff --git a/gnome2-accessibility-guide/C/gnome-access-guide.xml b/gnome2-accessibility-guide/C/gnome-access-guide.xml
index da0f680..cc562b4 100644
--- a/gnome2-accessibility-guide/C/gnome-access-guide.xml
+++ b/gnome2-accessibility-guide/C/gnome-access-guide.xml
@@ -5,16 +5,17 @@
   <!ENTITY manrevision "2.14.0">
   <!ENTITY date "February 2006">
   <!ENTITY LEGAL SYSTEM "legal.xml">
-  <!ENTITY dtconfig SYSTEM "dtconfig.xml">
-  <!ENTITY keynav SYSTEM "keynav.xml">  
-  <!ENTITY themes SYSTEM "themes.xml">  
-  <!ENTITY preface SYSTEM "preface.xml">
   <!ENTITY accessintro SYSTEM "accessintro.xml">
   <!ENTITY sysadmin SYSTEM "sysadmin.xml">
-  <!ENTITY ats SYSTEM "ats.xml">
+  <!ENTITY enable SYSTEM "enable.xml">
+  <!ENTITY low-vision SYSTEM "low-vision.xml">
+  <!ENTITY mobility SYSTEM "mobility.xml">
+  <!ENTITY general SYSTEM "general.xml">
   <!ENTITY author1 "Sun">
   <!ENTITY author2 "Java Desktop System Documentation Team">
 ]>
+<?db.chunk.max_depth 4?>
+<?yelp:chunk-depth 4?>
 <book id="index"> 
   <title>GNOME &gnomeversion; Desktop Accessibility Guide</title> 
   <bookinfo> 
@@ -156,13 +157,15 @@
 	  type="help">GNOME Feedback Page</ulink>. </para>
 	 </legalnotice> 
   </bookinfo>
-&preface;
 &accessintro;
-&dtconfig;
-&keynav;
-&themes;
-&ats;
+&enable;
+&general;
+&low-vision;
+&mobility;
+
+<!--
 &sysadmin;
+-->
 
 <!-- If generating PDFs and if you want an index, then uncomment <index/> -->
 <!-- <index/> -->
diff --git a/gnome2-accessibility-guide/C/sysadmin.xml b/gnome2-accessibility-guide/C/sysadmin.xml
index a310f57..587a7fc 100644
--- a/gnome2-accessibility-guide/C/sysadmin.xml
+++ b/gnome2-accessibility-guide/C/sysadmin.xml
@@ -5,523 +5,6 @@
 describes some tasks that a system administrator needs to perform to enable
 accessible login and to facilitate the use of the assistive technologies that
 are available in the GNOME Desktop.</para>
-<sect1 id="sysadmin-27">
-<title>Configuring the Desktop for Accessible Login</title>
-<indexterm>
-<primary>accessible login feature</primary>
-</indexterm>
-<para>The GNOME Desktop includes an Accessible
-Login feature. The Accessible Login feature enables users to: </para>
-<itemizedlist>
-<listitem>
-<para>Log in to the desktop even if the user cannot easily use the
-screen, mouse, or keyboard in the usual way.</para>
-</listitem>
-<listitem>
-<para>Launch assistive technologies at login time by associating
-a user action with an assistive technology application. The user can perform
-the user action from the standard keyboard, or from a keyboard, pointing device,
-or switch device that is attached to the USB or PS/2 mouse port. These user
-actions are called gestures.</para>
-</listitem>
-<listitem>
-<para>Change the visual appearance of the login dialog before the
-user logs in, for example, to use a high contrast theme for better visibility. </para>
-</listitem>
-</itemizedlist>
-<sect2 id="sysadmin-34">
-<title>To Enable Accessible Login</title>
-<indexterm>
-<primary>GDM</primary>
-</indexterm>
-<para>To enable the Accessible
-Login feature for the GNOME
-Desktop, you must configure the desktop to use the GNOME Display Manager
-(GDM) as the login manager. GDM is the default login manager on Linux systems
-but not on Solaris systems, therefore the instructions to enable Accessible
-Login differ depending on the platform you are using. </para>
-<sect3 id="sysadmin-38">
-<title>To Enable and Configure GDM on Solaris Systems</title>
-<para>To enable and configure GDM as the login manager on Solaris systems,
-perform the following steps:</para>
-<orderedlist>
-<listitem>
-<para>Log in as the <literal>root</literal> user.</para>
-</listitem>
-<listitem>
-<para>Open the file <filename>/etc/X11/gdm/gdm.conf</filename>.</para>
-</listitem>
-<listitem>
-<para>Search the file for the following line: </para>
-<para>
-<literal>#AddGtkModules=false</literal>
-</para>
-<para>and replace the line with the following:</para>
-<para>
-<literal>AddGtkModules=true</literal>
-</para>
-<para>This step enables the GtkModules.</para>
-</listitem>
-<listitem>
-<para>Search the file for the following line: </para>
-<para>
-<literal>#GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener</literal>
-</para>
-<para>and delete the <literal>#</literal> from the start of the line so that
-the line reads:</para>
-<para>
-<literal>GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener</literal>
-</para>
-<note>
-<para>The above lines must be displayed as single lines in the <filename>gdm.conf</filename> file without line breaks. The formatting of this guide
-may display the lines over two lines.</para>
-</note>
-<para>This step loads all of the GtkModules to enable assistive technologies
-such as <application>On-Screen Keyboard</application> and <application>Screen
-Reader and Magnifier</application>. You can edit the line above further to
-load only the GtkModules that you require to support the user base. For example: </para>
-<itemizedlist>
-<listitem>
-<para>If you need to use the <application>Screen Reader and Magnifier</application>, include <literal>gail</literal> and <literal>atk-bridge</literal>.</para>
-</listitem>
-<listitem>
-<para>If you need to use a pointing device without buttons or switches,
-include <literal>gail</literal>, <literal>atk-bridge</literal>, and<literal>dwellmouselistener</literal>. </para>
-</listitem>
-<listitem>
-<para>If you use pointing devices with switches, alternative physical
-keyboards, or switch and button devices, include <literal>keymouselistener</literal>.</para>
-</listitem>
-<listitem>
-<para><application>On-Screen Keyboard</application> can operate
-without <literal>gail</literal> and <literal>atk-bridge</literal> but with
-a reduced feature set. </para>
-</listitem>
-</itemizedlist>
-<para>For optimum accessibility, include <literal>gail</literal> and <literal>atk-bridge</literal>.</para>
-</listitem>
-<listitem>
-<para>Save the <filename>/etc/X11/gdm/gdm.conf</filename> file.</para>
-</listitem>
-<listitem>
-<para>Enter the following command to stop the <application>dtlogin</application> manager:</para>
-<para>
-<command>/usr/dt/bin/dtconfig -d</command>
-</para>
-</listitem>
-<listitem>
-<para>Enter the following commands to configure GDM as the login
-manager:</para>
-<para>
-<command>svccfg import /var/svc/manifest/application/gdm2-login.xml</command>
-</para>
-<para>
-<command>svcadm enable application/gdm2-login</command>
-</para>
-<note>
-<para>If you make any changes to the <filename>/etc/X11/gdm/gdm.conf</filename> file after you enable GDM, you can execute the following command
-to restart GDM and activate the changes:</para>
-<para>
-<command>gdm-restart</command>
-</para>
-</note>
-</listitem>
-<listitem>
-<para>Edit the file <filename>/etc/passwd</filename> to append the
-following to the end of the <literal>gdm</literal> line:</para>
-<para>
-<literal>:/etc/X11/gdm/home</literal>
-</para>
-</listitem>
-<listitem>
-<para>Create the <literal>/etc/X11/gdm/home</literal> directory
-and assign ownership of the directory to the <literal>gdm</literal> user.</para>
-</listitem>
-<listitem>
-<para>Restart your system.</para>
-</listitem>
-</orderedlist>
-</sect3>
-<sect3 id="sysadmin-39">
-<title>To Configure GDM on Linux Systems</title>
-<para>To configure GDM on Linux systems, perform the following steps:</para>
-<orderedlist>
-<listitem>
-<para>Log in as the <literal>root</literal> user.</para>
-</listitem>
-<listitem>
-<para>Open the file <filename>/etc/X11/gdm/gdm.conf</filename>.</para>
-</listitem>
-<listitem>
-<para>Search the file for the following line: </para>
-<para>
-<literal>#AddGtkModules=false</literal>
-</para>
-<para>and replace the line with the following:</para>
-<para>
-<literal>AddGtkModules=true</literal>
-</para>
-<para>This step enables the GtkModules.</para>
-</listitem>
-<listitem>
-<para>Search the file for the following line: </para>
-<para>
-<literal>#GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener</literal>
-</para>
-<para>and delete the <literal>#</literal> from the start of the line so that
-the line reads:</para>
-<para>
-<literal>GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener</literal>
-</para>
-<note>
-<para>The above lines must be displayed as single lines in the <filename>gdm.conf</filename> file without line breaks. The formatting of this guide
-may display the lines over two lines.</para>
-</note>
-<para>This step loads all of the GtkModules to enable assistive technologies
-such as <application>On-Screen Keyboard</application> and <application>Screen
-Reader and Magnifier</application>. You can edit the line above further to
-load only the GtkModules that you require to support the user base. For example: </para>
-<itemizedlist>
-<listitem>
-<para>If you need to use the <application>Screen Reader and Magnifier</application>, include <literal>gail</literal> and <literal>atk-bridge</literal>.</para>
-</listitem>
-<listitem>
-<para>If you need to use a pointing device without buttons or switches,
-include <literal>gail</literal>, <literal>atk-bridge</literal>, and <literal>dwellmouselistener</literal>. </para>
-</listitem>
-<listitem>
-<para>If you use pointing devices with switches, alternative physical
-keyboards, or switch and button devices, include <literal>keymouselistener</literal>.</para>
-</listitem>
-<listitem>
-<para><application>On-Screen Keyboard</application> can operate
-without <literal>gail</literal> and <literal>atk-bridge</literal> but with
-a reduced feature set. </para>
-</listitem>
-</itemizedlist>
-<para>For optimum accessibility, include <literal>gail</literal> and <literal>atk-bridge</literal>.</para>
-</listitem>
-<listitem>
-<para>Save the <filename>/etc/X11/gdm/gdm.conf</filename> file.</para>
-<note>
-<para>If you make any changes to the <filename>/etc/X11/gdm/gdm.conf</filename> file after you enable GDM, you can execute the following command
-to restart GDM and activate the changes:</para>
-<para>
-<command>gdm-restart</command>
-</para>
-</note>
-</listitem>
-<listitem>
-<para>Edit the file <filename>/etc/group</filename> and append the
-following to the <literal>audio</literal> line:</para>
-<para>
-<literal>,gdm</literal>
-</para>
-<para>This step ensures that speech works with GDM.</para>
-</listitem>
-<listitem>
-<para>Restart your system.</para>
-</listitem>
-</orderedlist>
-</sect3>
-</sect2>
-<sect2 id="sysadmin-29">
-<title>To Start Assistive Technologies at Login</title>
-<indexterm>
-<primary>gestures</primary>
-</indexterm>
-<para>If you load the <literal>keymouselistener</literal> and <literal>dwellmouselistener</literal> GtkModules
-in the GDM configuration file, you can assign user actions to launch specific
-assistive technologies at login time. These user actions are called gestures.
-The gesture associations are contained in the following GDM configuration
-files: </para>
-<itemizedlist>
-<listitem>
-<para>
-<filename>/etc/X11/gdm/modules/AccessKeyMouseEvents</filename>
-</para>
-</listitem>
-<listitem>
-<para>
-<filename>/etc/X11/gdm/modules/AccessDwellMouseEvents</filename>
-</para>
-</listitem>
-</itemizedlist>
-<note>
-<para>If you modify these files, you must restart your system before
-the changes take effect.</para>
-</note>
-<para>The following sections contain examples of the gestures that you can
-add to the GDM configuration files.</para>
-<note>
-<para>The gestures must be contained in a single line in the <filename>AccessKeyMouseEvents</filename> file without line breaks. The formatting of
-this guide might display the examples in the following sections over two lines. </para>
-</note>
-<sect3 id="sysadmin-30">
-<title>To Start Screen Reader Using a Keyboard Shortcut</title>
-<para>Edit the <filename>AccessKeyMouseEvents</filename> file to associate
-keyboard shortcuts with assistive technologies. For example, the following
-line enables you to press-and-hold <keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo>
-for one second to start <application>Screen Reader and Magnifier</application>
-in speech and Braille mode:</para>
-<para>
-<emphasis>Solaris:</emphasis>
-</para>
-<para>
-<literal>&lt;Control&gt;s 1 1000 10000 /usr/sfw/bin/srcore --login --disable-magnifier
---enable-speech --enable-braille</literal>
-</para>
-<para>
-<emphasis>Linux:</emphasis>
-</para>
-<para>
-<literal>&lt;Control&gt;s 1 1000 10000 srcore --login --disable-magnifier
---enable-speech --enable-braille</literal>
-</para>
-</sect3>
-<sect3 id="sysadmin-41">
-<title>To Start Magnifier Using a Keyboard Shortcut</title>
-<para>Edit the <filename>AccessKeyMouseEvents</filename> file to associate
-keyboard shortcuts with assistive technologies. For example, the following
-line enables you to press-and-hold <keycombo><keycap>Ctrl</keycap><keycap>M</keycap></keycombo>
-for one second to start <application>Screen Reader and Magnifier</application>
-in magnifier mode:</para>
-<para>
-<emphasis>Solaris:</emphasis>
-</para>
-<para>
-<literal>&lt;Control&gt;m 1 1000 10000 /usr/sfw/bin/srcore --login --enable-magnifier
---disable-speech</literal>
-</para>
-<para>
-<emphasis>Linux:</emphasis>
-</para>
-<para>
-<literal>&lt;Control&gt;m 1 1000 10000 srcore --login --enable-magnifier
---disable-speech</literal>
-</para>
-</sect3>
-<sect3 id="sysadmin-31">
-<title>To Start On-Screen Keyboard Using a Switch or Button Gesture</title>
-<para>Edit the <filename>AccessKeyMouseEvents</filename> file to associate
-switch, key, or button gestures with assistive technologies. Since the primary
-input device for many <application>On-Screen Keyboard</application> users
-is a switch or button, this is a good way to enable users to start <application>On-Screen Keyboard</application> at login time. </para>
-<para>If there is a tendency for a user to start an application unintentionally,
-you can associate the gestures with multiple switch presses or minimum durations.
-For example, the following line starts <application>On-Screen Keyboard</application>
-in inverse scanning mode when the user presses the switch that is defined
-as Switch 2 three times within two seconds, for a minimum of 100 milliseconds
-for each press:</para>
-<para>
-<emphasis>Solaris:</emphasis>
-</para>
-<para>
-<literal>&lt;Switch2&gt;3 100 2000 /usr/sfw/bin/gok --login --accessmethod=inversescanning
---scan-action=switch1 --select-action=switch2</literal>
-</para>
-<para>
-<emphasis>Linux:</emphasis>
-</para>
-<para>
-<literal>&lt;Switch2&gt;3 100 2000 gok --login --accessmethod=inversescanning
---scan-action=switch1 --select-action=switch2</literal>
-</para>
-<para>Users who use single switches may prefer to start <application>On-Screen
-Keyboard</application> in automatic scanning mode. The following line starts <application>On-Screen Keyboard</application> in automatic scanning mode when the user
-presses the switch on an alternative access device for more than four seconds:</para>
-<para>
-<emphasis>Solaris:</emphasis>
-</para>
-<para>
-<literal>&lt;Switch&gt;1 4000 5000 /usr/sfw/bin/gok --login --accessmethod=automaticscanning
---scan-action=switch1 --select-action=switch1</literal>
-</para>
-<para>
-<emphasis>Linux:</emphasis>
-</para>
-<para>
-<literal>&lt;Switch&gt;1 4000 5000 gok --login --accessmethod=automaticscanning
---scan-action=switch1 --select-action=switch1</literal>
-</para>
-<para>For information about the <application>On-Screen Keyboard</application>
-operating modes, see the online Help for <application>On-Screen Keyboard</application>.</para>
-</sect3>
-<sect3 id="sysadmin-32">
-<title>To Start On-Screen Keyboard Using a Motion-only Gesture</title>
-<para>You can define gestures that involve only the motion of a pointing device
-such as a mouse, or an alternative pointing device, such as a head pointer
-or trackball. The syntax of the gesture does not change depending on whether
-you are using a mouse or an alternative pointing device. Edit the <filename>AccessKeyMouseEvents</filename> file to associate motion gestures with assistive
-technologies.</para>
-<para>If the <literal>dwellmouselistener</literal> GtkModule is loaded, alternative
-pointing devices are temporarily latched to the core pointer. This means that
-if the user moves the alternative pointing device, the onscreen pointer moves.</para>
-<para>For example, the following line starts <application>On-Screen Keyboard</application> in dwell mode when the user moves the onscreen pointer from
-inside the login dialog through the top edge, back into the dialog through
-the top edge, out of the dialog through the left edge, back into the dialog
-through the left edge, and similarly through the bottom and right edges of
-the dialog in a cross pattern:</para>
-<para>
-<emphasis>Solaris:</emphasis>
-</para>
-<para>
-<literal>TTLLBBRR O 10000 /usr/sfw/bin/gok --login --access-method=dwellselection
---input-device=MOUSE[3]</literal>
-</para>
-<para>
-<emphasis>Linux:</emphasis>
-</para>
-<para>
-<literal>TTLLBBRR O 10000 gok --login --access-method=dwellselection
---input-device=MOUSE[3]</literal>
-</para>
-<para>Note that the <literal>--input-device</literal> parameter specified
-in the gesture must match the name of the extended user input device, such
-as a head pointer or trackball, as specified in <filename>/etc/X11/XF86Config</filename>.</para>
-</sect3>
-</sect2>
-<sect2 id="sysadmin-33">
-<title>Additional Requirements for Accessible Login</title>
-<para>To enable the Accessible Login feature to use alternative pointing devices
-and switch devices such as sip-and-puff switches, wheelchair-mounted switches,
-or trackballs, you might need to modify your X server system configuration
-to recognize these devices. You can use most devices that emulate mouse buttons
-with the Accessible Login feature and <application>On-Screen Keyboard</application>,
-including USB single switches and mouse-like pointing devices.</para>
-<note>
-<para>You should not configure an alternative input device to control
-the primary onscreen pointer. This might result in undesirable behavior or
-cause situations from which the user of the alternate input device cannot
-recover without using the primary keyboard or mouse. To prevent this problem,
-please remove any occurrences of the attributes <literal>SendCore</literal>
-or <literal>AlwaysCore</literal> from any of <literal>InputDevice</literal>
-lines in the X Server configuration file.</para>
-</note>
-</sect2>
-</sect1>
-<sect1 id="sysadmin-7">
-<title>Configuring the Java Environment for Accessibility on Solaris Systems</title>
-<indexterm>
-<primary>Java environment, configuring</primary>
-</indexterm>
-<para>To configure the Java environment on Solaris systems for accessibility, perform
-the following steps:</para>
-<orderedlist>
-<listitem>
-<para>Log in as the <literal>root</literal> user to the base directory
-of the Java SDK installation. </para>
-</listitem>
-<listitem>
-<para>Enter the following command:</para>
-<para>
-<command>cd jre/lib</command>
-</para>
-</listitem>
-<listitem>
-<para>Enter the following command:</para>
-<para>
-<command>ln -s /usr/share/jar/accessibility.properties</command>
-</para>
-</listitem>
-<listitem>
-<para>Enter the following command:</para>
-<para>
-<command>cd ext</command>
-</para>
-</listitem>
-<listitem>
-<para>Enter the following command: </para>
-<para>
-<command>ln -s /usr/share/jar/gnome-java-bridge.jar</command>
-</para>
-</listitem>
-</orderedlist>
-</sect1>
-<sect1 id="sysadmin-55">
-<title>Enabling XKB on Solaris Systems</title>
-<indexterm>
-<primary>XKB</primary>
-</indexterm>
-<para>If you are using the desktop
-for the Solaris operating system on a SPARC platform, you must enable XKB
-on your system before you can use the <application>AccessX</application> preference
-tool, <application>Screen Reader and Magnifier</application>, or <application>On-Screen Keyboard</application>. </para>
-<note>
-<para>XKB is not currently supported on Sun Ray systems.</para>
-</note>
-<para>To enable XKB on a non-Sun Ray Solaris system, perform the following
-steps:</para>
-<orderedlist>
-<listitem>
-<para>Log in as the <literal>root</literal> user.</para>
-</listitem>
-<listitem>
-<para>Check if the path and file <filename>/etc/dt/config/Xservers</filename> exists on your system.</para>
-</listitem>
-<listitem>
-<para>If the <filename>/etc/dt/config</filename> directory does
-not exist, enter the following command:</para>
-<screen>
-<command>mkdir -p /etc/dt/config</command>
-</screen>
-</listitem>
-<listitem>
-<para>If the <filename>Xservers</filename> file is not present,
-enter the following command:</para>
-<screen>
-<command>cp /usr/dt/config/Xservers /etc/dt/config/Xservers</command>
-</screen>
-</listitem>
-<listitem>
-<para>Open the <filename>Xservers</filename> file in a text editor
-and scroll to the end of the file. </para>
-</listitem>
-<listitem>
-<para>Append the following to the command line at the end of the
-file:</para>
-<screen>
-<userinput>+kb</userinput>
-</screen>
-</listitem>
-<listitem>
-<para>Save and close the <filename>Xservers</filename> file.</para>
-</listitem>
-<listitem>
-<para>Enter the following command at a command line:</para>
-<screen>
-<command>pkill -HUP dtlogin</command>
-</screen>
-</listitem>
-<listitem>
-<para>Open the <filename>/etc/X11/gdm/gdm.conf</filename> file in
-a text editor.</para>
-</listitem>
-<listitem>
-<para>Scroll towards the end of the file until you see the line <literal>[server - standard]</literal>.</para>
-</listitem>
-<listitem>
-<para>Edit the <literal>command</literal> line in this section to
-append the following to the end of the line:</para>
-<para>
-<command>+accessx +kb</command>
-</para>
-</listitem>
-<listitem>
-<para>Save and close the <filename>gdm.conf</filename> file.</para>
-</listitem>
-<listitem>
-<para>Log out of your session and log in again.</para>
-</listitem>
-<listitem>
-<para>To verify if XKB is running, execute the following command: </para>
-<para>
-<command>xdpyinfo</command>
-</para>
-<para>then search for XKEYBOARD in the extensions list.</para>
-</listitem>
-</orderedlist>
-</sect1>
 <sect1 id="sysadmin-6">
 <title>Enabling Full Screen Magnification</title>
 <indexterm>
@@ -697,43 +180,7 @@ current setup</guilabel> option. </para>
 </indexterm>
 <para>To enable
 your system to support Braille output, you must configure the access rights
-to the serial port to which the Braille device is connected. The following
-sections describe the steps that you need to perform depending on your operating
-system.</para>
-<sect2 id="sysadmin-53">
-<title>To Enable Braille on Solaris Systems</title>
-<para>To configure the serial port to which the Braille device is connected
-on Solaris systems, perform the following steps:</para>
-<orderedlist>
-<listitem>
-<para>Log in as the <literal>root</literal> user.</para>
-</listitem>
-<listitem>
-<para>Enter the following command:</para>
-<para>
-<command>chmod 777 /dev/cua/a</command>
-</para>
-</listitem>
-<listitem>
-<para>Enter the following command:</para>
-<para>
-<command>chmod 777 /dev/cua/b</command>
-</para>
-</listitem>
-<listitem>
-<para>Change the permissions to <literal>777</literal> on the devices
-to which the symbolic links <literal>/dev/cua/a</literal> and <literal>/dev/cua/b</literal> point. </para>
-</listitem>
-</orderedlist>
-<note>
-<para>If your system uses <command>/dev/cua/a</command> for system log
-messages, Braille will not work on that serial port. Use <command>/dev/cua/b</command> instead.</para>
-</note>
-</sect2>
-<sect2 id="sysadmin-54">
-<title>To Enable Braille on Linux Systems</title>
-<para>To configure the serial port to which the Braille device is connected
-on Linux systems, perform the following steps:</para>
+to the serial port to which the Braille device is connected. To do that:</para>
 <orderedlist>
 <listitem>
 <para>Log in as the <literal>root</literal> user.</para>
@@ -751,96 +198,20 @@ on Linux systems, perform the following steps:</para>
 </para>
 </listitem>
 </orderedlist>
-</sect2>
 </sect1>
 <sect1 id="sysadmin-37">
 <title>Configuring Alternative Pointer Devices</title>
-<para>The following sections describe how to configure your system to use
-a standard physical mouse and another pointer device such as a single switch
-device or head tracker device, and how to configure <application>On-Screen
-Keyboard</application> to use the second pointer device.</para>
-<sect2 id="sysadmin-45">
-<title>To Configure Alternative Pointer Devices on Solaris Systems</title>
-<indexterm>
-<primary>configuring two pointer devices</primary>
-<secondary>on
-Solaris systems</secondary>
-</indexterm>
-<para>To configure an alternative pointer
-device on a Solaris system, perform the following steps:</para>
-<note>
-<para>This procedure does not work on all Solaris platforms.</para>
-</note>
-<orderedlist>
-<listitem>
-<para>Before you connect the alternative pointer device to your
-system, enter the following command to list the existing devices:</para>
-<para>
-<command>ls -l /dev/usb/hid*</command>
-</para>
-</listitem>
-<listitem>
-<para>Connect the alternative pointer device to your system.</para>
-</listitem>
-<listitem>
-<para>Enter the following command again to list the new device:</para>
-<para>
-<command>ls -l /dev/usb/hid*</command>
-</para>
-</listitem>
-<listitem>
-<para>Open the file <filename>/usr/openwin/server/etc/OWconfig</filename>.</para>
-</listitem>
-<listitem>
-<para>Add the following lines to the <filename>OWconfig</filename>
-file:</para>
-<para>
-<literallayout># Sun Mouse module
-class=&quot;XINPUT&quot; name=&quot;IMOUSE2&quot;
-dev=&quot;/dev/usb/hid2&quot; strmod=&quot;usbms&quot;
-ddxHandler=&quot;ddxSUNWmouse.so.1&quot;
-ddxInitFunc=&quot;ddxSUNWmouseProc&quot;;</literallayout>
-</para>
-<para>where:</para>
-<itemizedlist>
-<listitem>
-<para>the <literal>name</literal> option starts with the string <literal>IMOUSE</literal> but is extended to form a unique string, such as <literal>IMOUSE2</literal> or <literal>IMOUSE3</literal>, depending on the number of
-existing devices.</para>
-</listitem>
-<listitem>
-<para>the <literal>dev</literal> option specifies the device name
-that you identified in Step 3.</para>
-</listitem>
-</itemizedlist>
-</listitem>
-<listitem>
-<para>Remove the following lines from the <filename>OWconfig</filename>
-file:</para>
-<para>
-<literallayout># Null Mouse module
-class=&quot;XINPUT&quot; name=&quot;NMOUSE&quot;
-ddxHandler=&quot;ddxSUNWmouse.so.1&quot;
-ddxInitFunc=&quot;ddxnullmouseProc&quot;;</literallayout>
-</para>
-</listitem>
-<listitem>
-<para>Save the <filename>/usr/openwin/server/etc/OWconfig</filename>
-file.</para>
-</listitem>
-<listitem>
-<para>Restart the X Server. </para>
-</listitem>
-</orderedlist>
-</sect2>
-<sect2 id="sysadmin-46">
-<title>To Configure Alternative Pointer Devices on Linux Systems</title>
 <indexterm>
 <primary>configuring two pointer devices</primary>
 <secondary>on
 Linux systems</secondary>
 </indexterm>
+<para>The following sections describe how to configure your system to use
+a standard physical mouse and another pointer device such as a single switch
+device or head tracker device, and how to configure <application>On-Screen
+Keyboard</application> to use the second pointer device.</para>
 <para>To configure an alternative pointer
-device on a Linux system, perform the following steps:</para>
+device, perform the following steps:</para>
 <orderedlist>
 <listitem>
 <para>Before you connect the alternative pointer device to your
@@ -934,7 +305,6 @@ or <literal>AlwaysCore</literal> attributes.</para>
 <para>Restart the X Server.</para>
 </listitem>
 </orderedlist>
-</sect2>
 <sect2 id="sysadmin-47">
 <title>To Configure On-Screen Keyboard to Use an Alternative Pointer Device</title>
 <indexterm>
diff --git a/gnome2-accessibility-guide/Makefile.am b/gnome2-accessibility-guide/Makefile.am
index 643f11e..b9767bb 100644
--- a/gnome2-accessibility-guide/Makefile.am
+++ b/gnome2-accessibility-guide/Makefile.am
@@ -4,12 +4,12 @@ dist-hook: doc-dist-hook
 DOC_MODULE = gnome-access-guide
 DOC_ENTITIES =			\
 	accessintro.xml		\
-	ats.xml			\
-	dtconfig.xml		\
-	keynav.xml		\
 	preface.xml		\
 	sysadmin.xml		\
-	themes.xml		\
+	enable.xml  \
+	general.xml \
+	low-vision.xml  \
+	mobility.xml	\
 	legal.xml
 
 DOC_LINGUAS = de el en_GB es fr it pt sv