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

[David Ching]

Thanks Constantin and Scott.  As is the case with all things off the "well 
beaten path," knowledge in this area comes in fits and spurts.  My latest is 
finding what appears to be a bug in Qt (which I've reported in Task 
Tracker):  widgets placed in a QStackedWidget are read by JAWS with an extra 
"EDIT" inserted.  I used the Windows Accessibility tool "inspect32.exe" and 
found that the stacked widget exposes what looks like a bogus "IP Address" 
control, which for all I know is what JAWS is reading about.

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();


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.

Cheers,
David