ResponsiveVoice accessibility features
Audio tools that support a more accessible reading experience.
ResponsiveVoice helps publishers add spoken versions of page content, article narration, keyboard-operable playback controls, and multilingual text to speech. It can support an accessibility program, but it does not by itself make a website legally compliant.
Supported audio accessibility features
Use ResponsiveVoice where spoken content is useful: long-form articles, help centers, education pages, onboarding flows, and content-heavy product pages. These features are designed to add audio access and reader control without pretending to replace a full accessibility audit.
Article web player
Add an inline player that narrates matched page content, highlights paragraphs, supports click-to-jump navigation, and can follow readers with a mini-player.
Keyboard-operable playback
The web player is built for pointer and keyboard use, including visible controls for play, pause, skip, progress, time, and speed when enabled.
Multilingual text to speech
Choose voice names or structured voice selectors for different languages, voices, rates, pitches, and volumes.
Content selection
Point the player at article, help, or lesson markup with selectors, then exclude decorative or non-reading-flow elements with data-rv-skip.
Dynamic content support
For single-page apps and lazy-loaded pages, mount the player after content appears in the DOM and unmount it before removing that content.
Brandable player themes
Use the neutral theme, the ResponsiveVoice theme, or custom tokens for color and layout decisions that fit your site.
Where ResponsiveVoice fits in an accessibility stack
Text to speech can be one part of an inclusive content strategy. It gives readers another way to consume text and can help teams offer audio playback without building a custom narration system from scratch.
ResponsiveVoice can help with
- Spoken playback for selected page content.
- Reader controls for play, pause, speed, progress, and skipping.
- Paragraph highlighting and click-to-jump reading flow.
- Configurable voice, language, rate, pitch, and volume.
- Documentation and examples for implementing the web player.
Your site team still owns
- Semantic HTML, headings, landmarks, forms, and labels.
- Keyboard navigation for the whole site experience.
- Color contrast, focus indicators, and responsive layout.
- Alternative text, captions, transcripts, and media alternatives.
- Legal review, accessibility audits, remediation, and compliance decisions.
Coming soon: Accessibility Pro
Accessibility Pro is the ResponsiveVoice package for teams that need audio playback with clearer accessibility positioning, documentation, and support. It is aimed at organizations adding web-player narration as part of a broader accessibility program.
Accessibility-focused setup
Guidance for adding the web player to article, support, education, and documentation pages.
Documentation for reviewers
Product documentation intended to help explain what the ResponsiveVoice player covers and what remains outside its scope.
Priority path for teams
A support and packaging path for teams treating audio playback as a planned accessibility feature, not a one-off widget.
Plan audio playback with clear scope.
Start with the Accessibility Pro page, then use the web-player guide and examples to decide where spoken content belongs on your site.
