W3C home > Mailing lists > Public > public-html-a11y@w3.org > July 2015

[transcript] spliced media, advertising, etc

From: <chaals@yandex-team.ru>
Date: Sun, 05 Jul 2015 13:07:25 +0200
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-Id: <57591436094445@webcorp02d.yandex-team.ru>
Hi,

this is for ACTION-317 - https://www.w3.org/WAI/PF/HTML/track/actions/317

a pretty common use case for timed media involves splicing things together. Key examples include putting advertising into television or radio broadcasts. Another case is what MSE does, dynamically selecting content to match e.g. fluctuating bandwidth.

I don't think the latter case implies anything new - the purpose of MSE is to make the same content available, perhaps at different quality levels.

We also *expect* transcripts to be a pretty basic version of the content in terms of requirements - beyond streaming text formats, it isn't clear that it might adapt somehow and change (as opposed to selecting different types of transcript from the beginning, e.g. using a simplified text.

The first case is more difficult. My thinking is that anyone who can insert material into the media element would have a technical capacity to do the same for a transcript (and for that matter for captions, etc). 

If the insertion is done live, and not determined in advance, there is more or less nothing that can be done to change a transcript after the user has it. Which means the linking mechanism isn't the most important part - if someone tries this, the approach that occurs most obviously to me is to chain together the first transcript, and then dynamically add a link at the end of each transcript to the next part.

So my current thinking is that there is nothing that should be changed in relation to this use case.

Just on the off-chance, I have raised ISSUE-3 - https://www.w3.org/WAI/PF/HTML/track/issues/3

Thoughts?

cheers

Chaals

--
Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Sunday, 5 July 2015 11:07:59 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 5 July 2015 11:07:59 UTC