As part of Gtk+ 3.1, Accessibility support has been integrated within Gtk+ itself. This page is a scratchpad for listing things that we find whilst testing Gtk+ 3 from master (in which Gail has been integrated).

Things which are broken in Gtk+ itself (not custom implementations)

the 'active' and 'focused' states have gone missing in tree views

1. Launch gtk3-demo
2. Arrow amongst the items in the tree view on the left

Result:

• Before states: 'active enabled focusable focused selectable selected sensitive showing single line transient visible'
• After states: 'enabled focusable selectable selected sensitive showing single line transient visible' relations='node child of'

messages seen when launching Gtk+ apps with a11y support enabled

1. Launch gnome-terminal from an xterm

Result:

• Gtk-Message: Failed to load module "pk-gtk-module"
  Gtk-Message: Failed to load module "gail"
  Gtk-Message: Failed to load module "canberra-gtk-module"

bugs which are not necessarily due to the gailectomy, but which are nonetheless present

• Bug 654405: Focused tables initially lack ATK_STATE_FOCUSED

• Bug 654410: Focus-related states and signals for menu items need sorting out

Custom implementations which got broken by side effect

654630 gnome-terminal isn't working

• According to Mike Gorse, "gnome-terminal isn't working right now ... because it uses a hack to get at the GailWidget type which doesn't work anymore."