bevyengine/bevy
bevy_a11y
Accessibility primitives. A small crate that exposes AccessKit types as ECS components so other crates (UI, windowing) can publish accessibility data to platform screen readers and assistive tech.
Purpose
Re-export AccessKit's Node, NodeBuilder, Role, Action, etc. as Bevy types and provide a plugin that registers them with the world. The actual integration with the OS-level a11y bus happens in bevy_winit (when accesskit_unix or platform-specific features are on).
Directory layout
crates/bevy_a11y/src/
└── lib.rs # Single file. AccessibilityPlugin, ManageAccessibilityUpdates, AccessibilityNode.Key abstractions
| Type | File | Description |
|---|---|---|
AccessibilityPlugin |
crates/bevy_a11y/src/lib.rs |
Adds the resources used by other crates. |
AccessibilityNode |
crates/bevy_a11y/src/lib.rs |
Component wrapping accesskit::Node. |
ManageAccessibilityUpdates |
crates/bevy_a11y/src/lib.rs |
Resource: whether Bevy is responsible for sending a11y updates this frame. |
Focus |
crates/bevy_a11y/src/lib.rs |
Resource holding the currently focused entity for screen readers. |
Integration points
- Depends on:
accesskit,bevy_app,bevy_ecs,bevy_reflect. - Depended on by:
bevy_winit,bevy_ui,bevy_input_focus.
Entry points for modification
The crate is intentionally minimal. Most work happens in bevy_winit's a11y systems — that's where AccessKit's tree gets pushed to the OS each frame.
See also
bevy_winit— sends the AccessKit tree to the OS.bevy_ui— populatesAccessibilityNodefor UI elements.
Built by Factory AutoWiki from public repository content. It is a generated preview for codebase exploration, not source-maintained documentation.