346
edits
Accessibility/Captioning Work Plan: Difference between revisions
Jump to navigation
Jump to search
Accessibility/Captioning Work Plan (view source)
Revision as of 09:40, 4 August 2008
, 4 August 2008→Work plan
| Line 12: | Line 12: | ||
##social caption creation (This poses very different requirements than the idea of making video files intrinsically accessible. [[User:Hsivonen|Hsivonen]] 09:06, 4 August 2008 (UTC)) | ##social caption creation (This poses very different requirements than the idea of making video files intrinsically accessible. [[User:Hsivonen|Hsivonen]] 09:06, 4 August 2008 (UTC)) | ||
##metadata indicating changes in captioning language for search and Braille. (Google seems to be doing better by ignoring author-entered language metadata. Is rendering foreign words into Braille strong enough an use case to justify the complexity of supporting this and authoring with this data. [[User:Hsivonen|Hsivonen]] 09:06, 4 August 2008 (UTC)) | ##metadata indicating changes in captioning language for search and Braille. (Google seems to be doing better by ignoring author-entered language metadata. Is rendering foreign words into Braille strong enough an use case to justify the complexity of supporting this and authoring with this data. [[User:Hsivonen|Hsivonen]] 09:06, 4 August 2008 (UTC)) | ||
##semantics and style, etc. (This seems like a pretty big departure from baseline established by TV captioning. [[User:Hsivonen|Hsivonen]] 09:06, 4 August 2008 (UTC)) | ##semantics and style, etc. (This seems like a pretty big departure from baseline established by TV captioning. [[User:Hsivonen|Hsivonen]] 09:06, 4 August 2008 (UTC)) [[User:aaronlev|aaronlev]] I'm not sure -- there are some higher level things such as embedding of a musical note graphic to indicate music. I believe that captioning is moving toward expressing more complex background information. | ||
# Ensure captioning solution is compatible with current authoring and if possible, video conversion tools, so that current and future content can easily use the solution | # Ensure captioning solution is compatible with current authoring and if possible, video conversion tools, so that current and future content can easily use the solution | ||
# Determine what can be done about supporting captioning when an external back end (gstreamer, QuickTime, DirectShow) is in use. (MP4 containers are the most likely external back end case, so 3GPP Timed Text is a potential format candidate in that case.) | # Determine what can be done about supporting captioning when an external back end (gstreamer, QuickTime, DirectShow) is in use. (MP4 containers are the most likely external back end case, so 3GPP Timed Text is a potential format candidate in that case.) | ||
| Line 18: | Line 18: | ||
# Build documentation for developers and content creators | # Build documentation for developers and content creators | ||
# Test solutions and file bugs in databases for each browser to drive the necessary work. Attach relevant test cases and documentation. Make sure the developers know what to fix. | # Test solutions and file bugs in databases for each browser to drive the necessary work. Attach relevant test cases and documentation. Make sure the developers know what to fix. | ||
= Measurements of Success (previous list) = | = Measurements of Success (previous list) = | ||