14:44:47 <RRSAgent> RRSAgent has joined #html-a11y-media
14:44:47 <RRSAgent> logging to http://www.w3.org/2014/04/28-html-a11y-media-irc
14:47:09 <MarkS> trackbot, associate this channel with #html-a11y
14:47:09 <trackbot> Associated this channel with #html-a11y.
14:47:15 <MarkS> trackbot, start meeting
14:47:17 <trackbot> RRSAgent, make logs world
14:47:19 <trackbot> Zakim, this will be 2119
14:47:19 <Zakim> ok, trackbot; I see WAI_HTML AT()11:00AM scheduled to start in 13 minutes
14:47:20 <trackbot> Meeting: HTML Accessibility Task Force Teleconference
14:47:20 <trackbot> Date: 28 April 2014
14:47:34 <MarkS> agenda?
14:47:42 <MarkS> zakim, clear agenda
14:47:42 <Zakim> agenda cleared
14:47:59 <MarkS> Meeting: HTML Accessibility Task Force Media Sub-Group
14:47:59 <MarkS> Chair: Mark Sadecki
14:47:59 <MarkS> agenda+ Identify Scribe
14:47:59 <MarkS> agenda+ Web & TV IG: Collaboration on Use Cases and Requirements (10 min)
14:47:59 <MarkS> agenda+ Media Accessibility User Requirements (Continued) (30 min)
14:48:00 <MarkS> agenda+ Open Media Bugs for 5.0 and 5.1 (10 min)
14:48:02 <MarkS> agenda+ Media Demo and Resources (5 min)
14:48:06 <MarkS> agenda+ What is missing/at risk in HTML5 (5 min)
14:51:26 <kaz> kaz has joined #html-a11y-media
14:58:23 <Zakim> WAI_HTML AT()11:00AM has now started
14:58:31 <Zakim> +Mark_Sadecki
14:59:10 <kaz> zakim, call kazuyuki-617
14:59:10 <Zakim> ok, kaz; the call is being made
14:59:12 <Zakim> +Kazuyuki
15:01:13 <Zakim> +Adrian_Roselli
15:01:30 <aardrian> aardrian has joined #html-a11y-media
15:01:45 <Zakim> +??P30
15:02:48 <MarkS> zakim, ??P30 is Janina
15:02:48 <Zakim> +Janina; got it
15:02:55 <MarkS> zakim, agenda?
15:02:55 <Zakim> I see 6 items remaining on the agenda:
15:02:57 <Zakim> 1. Identify Scribe [from MarkS]
15:02:57 <Zakim> 2. Web & TV IG: Collaboration on Use Cases and Requirements (10 min) [from MarkS]
15:02:57 <Zakim> 3. Media Accessibility User Requirements (Continued) (30 min) [from MarkS]
15:02:57 <Zakim> 4. Open Media Bugs for 5.0 and 5.1 (10 min) [from MarkS]
15:02:58 <Zakim> 5. Media Demo and Resources (5 min) [from MarkS]
15:02:58 <Zakim> 6. What is missing/at risk in HTML5 (5 min) [from MarkS]
15:03:11 <MarkS> zakim, take up item 1
15:03:11 <Zakim> agendum 1. "Identify Scribe" taken up [from MarkS]
15:03:33 <MarkS> scribe: MarkS
15:03:40 <MarkS> zakim, take up next item
15:03:41 <Zakim> agendum 1 was just opened, MarkS
15:03:45 <MarkS> zakim, close item 1
15:03:45 <Zakim> agendum 1, Identify Scribe, closed
15:03:46 <Zakim> I see 5 items remaining on the agenda; the next one is
15:03:46 <Zakim> 2. Web & TV IG: Collaboration on Use Cases and Requirements (10 min) [from MarkS]
15:03:50 <MarkS> zakim, take up next item
15:03:50 <Zakim> agendum 2. "Web & TV IG: Collaboration on Use Cases and Requirements (10 min)" taken up [from MarkS]
15:04:58 <kaz> -> http://www.w3.org/2013/10/tv-workshop/minutes.html Munich workshop minutes, March 2014
15:05:02 <MarkS> MS: Talked with Kaz and Daniel Davis from Web and TV IG
15:05:15 <kaz> http://www.w3.org/2011/09/webtv/minutes.html#session4 Hollywood ws minutes
15:06:16 <MarkS> 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
15:06:34 <MarkS> ...I mentioned that Mark was interested in collaborating with our group
15:07:24 <MarkS> MS: do you have any reference to your current work?
15:07:29 <kaz> -> https://www.w3.org/2011/webtv/wiki/Media_APIs/Use_Cases use cases from the 1st iteration
15:07:39 <MarkS> KA: we haven't really started second iteration yet, but here is link to our first iteration of work.
15:07:50 <MarkS> ...second screen appellations.
15:08:04 <MarkS> s/appellations/applications
15:08:11 <MarkS> ...how to share content and search content.
15:08:44 <MarkS> JS: in a group setting, second screen becomes very important.  You can tailor the accessibility needed to individuals in the group.
15:09:55 <MarkS> KA: there is a community group for second screen discussions.  There is talk of a special API for this.
15:10:44 <aardrian> Second Screen Presentation Community Group: http://www.w3.org/community/webscreens/
15:11:13 <MarkS> 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
15:11:32 <MarkS> KA: Would be a good idea to have a joint meeting at TPAC
15:11:33 <ShaneM> ShaneM has joined #html-a11y-media
15:11:58 <MarkS> JS: would be good to include use cases based on the scenarios in the accessibility document.
15:12:46 <MarkS> ...we are also looking to work with members to find content that we can release into public domain, and demonstrate accessible media.
15:13:09 <MarkS> ...navigating by structure, sign language translation, multiple languages.
15:13:28 <MarkS> KA: would this include DAISY and ebooks?
15:13:54 <MarkS> JS: the navigation model in those applies to media as well.  Not just next and previous, but more granular control.
15:14:27 <MarkS> ...need to be able to adjust the granularity
15:16:25 <MarkS> 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
15:16:44 <MarkS> KA: It makes sense for me to provide use cases based on your user requirements document.
15:16:53 <MarkS> MS: and we would be glad to review that work.
15:17:41 <MarkS> JS: What is the timeline for this second iteration of work
15:18:31 <MarkS> 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.
15:18:31 <MarkS> ...just getting started on second iteration.
15:18:59 <MarkS> ...next call is on Wednesday, 30 MAY.  I can talk about this idea on that call.
15:19:15 <MarkS> ...I would like to bring this to the group chairs to get their feedback.
15:19:29 <kaz> s/30 MAY/30 Apr./
15:21:03 <MarkS> ...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.
15:21:12 <MarkS> JS: We worked very hard to make sure it was comprehensive.
15:21:24 <MarkS> ...hope to publish it as a note soon.
15:21:55 <MarkS> ...good conversations in 2011 regarding techniques for implementing these features.
15:22:36 <MarkS> KA: we also have a Community Group for tuner controls, which also have accessibility implications.  Just an API might not be enough.
15:23:11 <MarkS> zakim, take up next item
15:23:11 <Zakim> agendum 3. "Media Accessibility User Requirements (Continued) (30 min)" taken up [from MarkS]
15:23:42 <MarkS> Topic: Adding Mark as Editor
15:24:13 <MarkS> JS: We agreed that this should be done and all we need to do is add your name to the document.
15:24:26 <MarkS> Topic: Processing Comments (Continued)
15:24:37 <MarkS> Topic: 3.3 Extended Video Descriptions
15:24:50 <MarkS> -> http://lists.w3.org/Archives/Public/public-html-a11y/2014Apr/0081.html suggested text
15:25:13 <MarkS> JS: suggest we drop one sentence and add a couple more
15:25:47 <MarkS> ...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.
15:26:17 <MarkS> ...every text description, as to be thought of as extended text description, which would require pausing the video
15:26:42 <MarkS> ...in a situation where the user is in a group environment, this could get confusing
15:26:58 <MarkS> ...we can make them reviewable "offline"
15:27:05 <MarkS> ...as a text file
15:27:35 <MarkS> ...good discussion in 2011 regarding options for user control of this feature.
15:28:24 <MarkS> ...options to auto pause, or truncate, etc.
15:28:28 <MarkS> KA: would require very precise time sync?
15:28:48 <MarkS> JS: yes, not only precise time, but knowing whether TTS is still talking and auto-pause the video
15:29:43 <MarkS> ...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.
15:30:09 <MarkS> ...would be appropriate for student to auto pause when watching by themselves, but not in a class setting.
15:30:26 <MarkS> ...user decides how fast the TTS goes
15:30:38 <MarkS> KA: important point.
15:31:27 <MarkS> Agreement
15:31:48 <MarkS> MS: I can make that change then.
15:32:03 <MarkS> ...the next issue was regarding Clean Audio and is in the same email
15:32:38 <MarkS> 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.
15:32:52 <MarkS> ...in a group situation, they would probably wear headphones.
15:33:33 <MarkS> ...viewing alone, they would probably want to set their TV to play only the clean audio, and drop the primary audio track.
15:33:58 <MarkS> ...added a line that clarified that point.
15:34:34 <MarkS> Agreement
15:34:41 <MarkS> MS: I can make that edit as well
15:34:59 <MarkS> Topic: 3.5 Content navigation by content structure
15:35:12 <MarkS> -> http://lists.w3.org/Archives/Public/public-html-a11y/2014Apr/0070.html Suggested rewrite
15:36:15 <MarkS> AR: makes sense to me
15:36:23 <MarkS> JS: I am in favor of this change
15:36:29 <MarkS> MS: I will make this change in the doucment
15:36:46 <MarkS> Topic: 3.7 ECC-4 Enhanced Captions/Subtitles
15:40:21 <MarkS> Ms: @@
15:40:42 <MarkS> JS: I don't think this was controversial when we originally added it.
15:41:07 <MarkS> ..."author proposes and user disposes" is the paradigm we should support.
15:41:26 <MarkS> http://www.w3.org/TR/media-accessibility-reqs/#ECC-4
15:43:06 <MarkS> JS: i think the more interesting part is the concept of overlapping speech.  traditional TTY communications.
15:45:09 <MarkS> RESOLUTION: keep ECC-4 as is.
15:45:52 <MarkS> JS: If you caption an Opera, you should at least be able to see the overlapping words.
15:46:01 <MarkS> ...should be overlapping and should be able to pause.
15:46:31 <MarkS> Topic: Publishing another draft
15:48:28 <MarkS> 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.
15:48:39 <MarkS> ...move to note status ahead of TPAC.
15:49:24 <MarkS> ...would need to convey to Shawn and EO to conclude their work in time for that Last Call publication.
15:49:41 <MarkS> MS: I can talk to EO.
15:50:16 <MarkS> Topic: Reviewing minutes from Shenzhen
15:50:42 <MarkS> JS: Michael had already made those minutes public.  They are available here: http://www.w3.org/2013/11/12-media-minutes
15:51:08 <MarkS> zakim, take up next item
15:51:08 <Zakim> agendum 4. "Open Media Bugs for 5.0 and 5.1 (10 min)" taken up [from MarkS]
15:51:41 <MarkS> https://www.w3.org/WAI/PF/HTML/wiki/Current_Bug_Triage_Issues
15:53:01 <MarkS> https://www.w3.org/Bugs/Public/show_bug.cgi?id=12794
15:54:41 <MarkS> JS: I think putting this back on JF 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
15:55:40 <MarkS> s/JF/John Foliot
15:59:28 <Zakim> -Janina
15:59:29 <Zakim> -Adrian_Roselli
15:59:29 <Zakim> -Mark_Sadecki
15:59:31 <Zakim> -Kazuyuki
15:59:31 <Zakim> WAI_HTML AT()11:00AM has ended
15:59:31 <Zakim> Attendees were Mark_Sadecki, Kazuyuki, Adrian_Roselli, Janina
15:59:44 <MarkS> rrsagent, make minutes
15:59:44 <RRSAgent> I have made the request to generate http://www.w3.org/2014/04/28-html-a11y-media-minutes.html MarkS
16:01:58 <ShaneM> ShaneM has joined #html-a11y-media
16:07:26 <ShaneM> uggh!  I had this on my calendar as 11 central time!  Sorry!