Expand description
Accessibility Layer — semantic roles, focus management, screen reader mapping.
Every native widget framework already has accessibility built into its widgets. Our job is to ensure the right semantics reach the platform:
- iOS: UIAccessibility (VoiceOver)
- Android: AccessibilityNodeInfo (TalkBack)
- macOS: NSAccessibility (VoiceOver)
- Windows: UI Automation (Narrator)
- Web: ARIA attributes
The accessibility tree is a parallel structure to the shadow tree. Not every visual node is an accessibility node — we merge/prune to match how screen readers expect to navigate.
Structs§
- Accessibility
Action - Custom accessibility actions.
- Accessibility
Info - Complete accessibility info for a node.
- Accessibility
State - Accessibility state for a node.
- Accessibility
Value - Accessibility value (for adjustable elements like sliders).
- Focus
Change - Focus
Config - Focus
Manager - Manages keyboard/accessibility focus across the application.
Enums§
- Accessibility
Role - Semantic role of a UI element (maps to platform accessibility APIs).
- Live
Region - Live region announcement policy.
Traits§
- Accessibility
Bridge - Platform bridges implement this to push accessibility info to the OS.