Re: Call for bug hunters and developers !
Thanks for sticking with us We are actually doing ok WRT to developer resources ATM. We had a very good meeting in Paris where several important projects were discussed and started on. We have people working on a new on-screen keyboard, better magnifier, and a more usable and stable Live CD system (access-wise).
There are several areas where we could do with some focused testing though and with both technical and end-user documentation.
* The AT-SPI coverage in standard applications will always need testing. How well does OpenOffice, Firefox, Natilus, etc. share its content with the access tools. It would be very worthwhile to test this in a systematic way and report problems upstream. Reporting upstream will help raise awareness of access issues as well. This can be done using the access apps, or with at-poke (install with synaptic). https://wiki.ubuntu.com/Accessibility/Specs/Testing
* KDE4: I've been told by KDE devs that the latest KDE code now supports AT-SPI, though it's not actually ready to run on non-developer systems yet because it's still very unstable (all of KDE4 that is, not specifically the AT-SPI). When KDE4 becomes a bit more stable in a month or two it will be very valuable to get some early testing in on their AT-SPI implementation, again using tools like at-poke.
* The new AT applications themselves need testing too. This includes Orca, Speech Dispatcher, SOK and compiz-mag (not yet available)
* Live CD testing - We are improving the boot screen access and making other tweaks, which could do with testing. In this cycle we will be rolling out Kubuntu and Xubuntu accessible versions as well so those will need testing.
Our access documentation is already out of date. Helping keep that current and useful would be a big help: https://wiki.ubuntu.com/Accessibility/doc We are also working on a website section: https://wiki.ubuntu.com/Website/access
There are some areas where we could do with some dev help as well.
* AT configuration system - This is a topic that wasn't picked up by the summer of code students (understandably, as it's quite boring). I'd like to see all the access configurations moved to a single location, giving us the opportunity to easily add more options as well. https://wiki.ubuntu.com/Accessibilit...CommonATConfig
* Compiz hooks - A key ingredient for the compiz-magnifier is the ability for an outside application to manipulate the behaviour of the magnifier compiz plugin. That really needs to be done by the compiz people, so some lobbying might be useful there.
Henrik Nilsen OmmaUbuntu QA Team Lead