Skip to main content

Module accessibility

Module accessibility 

Source
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§

AccessibilityAction
Custom accessibility actions.
AccessibilityInfo
Complete accessibility info for a node.
AccessibilityState
Accessibility state for a node.
AccessibilityValue
Accessibility value (for adjustable elements like sliders).
FocusChange
FocusConfig
FocusManager
Manages keyboard/accessibility focus across the application.

Enums§

AccessibilityRole
Semantic role of a UI element (maps to platform accessibility APIs).
LiveRegion
Live region announcement policy.

Traits§

AccessibilityBridge
Platform bridges implement this to push accessibility info to the OS.