<trackbot> Date: 17 May 2012

<JF> \

<JF> hmmm... her number has changed?

<JF> waves hi

<Judy> meeting: Media SubTeam of HTML5 A11Y Task Force

<JF> Meeting: HTML-A11Y teleconference

<JF> Chair: John_Foliot

<JF> Scribe: Janina_Sajka

<JF> agenda: this

<Judy> hi Silvia, sorry I cannot join you directly at this time, but thanks for continuing to work on this issue

hi Judy, no problem - thanks for getting us started

<JF> <video transcript="jf">

<JF> </video>

<JF> <transcript class="off-screen">

<JF> <a href="transcript.pdf">transcript</a>

<JF> </transcript>

<JF> <video transcript="jf">

<JF> </video>

<JF> <div class="off-screen">

<JF> <a href="transcript.pdf" id="jf">transcript</a>

… I would instead do this:

<JF> </div>

<video transcript="sp">

</video>

<trasncript id="sp" src="transcript.pdf"></transcript>

multiple links:

<video transcript="sp1 sp2">

</video>

<transcript id="sp1" src="trans1.pdf" lang="en"></transcript>

<transcript id="sp2" src="trans2.doc" lang="de"></transcript>

multiple links:

<video transcript="sp1 sp2">

</video>

<transcript id="sp1" src="trans1.pdf" lang="en"></transcript>

<transcript id="sp2" src="trans2.doc" lang="de"></transcript>

Question we are discussing: why we need the transcript element

My reply: I'd like a consistent way of authoring transcripts for all use cases

* URL off-page

* text on-page

* interactive transcript with video

* transcript-only (without video)

<JF> in this case:

<JF> <video transcript="jf">

<JF> </video>

<JF> <transcript class="off-screen">

<JF> <a href="transcript.html" id="jf">transcript</a>

<JF> </transcript>

<JF> scratch that

Since anchors can get focus, we'll try to avoid using anchors inside <transcript>

<JF> <video transcript="sp1">

so put the url directly on the <transcript> element

<JF> </video>

<JF> <transcript id="sp1" src="trans1.pdf" lang="en">

<JF> </transcript>

this instance would be rendered like a <a>

<JF> so: <transcript id="sp1" src="trans1.pdf" lang="en"></transcript>acts like a link

<JF> it would render a "control" (button, dropdown, equiv)

<video transcript="on-page">

</video>

<transcript lang="en" id="on-page">

This is the transcript for the above element.

</transcript>

<JF> how would that be populated dynamically?

JF explains a use case where the on-page transcript is rendered from an external html page

silvia: this can either be linked as above

<JF> so if dynamically populated, would be done via scripting

or if you really need to render it on page, you need to use JS

set the innerHTML of the <transcript> element to it

<JF> so we've covered the link scenario, and the static on screen scenario, what about interactive?

sp: interactive transcripts will be the killer app for video and will cause authors to want to create more captions

<JF> <transcript id="sp1" src="trans1.vtt" lang="en"></transcript>

rather:

<transcript id="sp1">

<track src="trans1.vtt" srlang="en">

</transcript>

that would be rendered on page as an interactive transcript

<JF> after looking at this, I think we have some solutions that work for accessiblity concerns

<JF> discoverability: the @transcript attribute will trigger some form of control - a button or menu dialog or (to be determined by device/platform considerations)

<JF> 2) option to consume or not consume: covered by discoverabiliyt/control above

<JF> 3) supports semantically rich content

I dropped out

<JF> can you try calling bck in?

my phone ran out of battery :-(

<JF> oh noe

it's been playing up and not showing the correct battery status - it may not be fully dead

<JF> ok, well we were wrapping up

<JF> next steps? update wiki?

<JF> I can make some contributes if you want

I can't dial back in, sorry

<JF> OK

I will want to completely rework that CP

<JF> OK, let me know how I can asssist

we have a lot more information now than when I wrote it

<JF> agreed

were you going to add to it?

<JF> I can

can you write a paragraph on why you think the approach is workable - as you started above?

<JF> I can add a section on accessiblity considerations and how/why this solves those issues

I'd like to add that after the tech descriptions so we have that viewpoint captured

<janina> I'll let the H5 CC's know we're agreed in principle. We need only to get it written up and socialized for objections, etc.

"only"!

<janina> We expect to have TF support by next Friday and a single CP for the WG.

<JF> Agreed. can you re-share the final wiki url?

it's the implementers I'm concerned about now...

<janina> Yes, that's the socializing task for next week.

sure, let's create a new one

<JF> OK, well if you start the page, I will go in tonight and add to it

<JF> leave me a place holder <grin>

will do, no problem

<JF> OK... are we done for now?

I'll email it to you

<JF> thank you

<janina> I'll push minutes

I think so … Janina?

<janina> Excellent stuff, Silvia!

<JF> let's call it a day. thank you silvia and janina

no worries - we need to get this right :-)

awesome, thanks everyone

and sorry for dropping out

<JF> no worries

I need to buy a new phone

or we use Google hangout next time!

<JF> lost the call

<janina> OK. We're done anyway!

<JF> trying your cell

<janina> Cell broke. My main 202.494 number is good

<JF> 7040?

<janina> I can push, if you like

<janina> Yes, Silvia, I will do minutes push

This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/we;ve coverd th elink/we've covered the link/
No ScribeNick specified.  Guessing ScribeNick: silvia
Found Scribe: Janina_Sajka

WARNING: No "Topic:" lines found.


WARNING: No "Present: ... " found!
Possibly Present: JF Judy P2 discoverability janina joined media rather silvia so sp trackbot
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

Found Date: 17 May 2012
Guessing minutes URL: http://www.w3.org/2012/05/17-media-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report