Jonathan Ridell said in a blog post that there were accessibility problems with Qt. I would just like to know what those problems are. Thank you very much and keep up the excelent work. Ubuntu Rocks!
I haven't done any development in Qt, but my gloss on the subject of accessibility there is that the concern might be a bit overblown. My understanding is that while GTK has built-in ATK support, Qt has to use a 'bridge' component to tie its native system to the accepted Linux accessibility framework.
Update -- I might have been premature in calling this issue overblown. For instance, as user9237 says, it doesn't look like AT-SPI was really ever implemented. So the trolltech doc quoted looks to be a bit "optimistic" . Here is an interesting blog post, unfortunately still a bit old, covering a lot of these issues : Qt/KDE and the state of free accessibility.
Here's Mark Doffman's code site for Qt AT-SPI. Of which he says,
The possibly bogus Trolltech/Nokia link:
A slightly newer document gives an overview of Qt accessibility.
By contrast, here's a quick run-down on accessibility interfaces from the Gnome project:
The quote in the first answer seems incorrect http://doc.qt.nokia.com/latest/accessible.html
"Qt supports Microsoft Active Accessibility (MSAA) on Windows and Mac OS X Accessibility on Mac OS X. On Unix/X11, support is preliminary."
AT-SPI support was never implemented for Qt on Linux (because it would require writing CORBA bindings). dbus AT-SPI is now available and could be implemented if someone had the time, sadly nobody has so far.
Accessibility on Linux used to be a problem for Qt due to the AT-SPI support requiring CORBA.
This is now fixed: starting with Ubuntu 11.10, Qt comes with accessibility support based on the dbus AT-SPI. Accessibility is available for classic QWidget-based applications as well as QML applications.