Accessibility

Voxlight is an app for people who listen to books. A great many of them listen because reading a printed page is difficult, painful, or impossible. Accessibility is not a compliance exercise here — it is the audience.

This page says plainly what works today, what does not, and what we are still fixing. We would rather tell you a feature is missing than let you discover it halfway through a book.

Running Voxlight entirely by voice

If your hands are not an option, Voxlight should still be. Every control in the app carries a spoken name, so iOS Voice Control can address it directly — "Tap Play", "Tap Next Chapter", "Tap Reader menu", "Tap Save Moment".

Turning a page used to be the exception. Page turns were a tap on the left or right side of the screen — a screen coordinate, which no assistive technology can reach, because Voice Control, VoiceOver and Switch Control all activate a named element, never a point. The reader's quick menu now carries Previous Page and Next Page as real, named buttons, and the menu stays open so you can keep going. Reaching the end of a chapter moves to the next one, exactly as a tap would.

Beyond that, Voxlight ships Siri App Intents and App Shortcuts, so playback, chapter navigation and capturing a moment can be spoken to Siri without opening the app at all.

VoiceOver

Icon-only buttons are labelled throughout — playback transport, the mini player, toolbars, moment rows, the reader's chrome. Sliders and scrubbers report a value, not just a position, and support the rotor's adjustable actions, so you can move through a book without dragging anything.

While audio and text are synchronised, the reader announces each sentence as the narrator reaches it. Hit targets meet the 44 pt minimum.

Larger text

The app's interface uses system text styles and scales with Dynamic Type, including the accessibility sizes. Layouts reflow rather than clip.

One honest caveat: the book reader itself does not inherit the system text-size setting. It has its own typography controls — size in 0.1 pt increments, margins, line spacing, font choice — which give finer control than Dynamic Type does, but you have to set them once inside the reader. Making the reader start from your system setting is on our list.

Reduced motion

With Reduce Motion enabled, the animated backdrop behind the karaoke lyrics freezes to a still frame, the "transcribing" indicators stop breathing and settle in their lit state, and page turns and narration-follow scrolling jump straight to position instead of gliding. Nothing moves perpetually.

Colour is never the only signal

Highlight and moment colours each carry a distinct shape — circle, square, triangle, diamond, star — so they remain distinguishable without hue. The palette itself is colourblind-safe. Server connection states are spelled out in words ("Connected", "Syncing…", "Unreachable"), not left to a green, yellow or red dot alone.

What we do not support yet

• Closed captions as a formal track. Voxlight transcribes audio on your device and can display it as live, synchronised text — but it is a feature, not an AVMediaSelectionGroup caption track, and it does not respond to the system captioning setting. We would rather leave this box unchecked than overstate it.
• Contrast on the karaoke screen. Lyric text sits over a backdrop generated from the book's cover art. Against a bright cover it does not reliably meet WCAG AA. This needs a design pass, not a patch, and it is queued.
• System text size in the reader. See above.

This website

We target WCAG 2.2 Level AA for voxlight.com: semantic landmarks, a skip link to main content, visible focus, keyboard operability throughout, and no colour-only meaning. If something here blocks you, that is a bug — please tell us.

Tell us what's broken

If an assistive technology cannot get you where you need to go — in the app or on this site — write to accessibility@voxlight.app. Tell us the screen, the technology you use, and what happened. Accessibility reports go to the front of the queue, ahead of features.