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

[Constantin Makshin]

As far as I could understant the code of the Qt accessibility module, it  
just sends widgets' properties to the underlying accessibility API.

Also the information I've found about JAWS says that it uses scripting to  
work with "non-standard Windows applications" (from the "JAWS Data  
Sheet"), "such as programs that do not use standard Windows controls"  
(from Wikipedia). Since Qt doesn't use Windows' native controls but draws  
them by itself, I guess it's possible that JAWS doesn't completely  
"understand" Qt applications and sometimes gives wrong results.

Unfortunately, I've never worked with any accessibility tools and  
therefore won't be able to give more than simple suggestions.

On Sat, 11 Jul 2009 05:59:34 +0400, David Ching  
<dc at remove-this.dcsoft.com> wrote:
> "Constantin Makshin" <dinosaur-rus at users.sourceforge.net> wrote in  
> message
> news:op.uwvm6zfqp27x8p at dinosaur-rus.lcl.starlink.ru...
>> Documentation for both QWidget::accessibleName() and
>> QWidget::accessibleDesciprion() functions refer to
>> QAccessibleInterface::text() one, where you can find the purpose of
>> different accessibility properties.
>
> Yes, those are good descriptions, but doesn't tell me why JAWS inserts  
> the word "Edit" when I specify an accessibleName or give guidance on
> how to set them with examples.  Not saying it's Qt's job to do that,
> but it does such a good job in many other areas to give good general
> introductions ....
>
> Thanks,
> David

-- 
Constantin "Dinosaur" Makshin