What problem does it solve?
Linux accessibility automation becomes brittle when AI tooling clicks or queries UI elements without safety guardrails, timeouts, and D-Bus-aware validation.
Core Features & Use Cases
- AT-SPI2-first desktop UI control: Traverse and query the accessibility tree for GTK/Qt applications and drive UI actions through accessible interfaces.
- Security guardrails for accessibility IPC: Apply D-Bus access control principles, treat all accessibility data as untrusted input, block sensitive roles (e.g., password fields), and enforce privilege separation via isolated process patterns.
- Deterministic, resilient interaction logic: Use GLib main loop patterns, bounded traversal (depth/node limits), cycle detection, event-driven listeners, and state verification before actions.
Quick Start
Use linux-at-spi2 to generate code that finds a focused window control and safely activates a clickable element in a Linux desktop app via AT-SPI2, respecting timeouts and role/state checks.