The Gecko support in Firefox should be exposing the objects in all pages that use DHTML, AJAX, etc. using their associated AT-SPI roles.  The "magic" is done by converting Web ARIA roles appropriately.  As a result, we should just get much of the support for free.  However, we will probably need logic in Gecko.py to do a few things:

1) Not consume arrow keyboard events if we are in a component that handles caret navigation appropriately

2) Not consume structural keyboard navigation events if we are in a component that needs to use normal typing keys

3) If need be (it may not be needed), tease apart the code for building up a line composed of static text and DHTML/AJAX components

See also:  http://developer.mozilla.org/en/docs/Accessibility/ATSPI_Support

At CSUN, users agreed that the "sexy" form of gmail would be a great test page.