Created issue 'All Media Elements should have the ability to have both short and longer textual descriptions associated to the element' nickname media-descriptions owned by Sam Ruby on product HTML 5 spec, description 'Related to:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12228
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12794
Summary: WCAG 2 requires that authors "Provide text alternatives for any
non-text content so that it can be changed into other forms people need,
such as large print, braille, speech, symbols or simpler language."
Currently, the specification does not allow for a programmatic means of
associating both short and long textual descriptions to these assets while
still respecting the design need/requirement for not having those
(redundant) textual descriptions on screen. Suggestions of placing that
text inside of the <video> (or <audio>) element(s) does not suffice, as the
specification clearly states:
"Note: In particular, this content is not intended to address
accessibility concerns. To make video content accessible to the blind, deaf,
and those with other physical or cognitive disabilities, authors are
expected to provide alternative media streams and/or to embed accessibility
aids (such as caption or subtitle tracks, audio description tracks, or
sign-language overlays) into their media streams."
http://www.w3.org/TR/html5/video.html#video
The requirement is the ability to "embed" the long and short textual
descriptions in the media streams.
Note: Possibly related to Issue 30 (Status: Open) and Issue 142 (Status:
Formal Objection)' non-public/html/wg/tracker/issues/203#2012-01-19T14:26:19Z2012-01-19T14:26:19ZSam Ruby

2012-01-19 14:26:19: Created issue 'All Media Elements should have the ability to have both short and longer textual descriptions associated to the element' nickname media-descriptions owned by Sam Ruby on product HTML 5 spec, description 'Related to:

Summary: WCAG 2 requires that authors "Provide text alternatives for any
non-text content so that it can be changed into other forms people need,
such as large print, braille, speech, symbols or simpler language."

Currently, the specification does not allow for a programmatic means of
associating both short and long textual descriptions to these assets while
still respecting the design need/requirement for not having those
(redundant) textual descriptions on screen. Suggestions of placing that
text inside of the <video> (or <audio>) element(s) does not suffice, as the
specification clearly states:

"Note: In particular, this content is not intended to address
accessibility concerns. To make video content accessible to the blind, deaf,
and those with other physical or cognitive disabilities, authors are
expected to provide alternative media streams and/or to embed accessibility
aids (such as caption or subtitle tracks, audio description tracks, or
sign-language overlays) into their media streams."http://www.w3.org/TR/html5/video.html#video

The requirement is the ability to "embed" the long and short textual
descriptions in the media streams.