Accessibility

Clear information for every way of working.

We want VibeKeys to be useful to developers with different access needs. This page describes what is available today, what is still limited, and how to help us improve it.

Our commitment

We are improving the VibeKeys website toward WCAG 2.2 AA practices, including keyboard navigation, visible focus, clear headings, skip links, and announcements for important status changes. We do not claim that the hardware or website is fully accessible today.

If a page or workflow blocks you, please contact VibeKeys support. We welcome specific reproduction steps and usability feedback from screen-reader users.

What is available now

  • The website can be operated with a keyboard and has screen-reader-friendly landmarks and labels.
  • Pro and Plus can be configured with the CLI and open-source firmware.
  • Physical keys and the navigation knob provide direct controls without relying on a mouse.
  • The setup page exposes configuration fields and connection changes to assistive technology.

Using the setup page with a screen reader

The Bluetooth configurator at setup.html is designed to be operated without sight. Useful things to know before pairing:

  • Tab order runs: Connect to VibeKeys, Load Configuration, Save Changes, then the WiFi list (+ Add, and per network: name, password, Remove).
  • Adding or removing a WiFi network is spoken aloud, and focus moves to the new row, or to the row that took the removed row's place.
  • Connection, load and save results are spoken through a live region as well as shown in a toast.
  • The list of Bluetooth devices is a dialog drawn by the browser itself, not by our page. Inside it, use the up and down arrow keys to move through devices, then press Enter or activate Pair; Tab only moves between the dialog's own buttons. If the dialog is closed without choosing a device, the page says so.

Current device limitations

VibeKeys Max currently communicates much of its state through the OLED/device display. That feedback is visual. The device does not currently provide built-in spoken feedback for the boot menu, modes, settings, Claude Code status, or transcription review.

There is no promise of a speaker, Bluetooth audio, or a 3.5mm output at this time. We are evaluating ways to expose device text over USB serial or BLE and exploring audio feedback ideas, but these are under evaluation and are not shipping features.

macOS VoiceOver and the MIC key

macOS VoiceOver uses Control + Option as its VoiceOver modifier. If your host dictation workflow also expects Ctrl + Option, the shortcuts can conflict.

  • Keep built-in ASR enabled in the configurator when it meets your needs.
  • Otherwise, remap the host dictation shortcut to a combination that does not use the VoiceOver modifier.
  • Test the selected MIC mode before relying on it in a long coding session.

See the Voice Input guide for setup details.

Roadmap and feedback

Our near-term accessibility work is focused on reliable text-based status output, better documentation, and testing with people who use VoiceOver and other screen readers. Hardware audio concepts remain exploratory; we will update this page if they become concrete product commitments.

To share feedback, email vibekeys-customer-support@secondstate.io with your device model, operating system, assistive technology, and the step where you encountered difficulty.