Changes

Jump to: navigation, search

Accessibility/Video a11y requirements

38 bytes removed, 08:05, 8 November 2008
m
Requirements for archiving
==== metadata & semantic annotations ====
** (structured) annotations that describe the scene and semantics** similar to audio description, but tends to be structured along different fields** may also be a random note left by somebody to leave a comment
Discussion:
** there are different types of annotations that are typically handled differently** RDF type annotations, e.g. is not rendered as text, but available for machine processing only** visible annotations are short pieces of text that are attached through speech/thought bubbles, or as notes ** visible annotations require a time range, on-screen position, text styling, and annotation box styling** visible annotations could also contain graphics, but mostly simple formatting such as for notes is required
MULTIPLEX INTO OGG: as timed text track
==== story board ====
** sequence of images that represent the original way in which the video was scripted** if it is possible to align it with the resulting video, provides insights into the video planning and production** if it cannot be time-aligned with the video, it should be referenced separately (text with url on webpage)
MULTIPLEX INTO OGG: as timed image track
==== transcript ====
** textual description of everything that happens in the video** basically similar to what captions and audio annotations provide together** it is probably better to keep as much of the different types of annotations separate as possible and call the complete textual annotations available to a audio/video file its "transcript"** if it cannot be time-aligned with the video, it should be referenced separately (text with url on webpage)
Discussion:
** transcripts are mostly not displayed on top of the video, but in parallel to it with the current text block selected in sync to the video** rich formatting is possible** wiki-style editing is often encouraged** often there are hyperlinks in transcripts
MULTIPLEX INTO OGG: as timed text track
==== script ====
** original description of the video for production purposes** if it is possible to align it with the resulting video, provides insights into the video planning and production** if it cannot be time-aligned with the video, it should be referenced separately (text with url on webpage)
Discussion:
** same as transcript
MULTIPLEX INTO OGG: as timed text track
==== lyrics ====
** for music files, a special type of transcript / subtitle format has evolved - the [http://en.wikipedia.org/wiki/Time_tag lyrics .lrc] file format** this is also a text codec and can be time-aligned with audio / video
Discussion:
** same as transcript
MULTIPLEX INTO OGG: as timed text track
==== titles / credits ====
** most videos have titles and/or credits at the start/end respectively** where it is possible to make these available as separate text rather than burnt in (i.e. open), they should be made part of a transcript
Discussion:
** same as transcript
MULTIPLEX INTO OGG: as timed text track
==== ticker text ====
** news often have a ticker text at the bottom of the screen** ticker text always stays at the same position and scrolls through from left to right** the ticker text often has small ads in it, too** there are often graphics included
MULTIPLEX INTO OGG: as timed text track
==== image maps ====
** advertisers in particular want to mark regions on online video with hyperlinks and some scroll-over text, which is linked to the region** there is the active region and there is the region for the scroll-over text** there can be text & graphics in the scroll-over text box** can be placed anywhere on top of the video screen** the active region is typically empty and lights up upon scroll-over
MULTIPLEX INTO OGG: as timed text track
401
edits

Navigation menu