-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Best practice document: Extracting data for TTS and a "reader mode" #69
Comments
I agree. A best practice document would be helpful even if TTS doesn't ultimately work out as a basis for Reader Mode. Improved and consistent TTS among reading systems would lower the expense of making an accessible ebook. Publishers who can't create audio overlays could rely on robust TTS to make compliant Epubs. End users who require smaller Epub files would benefit from an audio option without media overlays. And anecdotally, few publishers and users are satisfied with the current TTS experience. |
Research to do/Questions to ask:
|
Also overlap with the CSS algo for converting to plaintext. |
And work in ARIA/AccName... |
VitalSource seems to have a two-fold approach with a simplified and a detailed reading mode, as described by @rickj in the following comment: #72 (comment) This is exactly the kind of information that we're looking for to kickstart this joint effort on TTS and reader mode. |
Text-to-speech (TTS) is among the most popular features in reading apps and slowly creeping up as a must-have feature in Web browsers as well.
But despite the popularity and usefulness of TTS, there is no best practice document providing guidance for developers on how they should implement this feature.
The group working on accessibility for FXL publications has also identified that in addition to TTS, extracting text from an FXL resource could be used to provide a "reader mode" of the current page/spread, enabling users to adjust the text and layout to their needs.
For both TTS and a reader mode, reading systems need guidance about the way they should extract data from XHTML to build these alternate renderings:
accessModeSufficient
,readingOrder
,alternativeText
,longDescription
)The text was updated successfully, but these errors were encountered: