13:53:40 RRSAgent has joined #html-a11y-media
13:53:40 logging to http://www.w3.org/2014/05/12-html-a11y-media-irc
13:53:42 RRSAgent, make logs world
13:53:43 Zakim has joined #html-a11y-media
13:53:44 Zakim, this will be 2119
13:53:44 ok, trackbot; I see WAI_PFWG(HTML A11Y)9:00AM scheduled to start 53 minutes ago
13:53:45 Meeting: HTML Accessibility Task Force Teleconference
13:53:45 Date: 12 May 2014
13:54:02 Meeting: HTML Accessibility Task Force Media Sub-Group
13:54:02 Chair: Mark Sadecki
13:54:02 agenda+ Identify Scribe
13:54:05 agenda+ TV & Web: Collaboration on Use Cases and Requirements
13:54:07 agenda+ Media Accessibility User Requirements
13:54:09 agenda+ Open Media Bugs for 5.0 and 5.1
13:54:11 agenda+ Media Demo and Resources
13:54:13 agenda+ What requires testing in HTML5
13:54:36 zakim, agenda?
13:54:36 I see 6 items remaining on the agenda:
13:54:37 1. Identify Scribe [from MarkS]
13:54:37 2. TV & Web: Collaboration on Use Cases and Requirements [from MarkS]
13:54:37 3. Media Accessibility User Requirements [from MarkS]
13:54:37 4. Open Media Bugs for 5.0 and 5.1 [from MarkS]
13:54:37 5. Media Demo and Resources [from MarkS]
13:54:38 6. What requires testing in HTML5 [from MarkS]
13:58:29 janina has joined #html-a11y-media
13:59:03 WAI_PFWG(HTML A11Y)9:00AM has now started
13:59:10 +??P5
13:59:18 +Mark_Sadecki
13:59:41 aardrian has joined #html-a11y-media
14:00:23 zakim, ??P5 is Janina
14:00:23 +Janina; got it
14:01:08 Getting a message on the call that "conference is restricted at this time." What's up?
14:01:55 JF has joined #html-a11y-media
14:02:13 HI, I am having an issue dialing into the bridge
14:02:23 the conference is restricted at this time (?)
14:02:30 I am getting same issue.
14:03:09 I suspect that Mark did not re-schedule the meeging with Zakim
14:03:20 *meeting
14:03:27 Ah. Makes sense.
14:03:29 ok guys, give me a second
14:03:35 :)
14:04:55 -Mark_Sadecki
14:04:56 -Janina
14:04:57 WAI_PFWG(HTML A11Y)9:00AM has ended
14:04:57 Attendees were Mark_Sadecki, Janina
14:05:23 trackbot, associate this channel with #html-a11y
14:05:23 Associated this channel with #html-a11y.
14:05:35 trackbot, start meeting
14:05:37 RRSAgent, make logs world
14:05:39 Zakim, this will be 2119
14:05:40 Meeting: HTML Accessibility Task Force Teleconference
14:05:40 Date: 12 May 2014
14:05:40 ok, trackbot; I see WAI_HTML AT()11:00AM scheduled to start in 55 minutes
14:06:05 zakim, agenda?
14:06:06 I see 6 items remaining on the agenda:
14:06:06 1. Identify Scribe [from MarkS]
14:06:06 2. TV & Web: Collaboration on Use Cases and Requirements [from MarkS]
14:06:06 3. Media Accessibility User Requirements [from MarkS]
14:06:07 4. Open Media Bugs for 5.0 and 5.1 [from MarkS]
14:06:07 5. Media Demo and Resources [from MarkS]
14:06:07 6. What requires testing in HTML5 [from MarkS]
14:06:55 zakim, code?
14:06:55 the conference code is 2119 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), MarkS
14:07:14 yeah, me too now
14:07:25 its associated with the right meeting now though, so I don't know why
14:07:38 scheduled to start in 55 minutes
14:07:58 it should still work though.
14:08:09 its the 9:00 meeting that is causing the problem
14:08:20 zakim, room for 8 now?
14:08:20 I don't understand your question, MarkS.
14:08:29 zakim, room for 8?
14:08:30 ok, MarkS; conference Team_(html-a11y-media)14:08Z scheduled with code 26631 (CONF1) for 60 minutes until 1508Z
14:08:53 Team_(html-a11y-media)14:08Z has now started
14:09:00 agenda?
14:09:03 +Mark_Sadecki
14:09:13 ok, the code is 26631
14:09:15 +??P8
14:09:22 zakim, ??P8 is me
14:09:22 +janina; got it
14:09:34 +John_Foliot
14:09:43 Are we good to call in?
14:09:55 Zakim, John_Foliot is JF
14:09:56 +JF; got it
14:10:49 +Adrian_Roselli
14:11:32 zakim, take up item 1
14:11:32 agendum 1. "Identify Scribe" taken up [from MarkS]
14:11:50 scribe: janina
14:12:02 zakim, take up next item
14:12:02 agendum 1 was just opened, MarkS
14:12:07 zakim, close item 1
14:12:07 agendum 1, Identify Scribe, closed
14:12:08 I see 5 items remaining on the agenda; the next one is
14:12:08 2. TV & Web: Collaboration on Use Cases and Requirements [from MarkS]
14:12:10 zakim, take up next item
14:12:10 agendum 2. "TV & Web: Collaboration on Use Cases and Requirements" taken up [from MarkS]
14:13:51 ms: JS, MS, and Wu Wei met in ad hoc at WAI-CG's request to examine TV & Web IG's use cases
14:14:03 ms: IG is interested in our input
14:14:39 ms: No apparent distinction between consuming individually vs in a group
14:14:53 -> http://www.w3.org/2011/webtv/wiki/Media_APIs/Use_Cases TV & Web Use Cases Iteration 1
14:14:58 jf: 3 years ago a TV workshop, discussed second screen
14:15:04 ms: Still talking second screen
14:15:11 js: But not second audio device
14:15:58 js: what about a bluetooth headset?
14:16:10 ...might want to send described video to a headset
14:16:36 ...there needs to be a distinction of the individual or group setting
14:16:39 -> http://www.w3.org/2014/05/07-html-a11y-media-minutes.html Minutes from analysis meeting
14:17:20 ms: Has action to discuss timeline for second round of use cases and how we should offer our input
14:17:39 ms: They also meet semi-weekly, next is this Wednesday
14:18:24 js: there were plenty of opportunities to specify that the HTML content needs to be WCAG compliant.
14:18:44 ...if they are going to make screens, they need to be WCAG compliant.
14:19:25 JF: has user agents group talked to them at all?
14:19:27 js: not yet?
14:19:32 s/yet? yet
14:20:52 ...they will reach out to us and we can reach out to UAWG, but they won't do that on their own
14:21:05 ...they reached out to PF. We pointed them to MAUR
14:21:22 ...not much interaction with them since. I don't think it will be confrontational.
14:21:51 JF: If they are specifying use cases, hardware and software technology, we might want to reach out to UAWG now
14:22:06 zakim, next item
14:22:06 agendum 3. "Media Accessibility User Requirements" taken up [from MarkS]
14:22:33 ms: Noting new comment from EO
14:22:35 Topic: New Comment from EOWG
14:22:55 -> http://www.w3.org/TR/media-accessibility-reqs/ Media Accessibility User Requirements
14:23:04 -> http://lists.w3.org/Archives/Public/public-pfwg-comments/2014AprJun/0014.html New Comment from EOWG
14:23:43 JS: we had a round of comments that we haven't finished processing yet. we would like to work through those. Section 2 needs work from EOWG
14:23:56 ...we would like to publish in June or July
14:25:38 -> https://www.w3.org/WAI/PF/Group/comments/list?document_version_id=16 Comments
14:25:40 ms: Before we dive into finishing comment processing, what to do with new comment?
14:25:47 related Media checklist has been accessed 162,711 times. http://www.w3.org/WAI/PF/HTML/wiki/Media_Accessibility_Checklist
14:28:09 JS: take the new comment. it will be well received if we process it.
14:28:26 ...its 15 comments in one email, but its mostly editoral
14:28:56 -> http://lists.w3.org/Archives/Public/public-pfwg-comments/2014AprJun/0014.html New Comment from EOWG
14:29:31 MS: should we put this comment into michaels comment tracker even though we are not using that anymore?
14:29:35 JS: yes, we should
14:29:56 ACTION: for MarkS to enter comment into old tracker
14:29:56 Error finding 'for'. You can review and register nicknames at .
14:30:08 ACTION: MarkS to enter comment into old tracker
14:30:09 Created ACTION-246 - Enter comment into old tracker [on Mark Sadecki - due 2014-05-19].
14:34:14 agenda?
14:34:20 Topic: Processing comments
14:34:27 https://www.w3.org/WAI/PF/Group/comments/details?comment_id=381
14:34:55 jf: Believe this is addressed via javascript API
14:36:56 JS: point James to the API. the requirements in this doc are already handled. there has been progress made here
14:36:57 js: Suggest comment is out of sceop for req doc
14:37:04 Comment: I would include that the requirement be that controls must not only be scriptable, but the playback mechanism must be able to react to AT-triggered control of the media track. (Indie UI may apply here.)
14:37:11 ms: Next comment on Sign Lang 3.8
14:37:21 ms: Comment 381
14:37:25 Comment: I would include that the requirement be that controls must not only be scriptable, but the playback mechanism must be able to react to AT-triggered control of the media track. (Indie UI may apply here.)
14:37:53 https://www.w3.org/WAI/PF/Group/comments/details?comment_id=381
14:38:19 jf: Rather like saying water must be wet ... Duh!
14:39:11 ms: What if the script conflicts with AT?
14:39:52 js: Notes AT has pass through for conflicts
14:40:14 RESOLUTION: We accept the comment
14:40:26 https://www.w3.org/WAI/PF/Group/comments/details?comment_id=389
14:40:29 ms: Next #389
14:40:40 http://lists.w3.org/Archives/Public/w3c-wai-eo/2011OctDec/0014.html
14:41:29 jf: Already accepted
14:43:31 ms: Proposes to take all editorial comments into the doc, i.e. spelling errors
14:43:36 zakim, next item
14:43:36 agendum 4. "Open Media Bugs for 5.0 and 5.1" taken up [from MarkS]
14:43:44 -> Bugs https://www.w3.org/WAI/PF/HTML/wiki/Current_Bug_Triage_Issues#For_Media_Sub-Team
14:45:41 JS: we can move 12794 to 5.1, assign it to john. aria 1.1 might get us the markup we need to handle this one. less contentious to handle in aria. especially if we can generalize it, like in epub
14:48:01 ms: 12964 ...
14:48:07 -> https://www.w3.org/Bugs/Public/show_bug.cgi?id=12964 Bug 12964 -