UI Automation
A native API on the Windows platform that exposes the accessibility tree, providing screen readers and automation tools with role, name, state and position information for UI elements.
Core Facts
The Accessibility API is a programming interface provided by the operating system for assistive technologies, allowing programs to read the text content, hierarchical structure, and state information of UI elements; macOS's AX API, Windows's UI Automation, and Linux's AT-SPI are the three mainstream implementations.
The Windows Accessibility API (UI Automation/MSAA) can expose an application's UI element tree in a structured manner, including control types, names, states, position coordinates, and executable actions.
Timeline (last 90 days)
The accessibility tree is a structured UI description that the operating system maintains for assistive technologies (screen readers, voice control, automation tools), exposed by each platform's native APIs: on Windows it is UI Automation (UIA), on macOS it is AXUIElement, on Linux it is AT-SPI, and on Android it is AccessibilityNodeInfo.
The technical path of reading interface structure is typically implemented through the accessibility tree exposed by the operating system or application framework, such as Windows UI Automation, macOS Accessibility API, and the browser DOM tree.
Operating system-layer service products typically rely on system-level accessibility APIs in their technical implementation—macOS's AXUIElement framework or Windows UI Automation—to read foreground application text and write results back.
The Accessibility API is a programming interface provided by the operating system for assistive technologies, allowing programs to read the text content, hierarchical structure, and state information of UI elements; macOS's AX API, Windows's UI Automation, and Linux's AT-SPI are the three mainstream implementations.
All Facts (5)
The Accessibility API is a programming interface provided by the operating system for assistive technologies, allowing programs to read the text content, hierarchical structure, and state information of UI elements; macOS's AX API, Windows's UI Automation, and Linux's AT-SPI are the three mainstream implementations.
65%VerifiedThe Windows Accessibility API (UI Automation/MSAA) can expose an application's UI element tree in a structured manner, including control types, names, states, position coordinates, and executable actions.
65%UnverifiedThe accessibility tree is a structured UI description that the operating system maintains for assistive technologies (screen readers, voice control, automation tools), exposed by each platform's native APIs: on Windows it is UI Automation (UIA), on macOS it is AXUIElement, on Linux it is AT-SPI, and on Android it is AccessibilityNodeInfo.
50%UnverifiedThe technical path of reading interface structure is typically implemented through the accessibility tree exposed by the operating system or application framework, such as Windows UI Automation, macOS Accessibility API, and the browser DOM tree.
50%UnverifiedOperating system-layer service products typically rely on system-level accessibility APIs in their technical implementation—macOS's AXUIElement framework or Windows UI Automation—to read foreground application text and write results back.
50%