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

[David Ching]

"David Ching" <dc at remove-this.dcsoft.com> wrote in message 
news:h386g9$ei8$1 at eple.troll.no...
> Is the current status of QtAccessible in 4.5.2 supposed to be good?  Doing 
> some Internet searching, it seems Virtual Box (which uses Qt) and a few 
> other Qt-based products are having persistent difficulty with 
> QtAccessible.
>

Some more info...

I looked at the Qt Software Task Tracker and did not see that many open bugs 
for Accessibility.  What bugs there were had priority and were fixed right 
away.  So it looks like Accessibility is being given good attention at Qt. 
Thank you!


> My current issue is that the Windows JAWS screen-reader version 10.0.1142 
> insists on inserting the word "Edit" in front of all controls, e.g.  when 
> I tab to set focus to an "Unlock" button in my dialog, JAWS reads "EDIT 
> Unlock button".
>

I removed the text in the "accessibleName" field of the widgets, and now 
JAWS doesn't say "EDIT" any longer, it just reads the text of the control. 
So I guess that's what I want.  But where can I find guidelines on how to 
set the accessibleName, accessibleDescription, etc.?  No one seems to give 
practical info about them.



> In fact, when I simply click that button with the mouse, JAWS says "Edit". 
> In a standard Win32-based app, JAWS says "Unlock button" when I click the 
> button with the mouse.
>

I was wrong, the standard Windows app has JAWS reading "Unlock button" only 
when it gets the focus.  After it has focus, clicking on it doesn't say 
anything, same as the Qt one.  So again, the Qt one is correct.



> This is with the accessible\qtaccessiblewidgets4.dll put into the folder 
> containing my Qt app.exe.
>

This DLL for sure is required or else Password edit fields are not read 
"Star", they are read with the actual characters that are typed into the 
Password field!


Thanks,
David