KDE Accessibility
Developers' Information
Text To Speech
The KDE Text-To-Speech Daemon offers a D-Bus interface for applications using speech synthesis. Any notifications can also be read out.
AT-SPI
The biggest task of the KDEAP developments is the planning and implementation of AT-SPI support for KDE. AT-SPI (Assistive Technologies Service Provider Interface) is a cross-toolkit interprocess protocol that allows assistive technologies like screen readers, on-screen keyboards or braille device drivers to access all of the graphical user interfaces of an application, abstracting from toolkit dependent GUI objects.
Introduction:
Documents describing the current situation:
- Qt Accessibility Architecture
- GNOME Accessibility Architecture (ATK and AT-SPI)
- A Comparision of the Two Architectures
- Accessibility status of KDE widgets
Possible bridge architectures:
Conclusion:
Word Completion
One of the features recently added to KMouth is word completion. Our plan is to turn this into a library for use in other applications.
The file format of the word lists is shared by the GNOME On-screen Keyboard (GOK). We also plan to define a standard for storing word lists and settings, so GOK and KMouth can benefit from words added in other applications and vice versa.
Keyboard Accessibility
Hardly any part of KDE is independent of accessibility issues. One very important aspect of accessibility for example are the key bindings. Some people cannot use a mouse, some cannot use a keyboard, some can use both with pain. Making KDE fully keyboard accessible does not rely on big architecture changes. If you are a developer, please make sure all the GUI elements of you programs are easily accessible by the keyboard.
[ Edit ]
