Media Subteam: Draft for reference content publication

This document enumerates the key particulars required to create a complete
HTML5 media content publication. The purpose of this content publication will
be to:

1.)	Serve as a model for content authors demonstrating media publication
which includes support of persons with disabilities who require alternate
media representations; and
2.)	Provide user agent developers sufficient content to fully test both
primary and alternative media support in their products.

The content publication envisioned in this document implements the
requirements enumerated in the W3C note track document:

Media Accessibility User Requirements
http://www.w3.org/TR/media-accessibility-reqs/

Primary Media Resource
It is assumed the primary media resource will include both video and audio.
However, a yet more suitable primary resource for this content publication
would also provide audio tracks in at least two languages. If multiple
languages are supported by the primary resource, the following alternative
media representations are required for each language provided by the primary
media resource.

Described video
Audio recording of a human describing the video recorded as a separate track. May be
monaural.

Text video description
Should be rich text markup including hyperlinks
Note that texted descriptions are always likely to function as extended text
descriptions for reasons given in the Requirements note.

Clean audio
Note that this alternative media type will sometimes replace the primary audio
resource.  Because the highest quality clean audio is obtained during
production, we should try to obtain a content source for which a clean audio
mix is already available, or for which master, multi-track audio recordings
are available from which a clean audio mix can be created.

Content navigation by content structure
This feature is the primary reason a 1, 2 or 3 minute primary resource will be
inadequate. We require at least two nested levels, and preferably three nested
levels of content structure to effectivly demonstrate this feature.

Captioning
Should be rich text markup including hyperlinks
Should also demonstrate "Enhanced Captioning" as defined by the Requirements
note.

Sign translation
This will be a second video track--additional to the primary video resource.

Transcripts
[find href to former two proposals for realizing transcript support]



-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina@asterisk.rednote.net
		Email:	janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,	Protocols & Formats	http://www.w3.org/wai/pf
	Indie UI			http://www.w3.org/WAI/IndieUI/

Received on Monday, 28 April 2014 13:36:52 UTC