In the next release we want to improve accessibility in the core applications of Xfce. The Gtk+ toolkit already provides most of the required accessibility, but there are a lot of parts of the interface (custom widgets, buttons without label) that are hard to access with a screen reader.
This includes the following tasks:
More information about accessibility can be found in the Gnome accessibility guide.
Currently if Xfce4-session is compiled with
–enable-gnome (enable gconf) and Gnome compatibility is checked in the setting, we check the
/desktop/gnome/interface/accessibility key and if set to true, the string array in
/desktop/gnome/accessibility/startup/exec_ats is spawned (see code).
This is obviously hard to find and also not fully working since the required Gtk modules are not loaded as well (this probably was handled by gdm, but not any more?).
There has been a proposal for a D-Bus property to synchronize the setting that says whether assistive technologies are enabled across applications and desktop environments. We already have a “Enable assistive technologies” check button in the accessibility settings dialog. All we have to do is set the
org.a11y.status.IsEnabled property on startup and update our setting whenever the this property changes. This will allow applications like Orca to enable AT support in Xfce automatically. That way blind users can just start Orca–followed by a logout/login–to activate AT, rather than having to search for the “Enable assistive technologies” check button.
The D-Bus API proposed in the mails is outdated. at-spi2-core implements the following API instead (see http://git.gnome.org/browse/at-spi2-core/tree/bus/at-spi-bus-launcher.c#n60):
<interface name='org.a11y.Status'> <property name='IsEnabled' type='b' access='readwrite'/> </interface>
Testing can be done by running Orca or Accerciser and start the application with . – option for this in the accessibility dialog.
GTK_MODULES=“gail:atk-bridge” in the environ
We need an xfce-a11y mailing list for discussion on accessibility issues. Xfce-a11y list.
ExoIconView, which in turn is based on
GtkContainerand doesn't implement
gtk/a11y/gtkcontaineraccessible.c). So I guess we'll have to add an
ExoIconViewAccessibleclass or something similar to make this work. — Jannis Pohlmann 2011/09/08 23:11
(Looking at what is in place elsewhere and starting a brainstorming list)
Might be applicable (is any of this done by XFCE?):
Not applicable (cannot count on what the distro will ship):