Calling Active Accessibility APIs

Microsoft Active Accessibility provides application programming interfaces (APIs) for both clients and servers. Most are implemented in the Microsoft Active Accessibility dynamic-link library, Oleacc.dll, but NotifyWinEvent, SetWinEventHook, and UnhookWinEvent are implemented in user32.dll, which is a core component of the Microsoft Windows operating system.

Computers running Windows 95 or Microsoft Windows NT 4.0 do not have Oleacc.dll and the correct version of user32.dll installed because Microsoft Active Accessibility was incorporated in stages into succeeding versions of Windows. As a result, applications that run on these platforms explicitly link to Oleacc.dll at run time using the LoadLibrary function instead of relying on import libraries. Active Accessibility 1.3 supports Windows 95 and Microsoft Windows NT 4.0. Earlier versions of Windows are not supported by Microsoft Active Accessibility.

Server applications use the GetProcAddress function to retrieve the address of an Microsoft Active Accessibility function and then make the call through a function pointer. If calling a function that was implemented in Oleacc.dll, server applications use the handle returned from LoadLibrary in the call to GetProcAddress. If calling a function defined in user32.dll, server applications call GetModuleHandle specifying "USER32" and use the returned module handle in the call to GetProcAddress.

For example, if an application uses NotifyWinEvent, it calls GetProcAddress using the module handle of user32.dll to get the address of the function. If the call is successful (meaning that this version of Windows supports Microsoft Active Accessibility), then the application sets a flag that indicates that it is safe to call NotifyWinEvent. The address received from GetProcAddress is stored in a function pointer variable and used throughout the code.

 

 

Community Additions

ADD
Show:
© 2014 Microsoft