Quantcast
Channel: Windows Desktop Development for Accessibility and Automation forum
Viewing all articles
Browse latest Browse all 585

Failure to call IAccessible in Windows 10

$
0
0
Hello everybody,

We have an issue on Microsoft Active Accessibility interacting with our UI elements. It could be related to the SDK upgrading from version 6.0 to version 7.0.  In Windows 10, the AccessibleObjectFromWindow function sends WM_GETOBJECT to UI elements with a 10-digit wParam identifier, but in Windows 7, the wParam identifier in the same case only has 4 digits.  Such a difference would cause failure to call IAccessible in Windows 10.

Here are the steps for the comparison between Windows 10 and Windows 7 for the client:
1.The client calls Windows API: AccessibleObjectFromWindow
2.AccessibleObjectFromWindow send WM_GETOBJECT request message to the UI element
3.The UI element return IAccessible interface back to the client
4.Debug the client UI element with the received IAccessible interface and found that the wParam identifier has value 4294967295 in Windows 10
5.Use the same client and did the same test in Windows 7, the wParam identifier is a 4-digit value

May I know if the SDK upgrade from version 6.0 to version 7.0 impact on the Accessibility function? Any more information about the wParam code reference, or information about how it is generated?


Viewing all articles
Browse latest Browse all 585

Trending Articles