Automate Linux GUI applications through the AT-SPI accessibility tree using dogtail

domain: desktop-automation · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Confirm the target application implements the ATK/AT-SPI accessibility bridge — AT-SPI2's `registryd` daemon only knows about apps that connect to the dedicated accessibility D-Bus and register themselves; non-bridged apps expose no tree to automate
  2. Install dogtail, described by its own project as a Python GUI test/automation framework that "uses Accessibility (a11y) technologies to communicate with desktop applications"
  3. Query the accessibility tree by application, then by node role/name, rather than by pixel coordinates, the same way any AT-SPI-based screen reader navigates the same UI
  4. Drive found nodes' available actions (e.g. clicking) the way an assistive technology would trigger them, so the automation exercises the same accessible-actions path real AT users depend on
  5. On modern dogtail (v1.0+), rely on the bundled `gnome-ponytail-daemon` helper for Wayland sessions — older dogtail's input injection assumed a direct X11/Xorg session running AT-SPI
  6. Treat GTK/Qt/Electron-with-a11y-enabled apps as the realistic automation targets, since apps that never wire up ATK/AT-SPI are invisible to dogtail regardless of script correctness

Known gotchas

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans