The IAccessibleEx Interface
Controls that do not have a Microsoft UI Automation provider, but that implement IAccessible, can easily be upgraded to provide some UI Automation functionality by implementing the IAccessibleEx interface. This interface enables the control to expose UI Automation properties and control patterns, without the need for a full implementation of UI Automation provider interfaces such as IRawElementProviderFragment. To use IAccessibleEx, IRawElementProviderFragment, and all other UI Automation interfaces, include the UIAutomation.h header file in your source code.
For example, consider a custom control that has a range value. The Microsoft Active Accessibility server for the control defines the control's role and is able to return its current value. However, because Microsoft Active Accessibility does not define minimum and maximum properties, the server lacks the means to return the minimum and maximum values of the control. A UI Automation client is able to retrieve the control's role, current value, and other Microsoft Active Accessibility properties, because the UI Automation core can obtain these through IAccessible. However, without access to an IRangeValueProvider interface on the object, UI Automation is also unable to retrieve the maximum and minimum values.
The control developer could supply a complete UI Automation provider for the control, but this would mean duplicating much of the existing functionality of the IAccessible implementation: for example, navigation and common properties. Instead, the developer can continue to rely on IAccessible to supply this functionality, while adding support for control-specific properties through IRangeValueProvider.
In this section
- IAccessibleEx Implementation Guidelines
- Implementing IAccessibleEx for Providers
- Using IAccessibleEx from a Client
Related topics