Skip to main content

Accessibility Statement

Last updated: October 17, 2026

SylphSpeak is a product operated by SabotenAI LLC. We care about flexible participation and want SylphSpeak to support different ways people read, type, listen, move, see, communicate, and interact online.

This Accessibility Statement applies to the SylphSpeak website, desktop application, account portal, documentation, support channels, Voice Protocol (also called “VPTCL”), and related product experiences that SabotenAI LLC controls, including Voice Protocol at sylphspeak.com/protocol/, vptcl.co, voiceprotocol.co, and any successor domains. References to SylphSpeak may also include related technical, distribution, or infrastructure names we use, such as SylphSpeak Desktop, and related marketing names or descriptions we use, such as SylphSpeak LIVE.

SylphSpeak is a typing-first text-to-speech tool. It may be useful to people who cannot speak, prefer not to speak, temporarily lose their voice, communicate better by typing, or need another way to participate in voice environments. Accessibility is part of the product’s purpose, but it is also an ongoing process.

Our Accessibility Goal

Our goal is to make SylphSpeak usable by as many people as reasonably possible, including people who use assistive technologies, rely on keyboard input, prefer reduced motion, need clear text, or communicate in ways other than speaking.

As a practical benchmark, we aim to follow the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA where applicable to the public website and web-based product experiences we control.

For the desktop application, we aim to apply relevant accessibility principles where practical, including keyboard access, readable interface text, visible focus, reduced-motion support, predictable interaction patterns, and compatibility with operating system accessibility settings where feasible.

This is an accessibility goal and working standard, not a claim that every page, feature, prototype, beta feature, third-party flow, desktop interface, operating system interaction, audio device setup, or product experience fully conforms at all times.

What We Build For

We design and maintain SylphSpeak with accessibility considerations such as:

  1. Clear page structure, headings, and landmarks on public web pages.
  2. Keyboard navigation for interactive elements where practical.
  3. Visible focus styles.
  4. Text alternatives for meaningful imagery where appropriate.
  5. Reduced-motion support where the user’s system preferences request it.
  6. Readable text sizing, spacing, and interface density.
  7. Reasonable color contrast.
  8. Forms with labels, instructions, and error messaging where applicable.
  9. Link and button text that aims to be understandable in context.
  10. Responsive layouts across common screen sizes.
  11. Predictable onboarding steps.
  12. Clear setup guidance for audio routing, virtual microphones, and listening devices.
  13. Support for typed communication as a primary interaction method.
  14. Keyboard shortcuts and workflow patterns intended to reduce friction for users who type to communicate.
  15. Plain-language support materials where practical.

Desktop App Accessibility

SylphSpeak is a desktop application that interacts with your operating system, audio devices, virtual microphones, speakers, headsets, and third-party applications.

We aim to make the desktop app reasonably usable with common desktop interaction patterns, including:

  1. Keyboard-first workflows where practical.
  2. Clear focus behavior.
  3. Readable labels and controls.
  4. Avoiding unnecessary motion or animation where reduced-motion settings apply.
  5. Clear feedback for connection, playback, routing, and error states.
  6. Settings that help users control voice, volume, monitoring, routing, and behavior.
  7. Onboarding that explains important setup steps in a clear sequence.

Some accessibility behavior may depend on your operating system, device drivers, window manager, audio stack, virtual audio tools, browser, third-party app, screen reader, input device, or accessibility settings.

Voice Protocol

Voice Protocol is a directory and editorial project about creators who communicate in alternative ways. We aim to apply the same WCAG 2.2 Level AA benchmark to Voice Protocol pages, including:

  1. Directory search, filters, and listing cards that work with a keyboard and screen readers.
  2. Text alternatives for creator avatars and editorial images where practical.
  3. Descriptions of how creators communicate written in plain, respectful language.
  4. Clear labels, instructions, and error messages on the listing submission form.
  5. Text versions or captions for audio and video we publish, where practical.

Some Voice Protocol content comes from creators or third parties, such as avatars, artwork, banners, and linked channels, streams, and social profiles. Those materials, and the platforms they link to, may not meet our accessibility goals, and we don’t control them.

If you can’t use the submission form, you can ask to be listed, or ask for a correction or removal, by email: submissions@voiceprotocol.co for listings, editorial@voiceprotocol.co for corrections, and privacy@voiceprotocol.co for removals.

Audio and Communication Considerations

SylphSpeak helps convert typed text into spoken audio, but audio behavior can vary depending on your setup.

Accessibility-related limitations may include:

  1. Audio may route to the wrong device if system or app settings are not configured correctly.
  2. Virtual microphone setup may require third-party tools, operating system permissions, or manual configuration.
  3. Third-party meeting, game, streaming, or voice-chat apps may handle virtual microphones differently.
  4. Text-to-speech voices may vary in clarity, pronunciation, language support, emotional tone, latency, and availability.
  5. Cloud text-to-speech may depend on internet connection, provider availability, and account status.
  6. Local system text-to-speech may depend on installed operating system voices and system settings.
  7. Speech filtering, pronunciation rules, substitutions, and prediction tools are best-effort and may not catch or correct every issue.
  8. Generated speech may be delayed, mispronounced, interrupted, clipped, or routed unexpectedly.

We encourage users to test their audio routing, volume, listening device, and target app settings before relying on SylphSpeak in calls, streams, meetings, games, or other live environments.

Testing and Review

We use automated accessibility checks on key public pages as part of our release process. Automated tools can help identify many issues, but they do not catch every accessibility barrier.

Where practical, we also review pages and product flows manually for keyboard navigation, focus visibility, text alternatives, heading structure, reduced motion, readable text, contrast, and basic assistive technology compatibility.

For the desktop application, we may test core workflows such as onboarding, typing, sending speech, changing settings, routing audio, and managing account state. Testing coverage may vary by operating system, version, device, and release stage.

We may update our testing process over time as the website, application, design system, onboarding, audio features, and product architecture evolve.

Known Limitations

We are a small team, and accessibility coverage may vary across the Service.

Known or possible limitations may include:

  1. Some desktop app features may not yet be fully optimized for all screen readers, input methods, display settings, or operating system accessibility configurations.
  2. Some brand color pairings, glass effects, animations, or visual treatments may need further contrast or motion refinement as we continue developing the visual system.
  3. Older, experimental, draft, archived, alpha, beta, or newly released features may lag behind our current accessibility practices.
  4. Some third-party services, authentication flows, checkout flows, payment tools, analytics tools, voice providers, cloud services, virtual audio tools, operating system dialogs, or external platforms may not be fully controlled by SabotenAI.
  5. Product screenshots, concept art, decorative visuals, waveform-style visuals, or brand imagery may not always communicate all details through text alternatives if they are not essential to using the page.
  6. Audio setup may vary depending on your operating system, drivers, microphone, speakers, headset, virtual audio cable, target application, permissions, and privacy settings.
  7. Some text-to-speech voices may be less clear, less natural, unavailable, delayed, or unsupported in certain languages, accents, regions, providers, or plans.
  8. Keyboard shortcuts may conflict with third-party apps, games, operating system shortcuts, or assistive technology.
  9. Accessibility support may vary depending on your browser, device, operating system, assistive technology, and settings.

We aim to address reported barriers in a reasonable way and within a reasonable timeframe, taking into account severity, user impact, technical complexity, product stage, third-party limitations, and available resources.

Third-Party Services

SylphSpeak may link to or interact with third-party services, such as authentication providers, payment processors, cloud text-to-speech providers, analytics providers, crash-reporting tools, support tools, repositories, operating system services, virtual audio tools, meeting apps, games, streaming tools, and other external platforms.

Third-party services are controlled by their own providers. We cannot guarantee the accessibility of third-party websites, platforms, tools, voices, audio devices, operating system dialogs, or content, but we try to choose and configure services responsibly where we have practical control.

Accessibility Feedback

If you experience an accessibility barrier with SylphSpeak, please let us know.

Helpful details include:

  1. The page, feature, or app screen involved.
  2. What you were trying to do.
  3. What went wrong or what was hard to use.
  4. Your browser, device, operating system, app version, or assistive technology, if relevant.
  5. Your audio setup, if the issue involves microphone routing, listening devices, monitoring, volume, or playback.
  6. Any screenshot, recording, log, or description that would help us understand the issue.

You can contact us at:

Email: accessibility@sabotenai.com
Subject line: Accessibility

For accessibility barriers on Voice Protocol, contact accessibility@sabotenai.com with the subject line “Voice Protocol Accessibility”.

We review accessibility feedback and do our best to respond, investigate, and address confirmed barriers in a reasonable timeframe.

Product Support and Safety

Accessibility feedback is welcome, but SylphSpeak is not an emergency service, medical device, legal accommodation provider, telecommunications carrier, or guaranteed replacement for human speech in every situation.

Do not rely on SylphSpeak as your only communication method in emergencies, medical situations, legal proceedings, employment proceedings, safety-critical settings, or other high-stakes contexts.

For urgent safety, medical, legal, or emergency needs, use appropriate local emergency, medical, legal, workplace, school, or support resources.

Ongoing Improvement

Accessibility is an ongoing process, not a one-time checklist. We may update this page as our website, desktop app, onboarding, documentation, design system, product features, tools, and accessibility practices evolve.

Updates to This Statement

We may update this Accessibility Statement from time to time as SylphSpeak, SabotenAI, our products, our design system, our tools, our accessibility practices, and known limitations change.

When we update this page, we may revise the “Last updated” date above.

Contact

Questions about this Accessibility Statement may be sent to:

SabotenAI LLC
Email: accessibility@sabotenai.com
Website: https://sylphspeak.com

← Home