Yes, but my point is that these functions are not only used by ATs. UI Automation was designed for full automated testing of Windows. Accessibility was simply added to it after the fact.
I do know that RFT uses MSAA and UIA for testing and not for accessibility
purposes.
Rich Schwerdtfeger
CTO Accessibility Software Group
Pete Brunet
<p...@a11ysoft.co
m> To
Richard
05/25/2010 10:12 Schwerdtfeger/Austin/i...@ibmus
AM cc
IAccessible2 mailing list
<accessibility-...@lists.linux-foun
Please respond to dation.org>,
p...@a11ysoft.com accessibility-ia2-boun...@lists.lin
uxfoundation.org, Andres Gonzalez
<andgo...@adobe.com>, James Teh
<ja...@nvaccess.org>
Subject
Re: [Accessibility-ia2] screen
reader present flag
MSDN at
http://msdn.microsoft.com/en-us/library/dd373892%28VS.85%29.aspx
indicates that WM_GETOBJECT gets sent by oleacc in response to the three
MSAA AccessibleObjectFrom* functions. (It's also send in response to
IUIAutomation::ElementFromHandle, ElementFromPoint, and GetFocusedElement.)
Is RFT using it in some other fashion? If so is there any documentation I
can read to learn more?
Thanks, Pete
===
Richard Schwerdtfeger wrote:
Any application that would test other native applications would use
this. For example: Rational Functional Tester.
Rich Schwerdtfeger
CTO Accessibility Software Group
Inactive hide details for Pete Brunet ---05/25/2010 09:37:30
AM---Rich, What other apps are using this message? How are they us
Pete Brunet ---05/25/2010 09:37:30 AM---Rich, What other apps are
using this message? How are they using it?
Pete Brunet
<p...@a11yso
ft.com>
To
05/25/2010
09:37 AM Richard Schwerdtfeger/Austin/i...@ibmus
cc
Please respond to
p...@a11ysoft.com Andres Gonzalez <andgo...@adobe.com>,
IAccessible2 mailing list
<accessibility-...@lists.linux-foundation.org>
,
accessibility-ia2-boun...@lists.linuxfoundatio
n.org, James Teh <ja...@nvaccess.org>
Subject
Re: [Accessibility-ia2] screen reader present
flag
Rich, What other apps are using this message? How are they using it?
===
Richard Schwerdtfeger wrote:
I have to agree with Andres. WM_GETOBJECT is not solely
used by AT.
Rich Schwerdtfeger
CTO Accessibility Software Group
Inactive hide details for Andres Gonzalez ---05/25/2010
08:48:08 AM---WM_GETOBJECT is NOT a reliable way of
detecting AT eitherAndres Gonzalez ---05/25/2010 08:48:08
AM---WM_GETOBJECT is NOT a reliable way of detecting AT
either, since it may be triggered by apps and even device
drivers that don't
Andres Gonzalez
<andgo...@adobe.co
m>
Sent by:
accessibility-ia2- To
boun...@lists.linu
xfoundation.org "p...@a11ysoft.com"
<p...@a11ysoft.com>, James Teh
<ja...@nvaccess.org>,
05/25/2010 08:46 IAccessible2 mailing list
AM <accessibility-...@lists.linux-f
oundation.org>
cc
Subject
Re: [Accessibility-ia2] screen
reader present flag
WM_GETOBJECT is NOT a reliable way of detecting AT
either, since it may be triggered by apps and even device
drivers that don't have anything to do with AT, so you
are guarantied false positives even with the best
heuristics. I'm very interested in developing a reliable
handshake mechanism with AT, and would love to hear from
others with ideas/proposals on this respect. Perhaps we
can take this task for the next edition of IA2 in this
list, or by a subgroup of interested parties, and bring
back a concrete proposal to the general group.
Thanks,
--Andres.
From: accessibility-ia2-boun...@lists.linuxfoundation.org
[
mailto:accessibility-ia2-boun...@lists.linuxfoundation.org
] On Behalf Of Pete Brunet
Sent: Monday, May 24, 2010 4:18 PM
To: James Teh
Cc: IAccessible2 mailing list
Subject: Re: [Accessibility-ia2] screen reader present
flag
Thanks Jamie, I'll have to check with the architects to
see if they would have any issues with blocking. If I can
block then I might also be able to lazily call into the
secondary thread to build the tree as needed. -Pete
===
James Teh wrote:
On 25/05/2010 8:37 AM, Pete
Brunet wrote:
Thanks
Jamie,
[using
WM_GETOBJECT
to dynamically enable accessibility] may be a problem for the case where
the app
has
multiple
threads
and a
secondary
thread
needs to
be called
by the
window
proc to
participate
in the building of the accessibility tree. Is it
acceptable
to block the UI thread?
I don't see why this is any
different to creating the tree in
the same
thread. Either way, it will block
the UI thread, as the
WM_GETOBJECT
message needs to return the
requested accessible object. Can
you shorten
the setup time by creating parts
of the tree lazily only when
requested?
Jamie
_______________________________________________
Accessibility-ia2 mailing list
Accessibility-ia2@lists.linuxfoundation.org
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
<<inline: graycol.gif>>
<<inline: pic19380.gif>>
<<inline: ecblank.gif>>
_______________________________________________ Accessibility-ia2 mailing list Accessibility-ia2@lists.linuxfoundation.org https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
