Skip to content
Zahvox
LegalLast updated · January 2026

Accessibility Statement

Zahvox aims to be a useful writing tool for as many people as possible. This statement describes the current design goals, known limitations, and how to send accessibility feedback.

On this page
Zahvox does not claim formal WCAG certification or third-party audited accessibility conformance at this stage. This is an honest statement about what we try to do and where we know improvements are needed.
Section 01

1. Commitment to accessibility

Voice-to-writing tools have the potential to help people who find typing hard, tiring, or slow. Zahvox is built with that motivation in mind. Accessibility is treated as an ongoing responsibility rather than a one-time project.

Section 02

2. Current design goals

Zahvox tries to use clear typography, sufficient color contrast, sensible heading structure, keyboard-reachable controls, semantic HTML, and understandable copy. The site is designed to work on modern browsers on desktop and mobile.

Section 03

3. Keyboard and screen reader considerations

Interactive elements are built to be reachable by keyboard where possible. Focus states are visible. Buttons and links use standard HTML semantics so assistive technology can announce them. Some third-party components and complex UI elements may still need iteration.

Section 04

4. Color contrast

Text and background colors are chosen to keep essential text readable. Both dark and light surfaces are used across the site. If a specific piece of text is hard to read for you, please send feedback so it can be reviewed.

Section 05

5. Voice tool limitations

The free web voice-to-text tool depends on the browser's speech recognition. Accuracy varies by browser, language, accent, background noise, and microphone quality. It may not be suitable for every environment or every voice. Users who cannot rely on browser speech recognition may prefer to type into the transcript field directly.

Section 06

6. Browser and device variability

Zahvox is a web product. Some accessibility behavior — for example, focus management, form controls, and speech recognition — depends on the browser and operating system. Testing new browser combinations and improving fallbacks is an ongoing task.

Section 07

7. Feedback

If you find a barrier that stops you using Zahvox — a control that is not reachable, text that is too small, a color combination that is hard to read, or anything else — please tell us through the contact page or by email to hello@zahvox.com. Concrete details make it much easier to reproduce and fix.

Section 08

8. Future improvements

Planned improvements include reviewing complex components for keyboard and screen reader behavior, improving live-region announcements in the voice tool, and continuing to audit color contrast as the design evolves. This page will be updated as changes ship.

Section 09

9. Certification status

Zahvox does not currently claim WCAG 2.1 AA, EN 301 549, ADA, or Section 508 certification. Accessibility is treated as a practical, ongoing improvement effort rather than a certification claim. If formal conformance work is completed in the future, it will be documented here.

This page is provided for transparency and product information. It is not legal advice. Zahvox should have these policies reviewed by a qualified legal professional before public launch or paid billing. Policies may change as the product evolves — the last updated date at the top reflects the most recent revision.
Questions?

Get in touch about this policy

Reach the Zahvox team at hello@zahvox.com or use the contact page for structured requests.

Contact Zahvox