E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 2 (In chronological order)

From: John Foliot
Date: Wed, Oct 08 2008 2:40PM
Subject: Captioning Web Videos - and some feedback from you all please
No previous message | Next message →

Hello All!

Apologies if you get this multiple times, as I am sending it out to a
number of web accessibility lists.

Creating captioned web media is something that is not easy to do right now
- this we already know. Getting captioned iTunes media is even harder,
although it is possible, as the following link(s) will illustrate:

http://acomp.stanford.edu/atl/atr/podcast/atr13.mov
http://acomp.stanford.edu/atl/atr/podcast/atr12.mov

(these are both also available via the iTunes store:
http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewPodcast?id=272900846
)

The exciting thing is however, that it can be done, although it remains a
bit of a manual challenge to produce these files - a simple "turn-key"
solution really doesn't exist right now (but there *is* work being done in
this area).

Along with the challenge of the technical part of this process however is
some other, less technical aspects, and the purpose of this note: In the
first referenced video above (atr13.mov) the video stream features some
rap lyrics in foreign languages. For the purpose of the
caption/transcription, my associate Kim simply noted "Japanese Rap",
"German Rap", etc. Given that she's already adding to her work flow by
ensuring her podcasts are now captioned, I congratulated her on a job well
done and started telling everyone about the files above.

But the question of multi-lingual content within a caption file remains
one that I am unsure of, exactly. Is this as much a "policy" kind of
question as it is one of technical discussion:

1) should we provide the foreign transcript in the caption file? (this
raises questions of i11n as well, especially with the Japanese rap and
foreign character sets)

2) should we provide, instead, a translation of the rap? (even if it is
somewhat out of context; plus then we are providing information that
non-caption choice users are not getting, so is this right?)

3) is Kim's choice of simply noting "Japanese Rap" or "German Rap"
sufficient?

4) What kind of support do the various media players have for i11n
switching on the fly? (If in fact this is what needs to happen, or will
all the foreign text/character sets simply follow through from the initial
transcript/caption file? - I am thinking of alternative output as well -
Braille for example). Can we (should we) be thinking about the lang
attribute here (DFXP can accept it) - and if yes, how, and will, Adaptive
Technology be able to take advantage of it?

5) are there any other aspects of multi-language multi-media that I've
overlooked that we should be thinking about?

Now I suppose that these questions are also ones posed within the
caption/transcription community already (TV and Movie for example), but I
have not found any definitive information about this so far (in my limited
Google quest), and the delivery via the web of multi-media has its own
unique abilities and constraints that other forms of media delivery may or
may not share.

So... thoughts? Comments? Ideas?

Realizing that you might not subscribe to all of the lists I'm sending
this out to, I will recap the discussions on Friday, Oct. 10th.

Thanks in advance for your participation

JF

From: Keith Parks
Date: Mon, Oct 13 2008 5:10PM
Subject: Re: Captioning Web Videos - and some feedback from you all please
← Previous message | No next message

This may be Old News, but I'll take a shot...

On Oct 8, 2008, at 1:36 PM, John Foliot wrote:

> [snip...]
>
> But the question of multi-lingual content within a caption file
> remains
> one that I am unsure of, exactly. Is this as much a "policy" kind of
> question as it is one of technical discussion:
>
> 1) should we provide the foreign transcript in the caption file? (this
> raises questions of i11n as well, especially with the Japanese rap and
> foreign character sets)
>
> 2) should we provide, instead, a translation of the rap? (even if it
> is
> somewhat out of context; plus then we are providing information that
> non-caption choice users are not getting, so is this right?)
>
> 3) is Kim's choice of simply noting "Japanese Rap" or "German Rap"
> sufficient?


John,

IMHO, strictly from an accessibility standpoint, I think the way she
handles it would be not only sufficient, but the proper way of
providing text-equivalent of the audio information in the multimedia
presentation. In fact, providing translation could be seen as an
editorial distortion/modification of the content, it seems.

(With the caveat that in this case the German is so rudimentary,
combined with the fact that there are some shared word roots between
German and English, that many English-only speakers are likely to
understand *a bit* of the rap. (At least here in California, where we
regularly get to hear The Governator speak.) Not so for the Japanese
and Portuguese, due to the sound quality if nothing else.)

Using the caption function to provide translation *could* be a nice
use of the technology, but would be exceeding the requirements, and
might require the consent of the speaker, since it would add content
to the presentation that the speaker may not have wanted available or
revealed. (In other words, if a translation of the non-English
material was to be part of their presentation, they would have
provided it.)

My 2¢,

Keith

******************************
Keith Parks
Graphic Designer/Web Designer
Student Affairs Communications Services
San Diego State University
San Diego, CA 92182-7444
(619) 594-1046
mailto: = EMAIL ADDRESS REMOVED =
http://www.sa.sdsu.edu/communications

http://kparks.deviantart.com/gallery
----------------------------------------------------------

A riddle wrapped in a mystery inside an enigma, served with a side of
slaw.