[pygtk] accessibility mystery

Rich Burridge Rich.Burridge at Sun.COM
Sat Jan 28 00:00:33 WST 2006


Hi Dusty,

> Any ideas why some apps are noticed and some are asleep?

See:

http://developer.gnome.org/projects/gap/guide/gad/

which is a little dated now. 

The key is in the following paragraph:

        The implementation for the GTK widgets is in a module called
	GAIL (GNOME Accessbility Implementation Library), which is
	dynamically loadable at runtime by a GTK application.  Once
	loaded, those parts of your application that use standard GTK
	widgets will have a basic level of accessibility, without you
	having to modify your application at all.  (If GAIL is not
	loaded, GTK widgets will have a default accessibility
	implementation that essentially returns no information, though
	it nominally conforms to the ATK API.)  Applications which use
	Bonobo controls, particularly out-of-process ones, also load
	accessibility support code from module "libgail-gnome".  Whether
	or not applications on the GNOME desktop automatically load
	these accessibility support libraries depends on the value of a
	gconf key, "/desktop/gnome/interface/accessibility"; a boolean
	value of "true" enables support for assistive technologies and
	applications which call gnome_program_init will automatically
	load the appropriate accessibility libraries at runtime.  "Pure
	GTK+ applications", e.g. those that use gtk+ but do not link to
	libgnome, rely on the value of the GTK_MODULES environment
	variable, which must be set to "gail:atk-bridge" in order to
	enable assistive technology support.



More information about the pygtk mailing list