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

[David Ching]

"Constantin Makshin" <dinosaur-rus at users.sourceforge.net> wrote in message 
news:op.uw35fshtp27x8p at dinosaur-rus.lcl.starlink.ru...
> AFAIK QMessageBox static methods call native message box functions when 
> possible (i.e. on systems that have these functions), so it's rather 
> strange.
>

Yes, it turned out the reason was not the static calls, it was calling 
QMessageBox::setWindowTitle().  If a title is set, JAWS reads it twice 
instead of the QMessageBox::text().


>> 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. :)
>

I don't think it's necessary to have an HWND exposed, since Qt already 
exposes an IAccessibleObject for the widgets.  The IAccessibleObject is what 
holds the info for JAWS, but I'm not sure of the details.

Thanks,
David