Accessibility

How Autopilot stays usable for keyboard-first and assistive workflows.


Accessibility

Autopilot is meant to be usable without a mouse and without a complicated UI.

CLI Accessibility

  • Commands are keyboard-driven.
  • Help text is available in the terminal.
  • JSON output supports screen-reader-friendly tooling and wrappers.

Dashboard Accessibility

  • The dashboard uses simple terminal output and key commands.
  • q quits and p toggles pause.
  • It works best in a normal terminal rather than a mouse-heavy workflow.

Docs Accessibility

  • The docs use clear headings and short sections.
  • Code examples are written as copyable text.
  • Troubleshooting pages are structured so issues can be found quickly.

Recommendations

  • Prefer the JSON output flags when integrating with scripts.
  • Keep terminal font sizes and contrast readable.
  • Use branch rules and config settings rather than memorizing hidden behaviors.
Was this page helpful?
Edit this page