RE: [media] raising bugs in W3C bug tracker for LC

I've updated the table per my action item. There are a few remaining TBD's but I think they are mainly controlled by UAAG rather than WCAG, so I've left those for now.

As a result of this exercise, I think we need to check the spec and possibly open additional bugs on:

Providing visible indication that descriptions and captions are available.

Allowing the user to independently adjust the volumes of the audio description and original soundtracks.

Allowing the user to control playback timing in order to have more time to understand the material, read a lengthy description or caption  (I think this one is mostly covered by http://dev.w3.org/html5/spec/video.html#dom-media-playbackrate but we need possibly to add some text for when the timed text itself can control the playback rate)

Support the isolation of speech from other background sounds in AV media

Support user control over the visual presentation of caption text.


From: public-html-a11y-request@w3.org [mailto:public-html-a11y-request@w3.org] On Behalf Of Silvia Pfeiffer
Sent: 23 September 2010 05:52
To: HTML Accessibility Task Force
Subject: Re: [media] raising bugs in W3C bug tracker for LC

On Thu, Sep 16, 2010 at 10:59 PM, Silvia Pfeiffer <silviapfeiffer1@gmail.com<mailto:silviapfeiffer1@gmail.com>> wrote:
Hi media a11y ppl,

I just came across the note that Mike Smith has forward to the HTML WG:
On Thu, Sep 16, 2010 at 8:30 PM, Michael(tm) Smith <mike@w3.org<mailto:mike@w3.org>> wrote:
I want to remind members of the group that we are having our regular
weekly telcon of the Accessibility TF as scheduled this week --
and are using the call time during the next two weeks to make sure
we have not let anything slip between the cracks as far as making
sure we have raised all necessary bugs prior to October 1st.

I now wonder if we should discuss this also in the media a11y subgroup and ascertain all the things that we want solutions for are actually raised in the HTML WG bug tracker. I know we have Issue-9, but is it actually going to be enough?

As it stands, we have the following bugs:

1. On Markup for including external text tracks

"Introduce declarative markup to associate timed text resources with media elements"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9471
-> for which I have already suggested moving much of the WHATWG proposal into the W3C version.


2. On handling multitrack media resources

"Handling of additional tracks of a multitrack audio/video resource"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9452
-> which has been reflected to us for proposing a solution; this should be our next focus for technical discussion. It will include a solution for "clear audio" and for "sign translation", so cover a fair bit of ground.


3. Several on WebSRT

"There is not a clear difference between "subtitles" and "captions". These are mostly used to describe "closed captions" (binary transmissions in TV broadcasts) vs "subtitles" (text files), as far as I know"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9773

"Allowing A WebSRT voice declaration when the cue payload is WebSRT metadata text does not make sense, I think"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10619

"..multiple cues are supported at once. But many SRT players don't actually support more than one SRT subtitle at once.."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9777

"Percentages for text positioning don't seem better than using the actual video dimensions"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9776

---

So, the only thing I can see missing is a solution for the requirement area "Content navigation by content structure". We haven't discussed any potential technical approaches to this yet, but I think it is important enough to include that in this version of the HTML5 draft. It may well be that all we need is a means to switch easily between available timed text tracks and to make direct URLs to cues available. But we haven't got into the depth of this and I think we may need to make sure that there is a placeholder for this discussion in the HTML5 bug tracker.


After today's discussion I have added the following bug into the HTML5 bug tracker: http://www.w3.org/Bugs/Public/show_bug.cgi?id=10693 .

This should satisfy both, ACTION-63 and ACTION-64.

Cheers,
Silvia.