summaryrefslogtreecommitdiffstats
path: root/gnome2-accessibility-guide
diff options
context:
space:
mode:
authorVincent Alexander <vpalexander@src.gnome.org>2008-07-29 19:27:33 +0000
committerVincent Alexander <vpalexander@src.gnome.org>2008-07-29 19:27:33 +0000
commit4f71510a0b9a70d68394869094a13a645f675248 (patch)
tree5a046832829eacf61f385e27e716a42b4638a301 /gnome2-accessibility-guide
parente200209f01b749c62f990d4191ce31d4d78733c0 (diff)
downloadgnome-user-docs-4f71510a0b9a70d68394869094a13a645f675248.tar.gz
gnome-user-docs-4f71510a0b9a70d68394869094a13a645f675248.tar.xz
gnome-user-docs-4f71510a0b9a70d68394869094a13a645f675248.zip
corrections per willie.walker@sun.com
svn path=/trunk/; revision=926
Diffstat (limited to 'gnome2-accessibility-guide')
-rw-r--r--gnome2-accessibility-guide/C/general.xml24
-rw-r--r--gnome2-accessibility-guide/C/low-vision.xml86
-rw-r--r--gnome2-accessibility-guide/C/mobility.xml3
-rw-r--r--gnome2-accessibility-guide/C/sysadmin.xml6
4 files changed, 46 insertions, 73 deletions
diff --git a/gnome2-accessibility-guide/C/general.xml b/gnome2-accessibility-guide/C/general.xml
index 4c2990a..2406cea 100644
--- a/gnome2-accessibility-guide/C/general.xml
+++ b/gnome2-accessibility-guide/C/general.xml
@@ -88,7 +88,7 @@ Change the visual appearance of the login dialog before the user logs in; for ex
</itemizedlist>
<note>
<para>
-Ceessible login features are presently 100% functioning for Solaris only.
+Accessible login features are presently 100% functioning for Solaris only.
</para>
</note>
@@ -183,8 +183,7 @@ If you use pointing devices with switches, alternative physical keyboards, or sw
</itemizedlist>
<para>
For optimum accessibility, include
-<literal>gail</literal> and
-<literal>atk-bridge</literal>.
+<literal>gail</literal> and <literal>atk-bridge</literal>.
</para>
</listitem>
<listitem>
@@ -228,9 +227,7 @@ Restart your system.
<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:
+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>
@@ -264,17 +261,18 @@ The gestures must be contained in a single line in the <filename>AccessKeyMouseE
</note>
<section id="sysadmin-30">
-<title>Starting the Screen Reader Using a Keyboard
-Shortcut</title>
+<title>Starting the 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:
+Edit the <filename>AccessKeyMouseEvents</filename> file to associate keyboard shortcuts with assistive technologies. For example, the following lines enable you to press and hold <keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo> or <keycombo><keycap>Ctrl</keycap><keycap>M</keycap></keycombo> for one second to either start speech or magnification:
</para>
<para>
<literal>
-&lt;Control&gt;s 1 1000 10000 srcore --login
---disable-magnifier --enable-speech --enable-braille
+&lt;Control&gt;s 1 1000 10000 /usr/bin/orca -n -d main-window
+</literal>
+</para>
+<para>
+<literal>
+&lt;Control&gt;m 1 1000 10000 /usr/bin/orca -n -d main-window -e magnifier
</literal>
</para>
</section>
diff --git a/gnome2-accessibility-guide/C/low-vision.xml b/gnome2-accessibility-guide/C/low-vision.xml
index b124ade..3b929dd 100644
--- a/gnome2-accessibility-guide/C/low-vision.xml
+++ b/gnome2-accessibility-guide/C/low-vision.xml
@@ -17,7 +17,7 @@ are able to control what area of the computer screen they want enlarged, and can
<listitem>
<para>
<emphasis>Screen Reader</emphasis> - this makes on-screen information available as
-synthesized speech and/or a refreshable Braille display. They generally only translate text-based information. Graphics and other non-textual objects can be
+synthesized speech and/or a refreshable braille display. They generally only translate text-based information. Graphics and other non-textual objects can be
translated if there is alternative text
describing the item. They are also known as
blind access utilities or screen reviewers.
@@ -47,7 +47,7 @@ The <application>Orca Screen Reader and Magnifier</application> application enab
Screen Reader
</para>
<para>
-The screen reader enables non-visual access to standard applications in the GNOME Desktop by using speech and Braille output.
+The screen reader enables non-visual access to standard applications in the GNOME Desktop by using speech and braille output.
</para>
</listitem>
<listitem>
@@ -68,7 +68,7 @@ The following sections provide information about <application>Orca</application>
<section>
<title>What is Orca?</title>
<para>
-Orca is a flexible, extensible, and powerful assistive technology for people with visual impairments. Using various combinations of speech synthesis, Braille and magnification, Orca helps provide access to applications
+Orca is a flexible, extensible, and powerful assistive technology for people with visual impairments. Using various combinations of speech synthesis, braille and magnification, Orca helps provide access to applications
and toolkits that support the AT-SPI (e.g., the GNOME Desktop). <application>Orca</application> is also free open source software.
</para>
</section>
@@ -113,18 +113,18 @@ You can get in touch with developers and other users by <ulink url="mailto:orca-
</section>
<section>
-<title>Is Braille supported?</title>
+<title>Is braille supported?</title>
<para>
-Yes! Braille is supported via BrlTTY and it is tightly integrated with Orca. BrlTTY offers support for nearly every refreshable Braille display known to man. Refer to the
-<ulink url="ghelp:orca#braille">Braille page
+Yes! braille is supported via BrlTTY and it is tightly integrated with Orca. BrlTTY offers support for nearly every refreshable braille display known to man. Refer to the
+<ulink url="ghelp:orca#braille">braille page
</ulink> for more information.
</para>
</section>
<section>
-<title>Are Grade 2 Braille contractions supported?</title>
+<title>Are Grade 2 braille contractions supported?</title>
<para>
-Yes, <application>Orca</application> fully supports contracted Braille output.
+Yes, <application>Orca</application> fully supports contracted braille output.
</para>
</section>
@@ -190,10 +190,10 @@ The next item is <guilabel>Key Echo</guilabel>. This option will speak all keys
Now select your desired keyboard layout; generally, you will want to choose the layout that matches your keyboard type - 1 for Desktop or 2 for Laptop. This choice will determine what key will act as the <application>Orca</application> modifier key. The Desktop layout uses <keycap>Insert</keycap> while the Laptop layout uses <keycap>Caps Lock</keycap>. A system, host, shift or modifier key is one which is used in conjunction with other keys, enabling keyboard access to most program functions.
</para>
<para>
-Next, specify if you require Braille output. This functionality assumes a brlTTY-compatible device is available. Type <keycap>y</keycap> or <keycap>n</keycap> and press <keycap>Enter</keycap>.
+Next, specify if you require braille output. This functionality assumes a BrlTTY-compatible device is available. Type <keycap>y</keycap> or <keycap>n</keycap> and press <keycap>Enter</keycap>.
</para>
<para>
-Lastly, indicate whether you want an on-screen Braille output monitor. This is mostly for developers who need to verify brlTTY output, but may also be useful in other situations, such as visually diagnosing or verifying Braille output. Type <keycap>y</keycap> or <keycap>n</keycap> and press <keycap>Enter</keycap>.
+Lastly, indicate whether you want an on-screen braille output monitor. This is mostly for developers who need to verify BrlTTY output, but may also be useful in other situations, such as visually diagnosing or verifying braille output. Type <keycap>y</keycap> or <keycap>n</keycap> and press <keycap>Enter</keycap>.
</para>
<para>
That's it! <application>Orca</application> is now ready for use. If accessibility was not yet enabled, <application>Orca</application> does so now and asks you to logout and back in for the services to start. Type <keycap>y</keycap> and press <keycap>Enter</keycap> to restart your login session.
@@ -266,7 +266,7 @@ dialog.
</section>
<section>
-<title>Use a keyboard command to make Orca speak or Braille-output the current date and time</title>
+<title>Use a keyboard command to make Orca speak or braille-output the current date and time</title>
<para>
Place the following lines in <userinput>~/.orca/orca-customizations.py</userinput>. If this file doesn't exist yet, go ahead and create it.
</para>
@@ -326,8 +326,8 @@ Create an empty file named
<title>Orca Configuration</title>
<para>
The <application>Orca</application> configuration dialog allows you to customize
-the behavior and features of <application>Orca</application>, such as speech, Braille, and magnification. For example, you can select which speech synthesis engine you want to use, whether
-Braille is enabled or not, and which magnification preferences you want. You can select between Laptop/Desktop keyboard
+the behavior and features of <application>Orca</application>, such as speech, braille, and magnification. For example, you can select which speech synthesis engine you want to use, whether
+braille is enabled or not, and which magnification preferences you want. You can select between Laptop/Desktop keyboard
layouts and you can also examine and modify the existing keyboard layout with granular
control. To bring up the <application>Orca</application> configuration dialog, press
<keycombo><keycap>&lt;ORCA MODIFIER&gt;</keycap><keycap>Space</keycap></keycombo>, where <userinput>&lt;ORCA MODIFIER&gt;</userinput> is <keycap>Insert</keycap>
@@ -411,7 +411,7 @@ The speech page allows you to customize how <application>Orca</application> uses
<section>
<title>Enable Speech</title>
<para>
-The first control of note on the speech page is the <guilabel>Enable Speech</guilabel> check box. This check box toggles whether or not <application>Orca</application> will make use of a speech synthesizer. This option, along with the ability to enable Braille and magnifier support, allows <application>Orca</application> to be tailored to meet the specific needs of a wide variety of users.
+The first control of note on the speech page is the <guilabel>Enable Speech</guilabel> check box. This check box toggles whether or not <application>Orca</application> will make use of a speech synthesizer. This option, along with the ability to enable braille and magnifier support, allows <application>Orca</application> to be tailored to meet the specific needs of a wide variety of users.
</para>
</section>
@@ -501,32 +501,32 @@ check box is selected, <application>Orca</application> will announce any blank l
</section>
<section>
-<title>Braille Page</title>
+<title>braille Page</title>
<para>
-The Braille page allows you to customize various aspects of Braille output.
+The braille page allows you to customize various aspects of braille output.
</para>
<section>
-<title>Enable Braille Support</title>
+<title>Enable braille Support</title>
<para>
-The first control on the Braille page is the
-<guilabel>Enable Braille Support</guilabel> check box. This toggles whether or not <application>Orca</application> will make use of a Braille display. This option, along with the ability to enable Braille and magnifier support, allows <application>Orca</application> to be tailored to meet the needs of a wide variety of users. By default, this check box is enabled. If BrlTTY is not running, <application>Orca</application> will recover gracefully and will not communicate with the Braille display. If you configure BrlTTY later on, you need to restart <application>Orca</application> in
-order for it to use Braille.
+The first control on the braille page is the
+<guilabel>Enable braille Support</guilabel> check box. This toggles whether or not <application>Orca</application> will make use of a braille display. This option, along with the ability to enable braille and magnifier support, allows <application>Orca</application> to be tailored to meet the needs of a wide variety of users. By default, this check box is enabled. If BrlTTY is not running, <application>Orca</application> will recover gracefully and will not communicate with the braille display. If you configure BrlTTY later on, you need to restart <application>Orca</application> in
+order for it to use braille.
</para>
</section>
<section>
-<title>Enable Braille Monitor</title>
+<title>Enable braille Monitor</title>
<para>
-<application>Orca</application>'s Braille monitor provides an on-screen representation of what takes place on the Braille display. This feature is mostly for demonstration
-purposes, but is also useful for <application>Orca</application> developers who do not have access to a Braille display.
+<application>Orca</application>'s braille monitor provides an on-screen representation of what takes place on the braille display. This feature is mostly for demonstration
+purposes, but is also useful for <application>Orca</application> developers who do not have access to a braille display.
</para>
</section>
<section>
<title>Abbreviated Role Names</title>
<para>
-The <guilabel>Abbreviated Role Names</guilabel> check box determines the manner in which role names are displayed and can be used to help conserve real estate on the Braille display. This option is best explained by example:
+The <guilabel>Abbreviated Role Names</guilabel> check box determines the manner in which role names are displayed and can be used to help conserve real estate on the braille display. This option is best explained by example:
</para>
<para>
Let us assume that a slider had focus, and that the abbreviated role names box was not checked. In that case, the word "slider" would be shown on the display, to reflect the fact that the current control was indeed a slider. If the abbreviated role names box was checked, the word "slider" would be abbreviated to "sldr".
@@ -536,7 +536,7 @@ Let us assume that a slider had focus, and that the abbreviated role names box w
<section>
<title>Verbosity</title>
<para>
-The <guilabel>Verbosity</guilabel> radio button group determines the amount of information that will be output to Braille in certain situations. For example, if it is set to Verbose, keyboard shortcut and role name information is displayed. This information is not displayed in Brief mode.
+The <guilabel>Verbosity</guilabel> radio button group determines the amount of information that will be output to braille in certain situations. For example, if it is set to Verbose, keyboard shortcut and role name information is displayed. This information is not displayed in Brief mode.
</para>
</section>
</section>
@@ -604,7 +604,7 @@ The magnifier page allows you to enable/disable magnification and specify how ma
<section>
<title>Enable Magnifier</title>
<para>
-The first control on the magnifier page is the <guilabel>Enable Magnifier</guilabel> check box. This toggles whether or not <application>Orca</application> will provide magnification. This option, along with the ability to enable speech and Braille support, allow <application>Orca</application> to be tailored to meet the needs of a wide variety of users.
+The first control on the magnifier page is the <guilabel>Enable Magnifier</guilabel> check box. This toggles whether or not <application>Orca</application> will provide magnification. This option, along with the ability to enable speech and braille support, allow <application>Orca</application> to be tailored to meet the needs of a wide variety of users.
</para>
</section>
@@ -766,7 +766,7 @@ There is also a <guibutton>Reset</guibutton> button (<keycombo><keycap>Alt</keyc
<keycap>R</keycap></keycombo>) that will set the list values back to their initial state when the dialog was first displayed.
</para>
<para>
-When you initially display the text attribute pane, all your checked attributes are put at the top of the list. They are given in the order that they will be spoken and output to Braille.
+When you initially display the text attribute pane, all your checked attributes are put at the top of the list. They are given in the order that they will be spoken and output to braille.
</para>
<para>
If you decide to check others or wish to adjust the order, there are four buttons to help you do this:
@@ -984,10 +984,10 @@ away to some other application and then Alt-Tab back to the one that you've just
</section>
<section>
-<title>Braille</title>
+<title>braille</title>
<para>
<application>Orca</application> uses
-<ulink url='http://mielke.cc/brltty/'>BrlTTY</ulink> for Braille support. On Linux systems, BrlTTY is used to access the text mode console content. On a typical Braille-enabled installation of Linux, BrlTTY is already running and providing access to the text consoles. When Orca starts, it connects to BrlTTY. If you switch from a text console to your X Windows session, your Braille display will automatically follow and display the content that Orca is presenting to you.
+<ulink url='http://mielke.cc/brltty/'>BrlTTY</ulink> for braille support. On Linux systems, BrlTTY is used to access the text mode console content. On a typical braille-enabled installation of Linux, BrlTTY is already running and providing access to the text consoles. When Orca starts, it connects to BrlTTY. If you switch from a text console to your X Windows session, your braille display will automatically follow and display the content that Orca is presenting to you.
</para>
<para>
<application>Orca</application> attempts to work with various releases of BrlTTY. It works well with BrlTTY v3.7.2, and we've also been working with the BrlTTY team to get it going for BrlTTY v3.8. The remainder of this document provides information related to using <application>Orca</application> with <application>BrlTTY</application> 3.8.
@@ -1044,7 +1044,7 @@ symbolic link. Do so at your own risk.
<section>
<title>Keyboard Commands</title>
<para>
-This is the list of common <application>Orca</application> keyboard commands. Note that you can always enter <application>Orca</application>'s Learn mode while running <application>Orca</application> by pressing <keycombo><keycap>Insert</keycap><keycap>F1</keycap></keycombo>. When in Learn mode, <application>Orca</application> will intercept all keyboard and Braille input events and will tell you what the effect of them would be. To exit Learn mode, press the <keycombo><keycap>Escape</keycap></keycombo> key. If you are using a laptop computer, you will want to see the <ulink url="http://live.gnome.org/Orca/LaptopKeyboardCommands">laptop keyboard commands</ulink> page at live.gnome.org.
+This is the list of common <application>Orca</application> keyboard commands. Note that you can always enter <application>Orca</application>'s Learn mode while running <application>Orca</application> by pressing <keycombo><keycap>Insert</keycap><keycap>F1</keycap></keycombo>. When in Learn mode, <application>Orca</application> will intercept all keyboard and braille input events and will tell you what the effect of them would be. To exit Learn mode, press the <keycombo><keycap>Escape</keycap></keycombo> key. If you are using a laptop computer, you will want to see the <ulink url="http://live.gnome.org/Orca/LaptopKeyboardCommands">laptop keyboard commands</ulink> page at live.gnome.org.
</para>
<section>
@@ -1239,7 +1239,7 @@ application.
</para>
<note>
<para>
-In order for the next three commands to be of use, <application>Orca</application> needs to be started from a virtual console or via <application>gnome-terminal</application>. Output is sent only to the console (i.e., it is not sent to speech or Braille).
+In order for the next three commands to be of use, <application>Orca</application> needs to be started from a virtual console or via <application>gnome-terminal</application>. Output is sent only to the console (i.e., it is not sent to speech or braille).
</para>
</note>
<para>
@@ -1643,18 +1643,6 @@ Provides light text on a dark background using high-contrast colors.
<row>
<entry colname="colspec0" valign="top">
<para>
-<guilabel>LowContrast</guilabel>
-</para>
-</entry>
-<entry colname="colspec1" valign="top">
-<para>
-Uses low-contrast colors for the background and foreground text.
-</para>
-</entry>
-</row>
-<row>
-<entry colname="colspec0" valign="top">
-<para>
<guilabel>LargePrint</guilabel>
</para>
</entry>
@@ -1689,18 +1677,6 @@ Provides light text on a dark background using high-contrast colors. Increases t
</para>
</entry>
</row>
-<row>
-<entry colname="colspec0" valign="top">
-<para>
-<guilabel>LowContrastLargePrint</guilabel>
-</para>
-</entry>
-<entry colname="colspec1" valign="top">
-<para>
-Uses low-contrast colors for the background and foreground text. Increases the size of controls to accommodate larger fonts. To increase the font size, you must use the <guilabel>Font</guilabel> section.
-</para>
-</entry>
-</row>
</tbody>
</tgroup>
</table>
diff --git a/gnome2-accessibility-guide/C/mobility.xml b/gnome2-accessibility-guide/C/mobility.xml
index 3211133..7bf8ea0 100644
--- a/gnome2-accessibility-guide/C/mobility.xml
+++ b/gnome2-accessibility-guide/C/mobility.xml
@@ -44,7 +44,6 @@ that are currently running on the desktop. For example, <application>On-Screen K
</listitem>
</itemizedlist>
-
<para>
You must enable the assistive technology services before you are able to use many of the accessibility tools available.
</para>
@@ -68,7 +67,7 @@ Log back in. The assistive technology services will be started automatically.
</procedure>
<para>
-The next steps enable <application>gok</application> (GNOME Onscreen Keyboard). These steps are not necessary for Solaris and target Debian platforms (Ubuntu, etc.). See further down for rpm-based distributions (RedHat, Fedora, etc.).
+The next steps enable <application>gok</application> (GNOME Onscreen Keyboard). These steps are not necessary for Solaris (which ships with <application>gok</application> already loaded) and target Debian platforms (Ubuntu, etc.). See further down for rpm-based distributions (RedHat, Fedora, etc.).
</para>
<procedure>
<step>
diff --git a/gnome2-accessibility-guide/C/sysadmin.xml b/gnome2-accessibility-guide/C/sysadmin.xml
index 915b40b..50274a7 100644
--- a/gnome2-accessibility-guide/C/sysadmin.xml
+++ b/gnome2-accessibility-guide/C/sysadmin.xml
@@ -241,12 +241,12 @@ When you log out of your session, select the
</sect1>
<sect1 id="sysadmin-52">
-<title>Enabling Braille</title>
+<title>Enabling braille</title>
<indexterm>
-<primary>Braille, enabling</primary>
+<primary>braille, enabling</primary>
</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:
+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:
</para>
<orderedlist>
<listitem>