Differences between revisions 1 and 2
Revision 1 as of 2015-08-21 16:16:23
Size: 2550
Comment: add page
Revision 2 as of 2015-08-21 16:19:18
Size: 2548
Comment: fix links
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
development, please look at the [[accessibility-devel|accessibility
devel page]]. For user documentation on accessibility in Debian, please look
development, please look at the [[accessibility-devel|accessibility devel page]].
For user documentation on accessibility in Debian, please look
Line 17: Line 17:
[[https://summit.debconf.org/debconf15/meeting/290/thanks-for-maintaining-a-desktop-environment-but-is-it-accessible/
|Thanks for maintaing a desktop environment. But is it accessible?]],
[[https://summit.debconf.org/debconf15/meeting/290/thanks-for-maintaining-a-desktop-environment-but-is-it-accessible/|Thanks for maintaing a desktop environment. But is it accessible?]],

This page gathers useful information about accessibility for package maintainers in general. For more details about accessibility development, please look at the accessibility devel page. For user documentation on accessibility in Debian, please look at the accessibility page.

Desktop environments

Desktop environments can have varying levels of support for accessibility:

  • Accessibility stack working
  • Desktop bits being accessible
  • Desktop being actually accessible

Details are explained at the debconf15 talk Thanks for maintaing a desktop environment. But is it accessible?, with the slides.

Accessibility stack working

For graphical desktop accessibility to work, three things are needed:

  • the accessibility bus get started,
  • toolkits load their accessibility layer,
  • a screen reader get started.

The first two points, described in details on the accessibility devel page, can be checked automatically on any desktop with

$ git clone git://git.debian.org/git/pkg-a11y/check-a11y
$ sudo apt-get install build-essential pkg-config libdbus-1-dev libatspi2.0-dev libgtk2.0-dev libgtk-3-dev libqt4-dev qtbase5-dev 
$ cd check-a11y
$ source env.sh
$ make check

sourcing env.sh enables the various accessibility layers, and then make check can be used to check that the various toolkits are accessible.

One can also run orca -l to check that the screen reader does manage to get the list of applications, and thus probably also all the rest.

Starting the screen reader should be achievable by hand, through a keyboard shortcut (gnome uses super-alt-s), or automatically at login when enabled by the user (desktop-dependent).

Desktop bits being accessible

If the desktop is based on gtk or qt, it is relatively easy, you just need to make sure that the information is available, e.g. by running orca -e braille-monitor and work as usual.

Desktop being actually accessible

To be really usable, a desktop should notably be usable with only the keyboard.

A crash-test is to run orca, enable speech, switch off the screen, and try to work...

Gnome provides a good guide for developping accessible applications

https://developer.gnome.org/accessibility-devel-guide/stable/