See also: IRC log
trackbot, associate this channel with #html-a11y
<trackbot> Associated this channel with #html-a11y.
<trackbot> Date: 28 April 2014
<scribe> Meeting: HTML Accessibility Task Force Media Sub-Group
<scribe> scribe: MarkS
<kaz> Munich workshop minutes, March 2014
MS: Talked with Kaz and Daniel Davis from Web and TV IG
<kaz> http://www.w3.org/2011/09/webtv/minutes.html#session4 Hollywood ws minutes
KA: we've had a number of
workshops. At the last one we had a specific session on
accessibility. Work tends to focus on captioning and subtitles.
There is some discussion that we need to consider additional
things for TV accessibility
... I mentioned that Mark was interested in collaborating with
our group
MS: do you have any reference to your current work?
<kaz> use cases from the 1st iteration
KA: we haven't really started
second iteration yet, but here is link to our first iteration
of work.
... second screen applications.
... how to share content and search content.
JS: in a group setting, second screen becomes very important. You can tailor the accessibility needed to individuals in the group.
KA: there is a community group for second screen discussions. There is talk of a special API for this.
<aardrian> Second Screen Presentation Community Group: http://www.w3.org/community/webscreens/
JS: we have our Media Accessibility User Requirements document. We have taken up that document again, a new working draft of that document should be published in June. Depending on the number of comments, we may do a Last Call in August and hopefully become a W3C note in the fall, ahead of TPAC
KA: Would be a good idea to have a joint meeting at TPAC
JS: would be good to include use
cases based on the scenarios in the accessibility
document.
... we are also looking to work with members to find content
that we can release into public domain, and demonstrate
accessible media.
... navigating by structure, sign language translation,
multiple languages.
KA: would this include DAISY and ebooks?
JS: the navigation model in those
applies to media as well. Not just next and previous, but more
granular control.
... need to be able to adjust the granularity
MS: should we talk about a work flow? want to make sure we don't miss opportunity to contribute to Web and TV Use Cases
KA: It makes sense for me to provide use cases based on your user requirements document.
MS: and we would be glad to review that work.
JS: What is the timeline for this second iteration of work
KA: policy and procedure is to
put ideas on the groups wiki, then hold teleconferences, then
to publish the document as a group note. Usually takes 6
months.
... just getting started on second iteration.
... next call is on Wednesday, 30 Apr.. I can talk about this
idea on that call.
... I would like to bring this to the group chairs to get their
feedback.
... I remember discussing the media requirements document 3
years ago. I have reviewed this document again and this work is
great. We need to consider this again.
JS: We worked very hard to make
sure it was comprehensive.
... hope to publish it as a note soon.
... good conversations in 2011 regarding techniques for
implementing these features.
KA: we also have a Community Group for tuner controls, which also have accessibility implications. Just an API might not be enough.
JS: We agreed that this should be done and all we need to do is add your name to the document.
-> http://lists.w3.org/Archives/Public/public-html-a11y/2014Apr/0081.html suggested text
JS: suggest we drop one sentence
and add a couple more
... problem is that user is in charge of how fast TTS works. no
way for the author to know, unless its short text description,
how much time there is to get it in.
... every text description, as to be thought of as extended
text description, which would require pausing the video
... in a situation where the user is in a group environment,
this could get confusing
... we can make them reviewable "offline"
... as a text file
... good discussion in 2011 regarding options for user control
of this feature.
... options to auto pause, or truncate, etc.
KA: would require very precise time sync?
JS: yes, not only precise time,
but knowing whether TTS is still talking and auto-pause the
video
... WGBH brought this to our attention using a courseware demo.
The description is elaborate enough that the video needs to be
paused to get the description in.
... would be appropriate for student to auto pause when
watching by themselves, but not in a class setting.
... user decides how fast the TTS goes
KA: important point.
RESOLUTION: Accept proposed text found in http://lists.w3.org/Archives/Public/public-html-a11y/2014Apr/0081.html.
MS: I can make that change
then.
... the next issue was regarding Clean Audio and is in the same
email
JS: that one turned out to be
simple. In our last call, in a private viewing situation, the
user would want the clean audio version to be the
primary/replace the primary audio.
... in a group situation, they would probably wear
headphones.
... viewing alone, they would probably want to set their TV to
play only the clean audio, and drop the primary audio
track.
... added a line that clarified that point.
RESOLUTION: Accept proposed text found in http://lists.w3.org/Archives/Public/public-html-a11y/2014Apr/0081.html.
MS: I can make that edit as well
-> http://lists.w3.org/Archives/Public/public-html-a11y/2014Apr/0070.html Suggested rewrite
AR: makes sense to me
JS: I am in favor of this change
MS: I will make this change in the doucment
MS: I spoke with Christian Voegler who wanted to know the background on this particular reguirement.
...I did some digging in old minutes and records and found that Siliva Pheiffer added the text originally
...I contacted her and she said that she took it directly from CEA708 but that we could remove it if no one thought it was necessary.
JS: I don't think this was
controversial when we originally added it.
... "author proposes and user disposes" is the paradigm we
should support.
http://www.w3.org/TR/media-accessibility-reqs/#ECC-4
JS: i think the more interesting part is the concept of overlapping speech. traditional TTY communications.
RESOLUTION: keep ECC-4 as is.
JS: If you caption an Opera, you
should at least be able to see the overlapping words.
... should be overlapping and should be able to pause.
JS: Michael and I talked about
this. Once comments are done being processed. Take about a week
to respond to commenters, another 2 weeks to allow for
correspondence, and then another week to get the edits in, then
a week for publication prep, etc. We thought June 16 was a good
target date, considering the moratorium. Depending how that
goes, a Last Call sometime in august.
... move to note status ahead of TPAC.
... would need to convey to Shawn and EO to conclude their work
in time for that Last Call publication.
MS: I can talk to EO.
JS: Michael had already made those minutes public. They are available here: http://www.w3.org/2013/11/12-media-minutes
https://www.w3.org/WAI/PF/HTML/wiki/Current_Bug_Triage_Issues
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12794
JS: I think putting this back on John Foliot is a good thing. What is different about this now is that it could be solved by an ARIA feature, perhaps something to be included in ARIA 1.1, which should get a new draft in MAY