Difference between revisions of "Development/Tutorials/Accessibility"

(Link to Community Wiki)
 
(19 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== KDE Accessibility Howto ==
+
{{Archived}}
Accessibility on kde is not quite up to speed yet.  We are close to working well with people with different disabilities, but not quite there yet.  At least on linux.  One key ingredient that is missing is [http://gitorious.org/qt-at-spi qt-at-spi] which bridges Qt applications to at-spi2.
 
  
For a brief overview of how accessibility works on linux platforms, take a look at [http://a11y.org/atspi http://a11y.org/atspi].
+
{{Info|The [https://community.kde.org/Accessibility KDE Accessibility Project] is now located at the KDE Community Wiki.}}
  
== Setup a test environment ==
+
= Introduction =
=== What you'll need ===
+
Below is a list of tutorials for KDE accessibility improvements.
In order to set up a test environment to help improve qt-at-spi (or at-spi itself)  You'll need a few things.  Orca can be installed from your distribution, as can accerciser, however accerciser will need to be run in a particular way to work with at-spi2 as I'll mention later.  You'll also need at-spi2-core and at-spi2-atk to test gtk applications.  You'll also need pyatspi2. The simplest way to get these is to clone them from the following git urls:
 
  
git://git.gnome.org/at-spi2-core
+
== Screen Reader ==
git://git.gnome.org/at-spi2-atk
+
;[http://userbase.kde.org/Accessibility Accessibility Documentation for Users on userbase.kde.org]
git://git.gnome.org/pyatspi2
+
:''Explains how to get started with screen readers as a user.''
  
Then proceed to build them by running ./autogen.sh && make && make install (or sudo make install if your user doesn't have write privileges to /usr/local)
+
;[[Development/Tutorials/Accessibility/Checklist|Accessibility Checklist]]
 +
:''What to look for in your application to make it accessible for as many people as possible.''
  
=== How to test at-spi2 with gtk ===
+
;[[Development/Tutorials/Accessibility/Screen_Reader_Setup|Screen Reader]]
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:
+
:''This tutorial will explain some details about using screen readers with KDE applications.''
 +
A screen reader is an application that uses speech synthesis to allow users with visual impairments to use a computer.
  
export GTK_PATH=/usr/local/lib/gtk-2.0/
+
== Jovie ==
export PYTHONPATH=/usr/local/lib/python2.6/site-packages/
+
[http://websvn.kde.org/trunk/KDE/kdeaccessibility/jovie/ Jovie] is a subsystem within the KDE desktop for conversion of text to audible speech.
export QT_ACCESSIBILITY=1
 
export GTK_MODULES=gail:atk-bridge
 
  
then I just source ~/.a11ybashrc to set up my shell for testing accessibility.
+
;[[Development/Tutorials/Text-To-Speech|Text-To-Speech]]
 +
:''How to utilize Jovie text-to-speech service in your application.''
  
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 ===
+
== Simon ==
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 run qmake && make && make install.  There is a handy calculator in qt-at-spi under the test folder that can be used to test qt's at-spi plugin with.  Make sure QT_ACCESSIBILITY is set in your environment and run test/test from the source folder of qt-at-spi.  You should see some console message about the bridge initializing.  You'll also see the calculator's dbus path in the org.a11y.atspi.Registry GetChildren output.
+
 
 +
[http://simon.kde.org Simon] is an open-source speech recognition program and replaces the mouse and keyboard.

Latest revision as of 12:22, 30 May 2019


This page has been archived
The information on this page is outdated or no longer in use but is kept for historical purposes. Please see the Category:Archives for similar pages.
Dialog-information.png
Information
The KDE Accessibility Project is now located at the KDE Community Wiki.


Introduction

Below is a list of tutorials for KDE accessibility improvements.

Screen Reader

Accessibility Documentation for Users on userbase.kde.org
Explains how to get started with screen readers as a user.
Accessibility Checklist
What to look for in your application to make it accessible for as many people as possible.
Screen Reader
This tutorial will explain some details about using screen readers with KDE applications.

A screen reader is an application that uses speech synthesis to allow users with visual impairments to use a computer.

Jovie

Jovie is a subsystem within the KDE desktop for conversion of text to audible speech.

Text-To-Speech
How to utilize Jovie text-to-speech service in your application.


Simon

Simon is an open-source speech recognition program and replaces the mouse and keyboard.


This page was last edited on 30 May 2019, at 12:22. Content is available under Creative Commons License SA 4.0 unless otherwise noted.