Accessibility
Konthora is built to be usable by everyone, including people who navigate by keyboard, use screen readers, or scale text in their browser.
We aim for the Web Content Accessibility Guidelines (WCAG) 2.1 level AA. Accessibility is part of how we build the workspace, not a feature added afterwards: the tools are designed so that generating speech and transcripts does not depend on a mouse, a particular screen size, or a particular way of seeing the page.
What works today
- Keyboard navigation. Every control in the text-to-speech and transcription workspaces — language and voice pickers, speed and pause sliders, generate and download buttons — is reachable and operable by keyboard, with a visible focus outline on the active control.
- Screen-reader labels. Interactive controls carry accessible names and states: voice pickers announce the selected voice, toggles and sliders announce their values, and status changes (queued, generating, completed, failed) are shown as text rather than colour alone.
- Structure. Pages use one main heading and a logical heading order, landmarks, and breadcrumb navigation, so assistive technology can map a page before reading it.
- Text and contrast. Copy uses high-contrast text on the dark interface, and the layout is responsive, so text can be scaled up in the browser.
- No account walls. Nothing on the site requires creating an account or completing a visual challenge to use the tools.
- Audio alternatives. Transcription output is text (TXT, SRT, VTT, JSON), so audio content has a readable equivalent. For the other direction, see our guide on text-to-speech vs screen readers.
Known limitations
Generated speech previews play as audio with a visible play/pause control and a text label; a preview reads one short fixed sentence in the voice's own language. Some decorative motion (hero animation, hover states) is visual only and carries no information. If you find a control that cannot be reached by keyboard, a label that a screen reader misreads, or a page that breaks at large text sizes, that is a bug — please tell us.
Report a barrier
Tell us which page you were on, what you were trying to do, and what assistive technology or browser you use, through our contact page. We review accessibility reports as bugs and fix the underlying control rather than offering a separate version of the site.
This statement was last updated on 15 November 2026. It describes the site as built today; when a control changes, the statement is updated with it.