Accessibility requirements
What you'll find here
The AccessibilityRequirements contract that keeps multimodal and
companion surfaces usable without relying on a single input mode,
visual presentation, or motion pattern.
Evidence, not approval.
Accessibility checks do not approve product surfaces by themselves. They provide evidence for the desktop, mobile, voice, and visual workspace decisions.
What it records
Surface kind
desktop_companion · mobile_companion · visual_workspace · voice.
Keyboard navigation
Screen reader labels
Reduced motion support
Contrast checks
Transcript availability
Caption availability
Notification controls
Policy envelope id
Evidence ids
Receipt ids
accessibility_check returns a reviewable result with missing
requirement names when a surface does not meet the baseline.
Baseline
Companion and visual workspace surfaces provide:
- Complete keyboard navigation for controls.
- Meaningful labels for screen readers.
- Reduced-motion behavior for animated or live surfaces.
- Contrast checks for text, controls, and status indicators.
- Transcripts for voice or audio interactions.
- Captions for video or generated speech playback.
- Operator controls for notifications.
Audit trail required.
Accessibility reviews preserve policy, evidence, and receipt links so the decision can be audited later.