AT-SPI is the only accessibility framework I've tried, as it's also used by Dogtail, the new GNOME GUI testing framework. Nobody has really looked into accessibility issues, we've been more focused on compatability fixes and refactoring the code to be more modular and stable. I assume that AT-SPI would only work with the GTK2 & KDE guis, we'd potentially want something that also worked with the other GUIs so it would also work on embvedded systems.

Unless somebody decides to donate a patch making the Accessibility AS2 class actually do something, this will probably be on the TODO list for some time... For one thing implementing streaming video is a current top priority.

Given the excellent level of support for Firefox from screen readers like GW-Micro Window-Eyes, the failure of the Flash plugin to expose objects to MSAA when called from Firefox has been raised as a matter of great concern on the mozilla.dev.accessibility list:

Implementing the Accessibility classes is already on the Gnash TODO list. But it is crucial that Flash objects using that class be exposed correctly to the key accessibility frameworks, especially:

1) AT-SPI: the Gnome accessibility framework. This should give better access to Flash content to Linux assistive technology users, including those with motor impairments using online keyboards like GOK, and those with visual impairments using Linux screen readers such as Gnopernicus, Orca, and LSR. Supporting AT-SPI should allow integration with KDE assistive technologies (such as KTTS) too, thanks to the AT-SPI to QT Accessibility bridge planned for KDE 4.

As early as Flash Player 6, Adobe began introducing accessibility features into Flash via the MSAA (Microsoft Active Accessibility) framework. Flash Player 8 and higher give assistive technology users access to Flash content on the web, but this only happens when using Internet Explorer:

Given the excellent level of support for Firefox from screen readers like GW-Micro Window-Eyes, the failure of the Flash plugin to expose objects to MSAA when called from Firefox has been raised as a matter of great concern on the mozilla.dev.accessibility list:

Implementing the Accessibility classes is already on the Gnash TODO list. But it is crucial that Flash objects using that class be exposed correctly to the key accessibility frameworks, especially:

1) AT-SPI: the Gnome accessibility framework. This should give better access to Flash content to Linux assistive technology users, including those with motor impairments using online keyboards like GOK, and those with visual impairments using Linux screen readers such as Gnopernicus, Orca, and LSR. Supporting AT-SPI should allow integration with KDE assistive technologies (such as KTTS) too, thanks to the AT-SPI to QT Accessibility bridge planned for KDE 4.