How gnome/at-spi2-core works
AT-SPI is a multi-process accessibility stack: applications expose accessible objects through ATK, the adaptor translates them to AT-SPI over D-Bus, and assistive technologies use libatspi to query and interact with them. The registry tracks applications and supports communication among them; a session bus launcher and device-event services provide additional stack capabilities. The README documents the main component boundaries. Source excerpts also show application registration and event translation, but do not establish every runtime call between sampled modules.
Main entry points: bridge.c ATK Bridge · atspi libatspi Bindings · adaptors Interface Adaptors · registry.c Application Registry
Components 16
Application Accessibility
- ATK API
atk
ATK Adaptation
- ATK Bridge
atk-adaptor/bridge.c - Interface Adaptors
atk-adaptor/adaptors - Event Translation
atk-adaptor/event.c - Object References
atk-adaptor/object.c
Assistive Technology Client
- libatspi Bindings
atspi - Device APIs
atspi/atspi-device-a11y-manager.c
Session Services
- Application Registry
registryd/registry.c - Device Event Controller
registryd/deviceeventcontroller.c - X11 Backend
registryd/deviceeventcontroller-x11.c - Bus Launcher
bus/at-spi-bus-launcher.c
IPC Internals
- D-Bus
- D-Bus Utilities
dbind - D-Bus Routing
droute
Other components
- Accessible Application
- Assistive Technology
Connections 17
- Accessible Application → ATK API: implements access
README.md - ATK API → ATK Bridge: translates through
README.md - ATK Bridge → Interface Adaptors: dispatches interfaces
atk-adaptor/bridge.c - ATK Bridge → Application Registry: registers application
atk-adaptor/bridge.c - ATK Bridge → D-Bus: communicates over
atk-adaptor/bridge.c - Interface Adaptors → libatspi Bindings: translates to
README.md - Event Translation → D-Bus: emits events
atk-adaptor/event.c - Object References → Interface Adaptors: encodes references
- Assistive Technology → libatspi Bindings: uses bindings
README.md - libatspi Bindings → Application Registry: discovers applications
README.md - libatspi Bindings → D-Bus Utilities: uses utilities
README.md - Device APIs → D-Bus: calls services
- Application Registry → D-Bus: coordinates over
README.md - Device Event Controller → D-Bus: handles events
- Device Event Controller → X11 Backend: uses backend
- Bus Launcher → D-Bus: launches session bus
README.md - ATK Bridge → D-Bus Routing: uses routing
README.md