-
Notifications
You must be signed in to change notification settings - Fork 9
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
Proposed edits to section 5.11 Accessibility #87
Comments
Maybe just remove "content creators should" to avoid an rfc keyword in the section. If I were to really nitpick, I'd probably wonder why we need to first sentence. It doesn't seem to go anywhere. Alternatively, maybe it could be given some small context:
Or something like that. |
I like that better. I would eliminate "Although this specification covers the audio playback need", because it doesn't for example allow for chunking the audio content at a meaningful sub-chapter level, e.g. phrase navigation. This is use case where an audiobook produced according to this spec needs a sync overlay to enhance its accessibility. So maybe just say, for the start of the 2nd para:
What do you think? |
Right now, section 5.11 makes references to the work of the Sync Media for Publications CG, and acknowledges that work has not yet been stabilized. The references include specific details such as mime type, file extension, and spec name.
I would like to propose that we avoid referencing specifics and instead use this replacement text for Section 5.11:
"
5.11 Accessibility
This section is non-normative.
The history of the audiobook is rooted in the world of accessibility. To make publications fully accessible, content creators should refer to the Synchronized Multimedia for Publications Community Group regarding creating synchronized accessible content and incorporating it into an Audiobook.
Alternatively, a content creator can provide the text equivalent as HTML [html] resources in the resources.
"
Furthermore, I would delete the Editor's Note as well as Example 13 and leave Example 14.
The text was updated successfully, but these errors were encountered: