VoiceOver Support
Accessible labels exist on selected controls; terminal accessibility is more limited.
Availability
Partially implemented in stable. Read the limits below before relying on this workflow.
Reviewed against stable v0.5.1. Rust candidate additions are labeled separately. Release status.
The pain this solves
- Unlabeled controls can be difficult to identify with assistive technology.
What ships with it
- Some custom controls expose accessibility labels and values.
- The reviewed stable source does not establish navigable terminal-buffer text or automatic announcements for new output.
- Accessibility coverage varies by view.
Questions this answers
- Does Chau7 label controls for VoiceOver?
- Does VoiceOver automatically read new terminal output?
- Can I navigate terminal output as accessible text?
How it works
Some custom controls, including command-palette and tab actions, set accessibility labels or values so assistive technology can identify them.
The stable source does not show a complete terminal-buffer accessibility implementation that exposes output as navigable text and announces every new line.
Accessibility coverage varies by view. Do not claim every dialog, pane, tab, and terminal element is fully accessible without a separate verified review.
Why it matters
Clear labels on custom controls can help users identify app actions. Users who depend on terminal text navigation should verify the current terminal accessibility behavior before relying on Chau7 as a full screen-reader terminal.
Frequently asked questions
Are some Chau7 controls labeled for accessibility?
Yes. The stable source includes accessibility labels and values on selected app controls.
Does stable v0.5.1 announce all new terminal output?
The reviewed source does not establish automatic announcement of terminal output.
Is every UI surface fully VoiceOver accessible?
That universal claim is not supported by the available stable implementation evidence.