Bun CLI – Screen Reader Output Compatibility

Goal: Make Bun's command-line output perceivable by screen-reader users so that error messages, help text, and interactive prompts are conveyed as meaningful speech rather than raw escape sequences.

Constraint: Bun currently emits ANSI-colored text to stdout/stderr without any mechanism to replace color with semantic markers or to provide plain-text alternatives, and its help/version commands lack ARIA-like headings that assistive technology could navigate.

Uncertainty: It is unclear whether adding a flag such as --no-color or --plain would sufficiently expose semantic structure, or if a dedicated accessibility mode that outputs labeled sections and announces focus changes would be compatible with existing terminal workflows.

Questions: What output format could Bun offer to strip ANSI codes and insert screen-reader-friendly markers? Could a --plain-output flag provide structured headings for help and version commands? How might Bun announce focus changes for interactive prompts without breaking current usage?