Published 2026-03-20 · Updated 2026-10-22 · MachenVoice
Text-to-speech can help some people access written content by listening while they read along, but it is not a treatment for dyslexia. MachenVoice is a general-purpose TTS studio; this guide explains practical, respectful ways educators and publishers use TTS alongside accessible design. We focus on layout, player controls, and honest disclosure—not medical claims.
What research generally supports
Many learners with dyslexia benefit from multimodal reading—seeing text while hearing it spoken—which can reduce working-memory load for decoding. Results vary by person, age, and instruction context.
Major accessibility standards (such as WCAG) emphasize perceivable text alternatives and user control over time-based media. TTS is one tool in that toolbox, not a substitute for structured literacy instruction or clinical therapy.
Design content for listening and reading together
Use short paragraphs, generous line spacing in your LMS or HTML, and plain language. When MachenVoice narrates a block, mirror the same text on screen so users can follow along.
Avoid justified text and dense columns; dyslexia-friendly layouts often use left-aligned text and clear headings.
Voice choice and speed
Let users pick voice and playback speed in the player when possible. MachenVoice lets authors preview voices such as Aria (English - United States) or Ryan (English - United Kingdom) before export; the LMS should still expose speed controls after upload.
Slightly slower delivery often helps comprehension; adjust pacing with punctuation and sentence length before you rely on playback-speed sliders alone.
Low vision considerations
Screen magnification users may rely on TTS when eye fatigue sets in. Provide keyboard-accessible players and visible focus states in your web app.
Do not hide critical instructions inside audio only; always keep the text available and searchable.
Responsible claims for public sites
Do not market MachenVoice as a medical device or guaranteed dyslexia intervention. Position it as software that converts text you provide into audio you control.
If you serve schools, coordinate with accessibility coordinators and local policy on synthetic speech disclosure.
Workflow with MachenVoice
Chunk articles or chapters into blocks under 2,000 characters, generate MP3, and embed players next to the HTML text. Update both text and audio when content changes.
For internal training on inclusive design, pair this audio with our e-learning narrator tool and the script-writing guide so authors learn ear-first drafting.
Universal Design for Learning (UDL) alignment
UDL encourages multiple means of representation. Offering text plus optional TTS supports learners who decode slowly but does not remove the need for clear writing and instructor support.
Provide controls: play/pause, speed, and visible highlighting when your player supports it. Avoid autoplay with sound on public pages without a user gesture.
Classroom and workplace policies
Schools may require disclosure when assessments use synthetic readers. Check local accommodation plans before substituting TTS for human read-aloud in high-stakes testing.
Employers rolling out training should document that narration is synthetic so employees with hearing aids or cochlear implants can choose captions or transcripts.
Typography and layout that help everyone
Use at least 1.5 line height in HTML or PDF handouts, avoid all-caps paragraphs, and prefer sans-serif body fonts at comfortable sizes. MachenVoice cannot fix cramped PDFs—fix layout first, then narrate.
Break long pages with headings every few paragraphs so listeners can stop and resume without losing context.
Evaluating whether TTS helps a given reader
Run a short pilot: same passage with and without audio, then ask the reader which version they understood faster. Some people prefer human voice actors; others prefer consistent synthetic pacing.
Do not use comprehension scores from a single session as proof of clinical benefit; treat feedback as qualitative input for your content design.
Pairing with audiobooks and long reads
For long chapters, export MachenVoice MP3 per section and offer a download next to the HTML chapter. Podcast-style feeds are optional; many readers only need an on-page player.
When updating a chapter, bump the audio version in the filename so assistive-technology users know the narration matches the text.
Assistive technology compatibility
Screen readers read the DOM; embedded players should expose accessible names and keyboard-focusable controls. Do not trap focus inside a custom player without an obvious exit.
If you offer both TTS and a screen reader, avoid playing both at once by default. Let the user choose listen mode explicitly.
Color, contrast, and motion
Low vision users benefit from high-contrast themes and reduced motion settings. MachenVoice audio does not replace WCAG contrast requirements on your site template.
Avoid flashing visuals synchronized to speech beats; some readers are sensitive to motion while listening.
Training authors and moderators
Publish a short internal style guide: when to offer audio, how to write plain language, and how to disclose synthetic speech. Include a link to the Licenses page for commercial questions.
Moderators updating wiki pages should regenerate audio when they change a heading or warning box, not only body paragraphs, so listeners hear safety-critical edits.
Libraries, schools, and public-sector sites
Public libraries offering article audio should keep transcripts public and searchable for patrons who cannot use audio players. Cache MP3s with the same URL only when text is unchanged.
Government pages may require plain-language review before TTS publication; treat synthetic narration as another publishing step, not a shortcut around legal clearance.
Measuring impact without overclaiming
Track engagement metrics such as time on page and player plays, but avoid claiming medical outcomes from TTS alone. Share qualitative feedback from readers who chose listen mode.
Iterate on sentence length and voice speed when users report fatigue; small script edits in MachenVoice often beat buying new accessibility widgets.
Glossary for stakeholders
Text-to-speech converts written strings into audio files or streams. It is not the same as a screen reader, which reads interface elements aloud. MachenVoice is authoring software; your website player is delivery.
Use this distinction in RFPs so vendors do not promise “full accessibility” from TTS alone.
| Practice | Why it matters |
|---|---|
| Captions on all narrated video | Deaf and hard-of-hearing access |
| Text visible while audio plays | Multimodal reading support |
| User-controlled speed | Comprehension varies by person |
| No audio-only critical steps | Searchable, perceivable instructions |
| Plain language review | Reduces cognitive load for everyone |
| Synthetic speech disclosure | Trust and policy compliance |