This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| Microsoft UI Automation | |
|---|---|
| Name | Microsoft UI Automation |
| Developer | Microsoft |
| Initial release | 2007 |
| Stable release | Windows 10 / Windows 11 SDKs |
| Programming language | C++, C#, COM |
| Platform | Windows |
| License | Proprietary (Microsoft) |
Microsoft UI Automation is an accessibility framework and API developed to expose user interface elements and control patterns to assistive technologies such as screen readers and automated testing tools. It integrates into the Windows ecosystem to enable interoperability between applications, assistive technology vendors, and development platforms, while aligning with standards and regulations for accessible computing.
Microsoft UI Automation was introduced to succeed legacy accessibility APIs and to provide a comprehensive model for programmatic UI access across Windows, enabling interoperability with assistive technologies such as Freedom Scientific, NVDA Project, Dolphin Computer Access, JAWS (screen reader), Narrator (Windows). It is part of the Windows accessibility stack alongside technologies like Active Accessibility and interacts with components of Windows Presentation Foundation, Windows Forms, XAML, Win32 API, Universal Windows Platform. Major stakeholders include Microsoft Accessibility, independent software vendors such as Qualcomm, Intel, and standards bodies like W3C and ISO that influence accessibility norms such as Web Content Accessibility Guidelines and Accessible Rich Internet Applications. The framework supports interoperability with testing tools from vendors like Selenium (software), Appium, and enterprise automation suites from HP (Hewlett-Packard), Micro Focus, and IBM.
The architecture comprises core runtime components implemented in Windows NT, exposed via COM and managed wrappers used by applications built on .NET Framework, .NET Core, and .NET 5+. Key components include the UI Automation client API, provider API, eventing system, and bridge technologies that map legacy interfaces from Microsoft Active Accessibility to UI Automation. The runtime coordinates with system services like Windows Shell, Desktop Window Manager, Windows Accessibility Insights, and integrates with developer tooling such as Visual Studio, Windows SDK, and Windows App Certification Kit. Security and process isolation rely on mechanisms in Windows Security, User Account Control, and Windows API Code Pack patterns.
The UI Automation tree models a hierarchy of Windows UI elements, with nodes representing controls, windows, and content items originating from frameworks like Windows Presentation Foundation, Microsoft Edge, Internet Explorer, Outlook (Microsoft) and third-party toolkits like Qt and Electron (software framework). Control Patterns (e.g., Invoke, Value, Selection, Grid) capture interaction semantics, while property metadata describes attributes such as Name, ControlType, and IsEnabled. The tree evolves with dynamic content updates from platforms like SharePoint, Office (Microsoft), and desktop applications built with MFC or WinUI. Patterns enable assistive technologies used by organizations such as Apple Inc. and Google to interpret UI behavior for users with disabilities.
Providers implement the API within applications, often via framework-built adapters in WPF, WinForms, UWP, and third-party frameworks including GTK, wxWidgets, and Avalonia UI. Clients include assistive technologies, automated test runners, and monitoring tools from vendors such as Deque Systems, Tenon.IO, aXe, Siteimprove, and enterprise suites from Microsoft Test Manager and Azure DevOps. Interoperability scenarios involve processes like cross-process communication handled by COM and technologies influenced by Remote Desktop Services and virtualization stacks from VMware and Citrix Systems.
AutomationElements expose properties and control patterns programmatically, enabling clients to traverse the UI tree and invoke actions. Properties map to semantics used in standards bodies like W3C and to documentation by entities such as IEEE and ISO. Typical elements include Window, Button, Edit, List, and TreeView with properties such as AutomationId, HelpText, and IsOffscreen. Tooling support for inspecting these elements is provided by utilities from Microsoft Accessibility Insights, Inspect.exe, and third-party debuggers from JetBrains, Redgate, and Sentry (company).
UI Automation is supported across modern Windows releases from Windows Vista through Windows 11, with runtime enhancements delivered via Windows Update and SDKs in Windows SDK packages. Support extends to application models including Win32, COM servers, UWP, and hybrid applications such as those using WebView2 or hosted in Microsoft Teams. Legacy bridging to Microsoft Active Accessibility preserves compatibility for applications written against older APIs like MAPI or using UI toolkits such as Borland Delphi.
Developers consume managed client and provider libraries in .NET Framework and native interfaces in C++ via COM, using development environments like Visual Studio and CI/CD platforms including Azure DevOps and GitHub. Common workflows include implementing IRawElementProviderFragment, exposing patterns such as IInvokeProvider, and raising events for property changes to support automated test frameworks like NUnit, xUnit.net, MSTest, and UI automation tools like WinAppDriver. Documentation and sample code are distributed through channels like Microsoft Docs and community repositories hosted on GitHub.
UI Automation underpins compliance efforts with laws and standards such as Americans with Disabilities Act, Section 508, European Accessibility Act, and helps organizations meet procurement requirements cited by United Nations agencies and public institutions like US Department of Justice. It is integral to accessibility testing by consultancies such as W3C WAI members and vendors like Deque Systems and contributes to inclusive product design practices at companies such as Microsoft Accessibility, Apple Inc., Google, Amazon (company), and nonprofit advocacy groups including American Foundation for the Blind and Royal National Institute of Blind People.
Category:Microsoft APIs