A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
Video Overlay: Difference between revisions
Jump to navigation
Jump to search
(stub except the references) |
|||
| Line 44: | Line 44: | ||
== References == | == References == | ||
Silvia Pfeiffer's blog posts: | Silvia Pfeiffer's blog posts: | ||
* http://blog.gingertech.net/2009/07/14/more-video-accessibility-work/ | * [http://blog.gingertech.net/2009/07/14/more-video-accessibility-work/ More video accessibility work] | ||
* http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/ | * [http://blog.gingertech.net/2009/07/29/first-experiments-with-itext/ First experiments with itext] | ||
* http://blog.gingertech.net/2009/08/03/aspects-of-video-accessibility/ | * [http://blog.gingertech.net/2009/08/03/aspects-of-video-accessibility/ The different aspects of video accessibility] | ||
* http://blog.gingertech.net/2009/10/06/new-proposal-for-captions-and-other-timed-text-for-html5/ | * [http://blog.gingertech.net/2009/10/06/new-proposal-for-captions-and-other-timed-text-for-html5/ New proposal for captions and other timed text for HTML5] | ||
* http://blog.gingertech.net/2009/11/23/model-of-a-time-linear-media-resource/ | * [http://blog.gingertech.net/2009/11/23/model-of-a-time-linear-media-resource/ The model of a time-linear media resource for HTML5] | ||
* http://blog.gingertech.net/2009/11/25/manifests-exposing-structure-of-a-composite-media-resource/ | * [http://blog.gingertech.net/2009/11/25/manifests-exposing-structure-of-a-composite-media-resource/ Manifests for exposing the structure of a Composite Media Resource] | ||
Silvia Pfeiffer's <itext> proposals: | Silvia Pfeiffer's <itext> proposals: | ||
* [https://wiki.mozilla.org/Accessibility/HTML5_captions HTML5 captions] ([https://wiki.mozilla.org/Accessibility/Experiment1_feedback feedback]) | * [https://wiki.mozilla.org/Accessibility/HTML5_captions HTML5 captions] ([https://wiki.mozilla.org/Accessibility/Experiment1_feedback feedback]) | ||
* [https://wiki.mozilla.org/Accessibility/HTML5_captions_v2 HTML5 captions v2] | * [https://wiki.mozilla.org/Accessibility/HTML5_captions_v2 HTML5 captions v2] | ||
Mailing lists: | Mailing lists: | ||
* [http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2008-May/014887.html re-thinking "cue ranges"] | * [http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2008-May/014887.html re-thinking "cue ranges"] from David Singer (Apple) | ||
* [http://lists.w3.org/Archives/Public/public-html-a11y/2009Nov/0098.html initial <overlay> suggestion] | * [http://lists.w3.org/Archives/Public/public-html-a11y/2009Nov/0089.html timing model of the media resource in HTML5] from Silvia Pfeiffer | ||
* [http://lists.w3.org/Archives/Public/public-html-a11y/2009Nov/0098.html initial <overlay> suggestion] from Philip Jägenstedt (Opera) with feedback from Eric Carlson (Apple) | |||
[[Category:Feature Request|empty Template]] | [[Category:Feature Request|empty Template]] | ||
Revision as of 11:24, 28 November 2009
<overlay> is a proposal to display and style subtitles/captions for <video> in a uniform way, regardless of whether they are in-band or from an external resource. It also doubles as a container to overlay arbitrary (HTML) content on a <video>, enabling advanced scripted overlays such as karaoke animations or visual annotations.
Background
Use Case Description
Complete description of the use case.
Current Limitations
HTML5 currently lacks convenient markup and interfaces to handle at least three things:
- Syncing and displaying external subtitles/captions with <video>
- Styling in-band subtitles/captions from media resources
- Placing
Current Usage and Workarounds
Some evidence that this feature is desperately needed on the web. You may provide a separate examples page for listing these.
Benefits
Explanation of how and why new markup would be useful.
Requests for this Feature
- Source
I would like this feature ...
Proposed Solutions
My Solution
- Brief description of the solution and of how it address the problem at hand.
Processing Model
- Explanation of the changes introduced by this solution. It explains how the document is processed, and how errors are handled. This should be very clear, including things such as event timing if the solution involves events, how to create graphs representing the data in the case of semantic proposals, etc.
Limitations
- Cases not covered by this solution in relation to the problem description; other problems with this solution, if any.
Implementation
- Description of how and why browser vendors would take advantage of this feature.
Adoption
- Reasons why page authors would use this solution.
References
Silvia Pfeiffer's blog posts:
- More video accessibility work
- First experiments with itext
- The different aspects of video accessibility
- New proposal for captions and other timed text for HTML5
- The model of a time-linear media resource for HTML5
- Manifests for exposing the structure of a Composite Media Resource
Silvia Pfeiffer's <itext> proposals:
Mailing lists:
- re-thinking "cue ranges" from David Singer (Apple)
- timing model of the media resource in HTML5 from Silvia Pfeiffer
- initial <overlay> suggestion from Philip Jägenstedt (Opera) with feedback from Eric Carlson (Apple)