An additional listening option for selected content
Some visitors prefer to hear a long article; others alternate between reading and listening. People who find reading difficult may welcome another option. Suitability depends on the person, content and situation. A narration feature does not establish a medical benefit or guarantee better learning.
With Verbison, editors prepare the spoken text, review the recording and publish the required languages. Playback uses that stored file. This is an editorial edition, distinct from a browser feature reading currently selected text aloud.
An audio edition is not a screen reader
Screen readers expose the structure and controls of an interface as well as its text. An article recording does not provide that navigation. Headings, links, forms and status messages must still work with assistive technology. W3C WAI describes accessibility as depending on content, browsers, media players and assistive tools working together.
People may already use reading and adaptation features in their browser or operating system. An optional website player should complement those tools without obstructing their use.
How synchronised highlighting supports orientation
Verbison displays the spoken sentence in the player and highlights its corresponding source passage. With Spanish audio on a German page, listeners can still locate the German section being discussed. This content connection is not an automatic word-by-word translation.
Highlighting helps people find a passage again. It does not replace accessible text structure, useful image descriptions or explanations of complex tables. If narration has deliberately been shortened, make its scope clear. Recording, visible text and intended meaning should agree.
Practical checks for website owners
- Keyboard: Can people reach and operate play, pause, language selection and other offered controls without a mouse? WCAG 2.1.1 addresses keyboard access.
- Focus: Can people see which control has focus, and can they reach it? WCAG 2.4.7 explains visible keyboard focus.
- Audio: Does playback begin deliberately and pause easily? Unexpected sound can interfere with screen readers; WCAG 1.4.2 explains audio control.
- Highlight: Does orientation remain understandable without relying on one colour? WCAG 1.4.1 addresses information conveyed by colour alone.
- Layout: On a small screen, does the player leave forms, cookie settings and important text available? Check zoom and the actual reading order too.
- Content: Are sources, warnings and visual information still accessible? Review the complete recording and repeat the check after relevant changes.
No automatic claim of conformance
This checklist is a practical starting point, not a complete WCAG audit. Adding a read-aloud widget does not establish whole-site conformance or fulfilment of legal requirements. A reliable assessment needs the actual site, applicable requirements and appropriate testing.
Verbison provides editorially controlled website audio. Translation, voices and highlighting are product features. Therapeutic effects and blanket accessibility guarantees are not part of that promise.
A useful first test
Choose a representative article and test it with people who use different interaction methods. Observe whether they find the audio, operate the player and understand its connection to the text. A concrete obstacle is more useful than a generic quality label.
See integration for the embed, workflow overview for text, language and publication steps, and audio for education for educational scenarios.
Sources and further reading
- W3C WAI: Components of web accessibility
- W3C WAI: Tools and techniques
- WCAG 2.1.1: Keyboard
- WCAG 2.4.7: Focus Visible
- WCAG 1.4.2: Audio Control
- WCAG 1.4.1: Use of Color
These W3C explanations address individual requirements. They do not certify Verbison or your website.