This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Feedback from the HTML Accessibility Task force on WebVTT as per http://lists.w3.org/Archives/Public/public-tt/2015Apr/0049.html We are concerned that too often in this document a feature's function can only be understood by parsing the provided algorithms. We would prefer plain language explanations be included. A specific case in point would be Sec. 6.1.
Note related bug: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28408 Section 6.1 has been resolved in the latest editor draft, see http://dev.w3.org/html5/webvtt/ , which was possible after some changes to the HTML specification were introduced. As for providing more "plain language explanations" - the WebVTT specification is mainly targeted at WebVTT UA and tool implementers and not at WebVTT authors (similar to the HTML specification). For author-related introductions, please refer e.g. to https://docs.webplatform.org/wiki/concepts/VTT_Captioning .
Marking as duplicate of bug 28408 since it also asks for improvement for authors. *** This bug has been marked as a duplicate of bug 28408 ***
We rely on external documents to provide an authoring guide.
The authoring guide was recovered from the sinking web platform docs and moved to the Wiki at https://www.w3.org/wiki/VTT_Concepts
MOVED TO GITHUB: https://github.com/w3c/webvtt/issues/427