Documentation
¶
Overview ¶
atspicheck is the Phase G1 spike: walks a target app's AT-SPI accessible tree and prints whatever text + bounding-box data comes back, to answer one question before any integration work — does this actually retrieve real, correctly-positioned text? See docs/gui-bridge.md and the plan this was built against.
Self-contained (doesn't import internal/bridge) since this predates and is independent of the eventual BridgeSurface integration — it's meant to validate the AT-SPI mechanism on its own.
Usage: DBUS_SESSION_BUS_ADDRESS must already point at a session bus with at-spi2-registryd running and the target app launched against it (see the accompanying shell setup used during the spike).
Click to show internal directories.
Click to hide internal directories.