Development/Tutorials/Accessibility - Revision history

Frederik.gladhorn: /* Screen Reader */

2012-01-21T00:52:43Z

‎Screen Reader

2012-01-21T00:45:49Z

‎Screen Reader

2012-01-21T00:45:28Z

‎Screen Reader

2012-01-21T00:38:28Z

2012-01-20T23:51:39Z

2011-02-25T16:43:08Z

2011-02-07T14:38:55Z

‎How to test at-spi2 with gtk

2010-11-11T01:12:08Z

‎Qt AT-SPI

2010-11-11T01:05:18Z

‎Qt AT-SPI

2010-11-11T00:58:34Z

‎QAccessible

@@ Line 3: / Line 3: @@
 == Screen Reader ==
-;[http://userbase.kde.org/Accessibility|Accessibility Documentation for Users on userbase.kde.org]
+;[http://userbase.kde.org/Accessibility Accessibility Documentation for Users on userbase.kde.org]
 :''Explains how to get started with screen readers as a user.''

@@ Line 3: / Line 3: @@
 == Screen Reader ==
-;[http://userbase.kde.org/Accessibility|Accessibility Documentation for Users]
+;[http://userbase.kde.org/Accessibility|Accessibility Documentation for Users on userbase.kde.org]
 :''Explains how to get started with screen readers as a user.''

@@ Line 3: / Line 3: @@
 == Screen Reader ==
+;[http://userbase.kde.org/Accessibility|Accessibility Documentation for Users]
-;[[Development/Tutorials/Accessibility|Accessibility Overview]]
+:''Explains how to get started with screen readers as a user.''
-:''A list of accessibility tutorials and general information.''
 ;[[Development/Tutorials/Accessibility/Checklist|Accessibility Checklist]]

@@ Line 1: / Line 1: @@
 == Screen Reader ==
-A screen reader is an application that uses speech synthesis to allow users with visual impairments to use a computer.
+;[[Development/Tutorials/Accessibility|Accessibility Overview]]
-Read the [[Development/Tutorials/Accessibility/Screen_Reader_Setup|Screen Reader Setup page]] for more details.
+;[[Development/Tutorials/Accessibility/Checklist|Accessibility Checklist]]
 == Jovie ==
 [http://websvn.kde.org/trunk/KDE/kdeaccessibility/jovie/ Jovie] is a subsystem within the KDE desktop for conversion of text to audible speech.
-See also the [http://techbase.kde.org/Development/Tutorials/Text-To-Speech Text-To-Speech tutorial].
+;[[Development/Tutorials/Text-To-Speech|Text-To-Speech]]
 == Simon ==
 [http://simon-listens.org/ Simon] is an open-source speech recognition program and replaces the mouse and keyboard.

@@ Line 1: / Line 1: @@
-== QAccessible ==
+== Screen Reader ==
-[http://doc.qt.nokia.com/4.7/accessible.html QAccessible] is the Qt Accessible framework. Each Qt/KDE application supports QAccessible out of the box.
+A screen reader is an application that uses speech synthesis to allow users with visual impairments to use a computer.
-You need to call "export QT_ACCESSIBILITY=1" before you start the application that should be made accessible. Once the application is started and QT_ACCESSIBILITY set, then the application will load all installed accessibility-plugins (such as the Qt AT-SPI and KAccessible plugins) to provide accessibility-services.
+Read the [[Development/Tutorials/Accessibility/Screen_Reader_Setup|Screen Reader Setup page]] for more details.
 == Jovie ==

@@ Line 26: / Line 26: @@
 === How to test at-spi2 with gtk ===
-Once these are installed, you can then test at-spi2 by running gcalctool with a few environment variables set.  As mentioned on the [http://a11y.org/dbus at-spi dbus site] under "Instructions for Testing" you'll need some environment variables set.  I use a file called ~/.a11ybashrc with the following contents:
+Once these are installed, you can then test at-spi2 by running gcalctool with a few environment variables set.  As mentioned on the [http://a11y.org/dbus at-spi dbus site] under "Instructions for Testing" you'll need some environment variables set.
   export GTK_PATH=/usr/local/lib/gtk-2.0/

@@ Line 7: / Line 7: @@
 == Qt AT-SPI ==
-[http://gitorious.org/qt-at-spi qt-at-spi] is a Qt plugin that bridges the QAccessible API’s to the AT-SPI 2 protocol enabling Qt applications to be used with Orca, Accerciser, and GOK.
+[http://gitorious.org/qt-at-spi qt-at-spi] is a QAccessibleBridgePlugin that bridges the QAccessible API’s to the AT-SPI 2 protocol enabling Qt applications to be used with Orca, Accerciser, and GOK.
 For a brief overview of how atk/at-spi accessibility works on linux platforms, take a look at [http://a11y.org/atspi http://a11y.org/atspi].

@@ Line 37: / Line 37: @@
 Then to test just run gcalctool with gcalctool & from that shell.  You should see at-spi2-registryd in your process table once gcalctool has started.  If not you are likely still using at-spi instead of at-spi2.  You can use d-feet or qdbusviewer, or just qdbus to inspect the dbus interface of the registry and the accessible methods of the application at this point.  You should also be able to run orca and hear the text of the calculator tool at this point.
-==== How to test at-spi2 with Qt ====
+=== How to test at-spi2 with Qt ===
 Once you have a gtk app running correctly with orca and/or accerciser you are ready to try qt-at-spi.  In order to do so, just clone the repo from
   git://gitorious.org/qt-at-spi