Accessibility and screen readers

Getting started·3 min read·Updated 2 months ago

Voysey is built to be usable regardless of how you interact with a screen. The whole app is keyboard-friendly, focus is always visible as you tab through, touch targets are sized to be reachable, and screen readers have the labels they need to describe what is on screen.

Screenshot: focus outline visible on the primary Studio action

Keyboard navigation

Tab moves forward through interactive elements. Shift+Tab moves backward.
Enter or Space activates the focused control.
Esc closes an open modal or dismisses a takeover.
Focus is always visible. A clear outline shows what you are about to activate.

Screen reader support

Every control has a name, a role, and a state that screen readers can announce. Icon-only buttons have text alternatives. Live regions announce when a run finishes or an artifact lands. Long-form content (manuscript pages, generated documents) reads as continuous prose.

Contrast

Text everywhere in the app meets the WCAG AA contrast floor. Cards and panels have real separation borders rather than a subtle color shift, so boundaries are visible in bright light and for anyone with reduced vision. The "generating" state hue is tuned to read clearly for everyone.

Touch and click targets

Touch targets on mobile are sized to be reachable at 44 points minimum. Desktop keeps controls comfortable to click without hunting.

Notice something that could be better?

Accessibility is an ongoing pass, not a fixed state. If you hit a control you cannot reach with a keyboard, a label that does not read well, or contrast that fails you, let us know so we can fix it.

Was this article helpful?