[Qt-interest] QtAccessible - anyone else having issues?

[Constantin Makshin]

On Tue, 14 Jul 2009 04:36:30 +0400, David Ching  
<dc at remove-this.dcsoft.com> wrote:
> I've also found what appears to be another bug in Qt (also reported in  
> Task Tracker): text in the static calls to e.g.
> QMessageBox::information() do not properly have the text content read
> by JAWS.  I worked around it by using the "properties API" of
> QMessageBox instead, e.g.
>
>   QMessageBox msg;
>   msg.setText("This text is read properly by JAWS");
>   msg.exec();
AFAIK QMessageBox static methods call native message box functions when  
possible (i.e. on systems that have these functions), so it's rather  
strange.

> One more thing:  although Qt usually just makes each top-level window  
> have one HWND with no child windows, this behavior is entirely changed
> when JAWS is running.  When JAWS is running, the same app now appears
> with native Windows HWND's for all the child widgets!  I couldn't
> believe that, but it's true! I ran Spy++ to see that.
Well, it's likely that Qt works this way to let accessibility tools know  
that the top-level window has controls/widgets. :)

-- 
Constantin "Dinosaur" Makshin