21:00:43 RRSAgent has joined #html-a11y-media 21:00:43 logging to http://www.w3.org/2014/12/08-html-a11y-media-irc 21:00:44 zakim, who's here? 21:00:44 sorry, JF, I don't know what conference this is 21:00:46 On IRC I see RRSAgent, Zakim, JF, ShaneM, MarkS, janina, trackbot 21:01:12 zakim, help 21:01:12 Please refer to http://www.w3.org/2001/12/zakim-irc-bot for more detailed help. 21:01:14 Some of the commands I know are: 21:01:14 xxx is yyy - establish yyy as the name of unknown party xxx 21:01:14 if yyy is 'me' or 'I', your nick is substituted 21:01:14 xxx may be yyy - establish yyy as possibly the name of unknown party xxx 21:01:15 I am xxx - establish your nick as the name of unknown party xxx 21:01:15 xxx holds yyy [, zzz ...] - establish xxx as a group name and yyy, etc. as participants within that group 21:01:16 xxx also holds yyy - add yyy to the list of participants in group xxx 21:01:16 who's here? - lists the participants on the phone 21:01:16 who's muted? - lists the participants who are muted 21:01:16 mute xxx - mutes party xxx (like pressing 61#) 21:01:16 unmute xxx - reverses the effect of "mute" and of 61# 21:01:17 is xxx here? - reports whether a party named like xxx is present 21:01:17 list conferences - reports the active conferences 21:01:18 this is xxx - associates this channel with conference xxx 21:01:18 excuse us - disconnects from the irc channel 21:01:18 I last learned something new on $Date: 2013-03-03 19:18:47 $ 21:01:41 zakim, please list conferences 21:01:41 I see WAI_HTML AT()4:00PM, Team_(html-a11y-media)21:10Z active 21:01:42 also scheduled at this time are GA_FXTF()4:00PM, SEC_WebCryp()3:00PM 21:02:02 zakim, this is Team_ 21:02:02 ok, ShaneM; that matches Team_(html-a11y-media)21:10Z 21:02:44 Hi, trying to get on 21:03:05 Hmmm, I have no audio. Will try and try again ... 21:05:08 zakim, who is here? 21:05:08 On the phone I see janina, MarkS, JF 21:05:10 On IRC I see RRSAgent, Zakim, JF, ShaneM, MarkS, janina, trackbot 21:05:29 zakim, who's on the phone? 21:05:29 On the phone I see janina, MarkS, JF 21:06:49 zakim, who's on the phone? 21:06:49 On the phone I see janina, MarkS, JF 21:07:03 zakim, who's here? 21:07:03 On the phone I see janina, MarkS, JF 21:07:05 On IRC I see RRSAgent, Zakim, JF, ShaneM, MarkS, janina, trackbot 21:07:14 zakim, I am here 21:07:15 sorry, ShaneM, I do not see a party named 'here' 21:07:40 zakim, WAI_HTML also has ShaneM 21:07:40 sorry, MarkS, I do not recognize a party named 'WAI_HTML' 21:07:42 zakim, who is here? 21:07:42 On the phone I see janina, MarkS, JF 21:07:44 On IRC I see RRSAgent, Zakim, JF, ShaneM, MarkS, janina, trackbot 21:07:50 zakim, present+ 21:07:50 I don't understand 'present+', ShaneM 21:07:52 zakim, a11y also has ShaneM 21:07:52 sorry, MarkS, I do not recognize a party named 'a11y' 21:07:58 zakim, 2119 also has ShaneM 21:07:58 sorry, MarkS, I do not recognize a party named '2119' 21:08:05 trackbot, start meeting 21:08:07 RRSAgent, make logs world 21:08:09 Zakim, this will be 2119 21:08:09 ok, trackbot; I see WAI_HTML AT()4:00PM scheduled to start 8 minutes ago 21:08:10 Meeting: HTML Accessibility Task Force Teleconference 21:08:10 Date: 08 December 2014 21:08:16 present+ ShaneM 21:08:24 zakim, who's here? 21:08:24 I notice Team_(html-a11y-media)21:10Z has restarted 21:08:26 On the phone I see janina, MarkS, JF 21:08:26 On IRC I see RRSAgent, Zakim, JF, ShaneM, MarkS, janina, trackbot 21:08:56 agenda? 21:09:47 Chair+ Janina Sajka 21:09:47 agenda+ Identify Scribe 21:09:47 agenda+ Media Accessibility User Requirements: Remaining Comment Responses 21:09:47 agenda+ Responses to Commenters 21:09:47 agenda+ Checklist Updates 21:09:58 zakim, take up item 1 21:09:58 agendum 1. "Identify Scribe" taken up [from MarkS] 21:10:04 scribe: MarkS 21:10:40 agenda+ BBC Comments 21:10:40 agenda? 21:10:53 zakim, agenda order is 1,5,2,3,4 21:10:53 ok, MarkS 21:10:56 agenda? 21:10:57 http://lists.w3.org/Archives/Public/public-html-a11y/2014Dec/0020.html 21:11:03 zakim, close item 1 21:11:03 agendum 1, Identify Scribe, closed 21:11:04 I see 4 items remaining on the agenda; the next one is 21:11:04 5. BBC Comments [from MarkS] 21:11:09 zakim, take up next item 21:11:09 agendum 5. "BBC Comments" taken up [from MarkS] 21:11:41 SM: these are great comments 21:12:03 ...3.6, comment about CC-10 about rendering background colors in full range of opacity 21:12:12 [reads] 21:12:59 ...enable background area to extend to a preset distance relative to the foreground text... 21:13:29 JF: Overall I agree. sounds overly prescriptive about how much padding should be applied. Don't think we should have a physical measurment 21:13:48 SM: I don't think he is saying that. just that it should be expandable. 21:14:19 JF: who is responsible that the padding exists? author, user agent? both? 21:14:36 SM: i think it would be both 21:15:04 MS: depends on if the controls are rendered by the UA or the author 21:15:45 JS: developers are reminded that readability is enhanced when padding is provided... etc. 21:16:35 JF: this would be a should requirement, right 21:16:55 SM: not specified in the comment 21:17:01 SHOULD as in RFC 2119, and not a MUST 21:17:49 JF: lets wordsmith it offline. 21:17:58 SM: I'm happy to do that and add it at the end of the CC section 21:18:11 SM: CC-11, rendering text in a range of colors 21:18:35 [reads] 21:19:25 ...recommend that full color customization is available 21:19:36 ...I think we are kind of saying that already 21:19:41 JS: I like what he says 21:19:48 SM: I agree. its well written 21:19:59 JF: I believe that the requirement is already there. 21:20:08 ...this adds some justification 21:20:18 ...but doesn't change the requirement 21:20:40 JS: Maybe add to the explanatory tex.t its very well written. worth capturing 21:21:24 SM: JF thinks that there is already a requirement for this, but I don't think there is. There is a note about this. 21:21:42 ...I would probably add this to that note 21:21:58 JS: do we want to elevate this? 21:22:03 ...get it out of the note 21:22:29 JF: We can take out "Note" then its just a continuation of the requirement 21:22:45 JS: I'm happy with that 21:22:49 JF: me too 21:23:01 ...WebVTT uses standard CSS, which aids this. 21:23:37 SM: CC-12 Thicker outline to allow for better contrast 21:23:56 [reads] 21:24:35 ...preferable to not use drop shadows 21:24:42 JS: so it should be user customizable... 21:24:55 SM: which is what I am assuming with use of the word enabled. 21:25:16 JS: Happy to accept this clarification 21:25:27 SM: should clarify that its enable able by user 21:25:39 [agreement] 21:26:26 SM: CC-13 preferable to keep the caption background when frequent captions, but should fade away when captions are infrequent 21:26:40 ...proposal, remove this requirement, 21:26:53 ...alt proposal, change it is preferable to it should be possible. 21:27:02 [agreement on proposal 2] 21:27:18 SM: I was surprised we had this as a MUST 21:27:42 ...CC-14 paint on with pop up captions 21:27:55 ...proposal to add a 2 notes to the section: 21:28:09 [reads] 21:28:56 JS: Makes sense to me now that its brought up 21:29:10 SM: final words are available for enough time that they can be read. 21:29:27 ...i don't want that to be a note. should be a requirement.... 21:29:43 [agreement] 21:29:59 ...take the first proposal and make it a note. the 2nd should be included in the base requirement 21:30:40 ...this happens to me at the gym all the time due to commercials interrupting the captions 21:31:09 ....CC-15, lowest line of captions, 1/12 of the total height above the bottom 21:31:33 ...not global, as the measurement appears to be arbitrary. specificity should be removed. 21:32:16 JF: I tend to agree. don't like to be overly prescriptive 21:32:42 SM: I think we should say "a reasonable gap e.g. 1/12th, etc." 21:32:42 [agreement] 21:32:49 JF: Its a hint/suggestion, not a requirement 21:34:21 crap 21:34:25 I was being briliant too 21:34:27 Zakim lost you! 21:34:43 is that how they spell it in England? 21:36:04 SM: the next comment is a proposal for new req. 21:36:16 ...my reaction is that this is covered by CC-9 21:36:33 JS: If we want to add any explanatory, just add it there re screen sizes and differences 21:36:43 JF: the end user should be able to adjust this. 21:37:12 JS: Happy to expand the one that is there. don't think we need to add a new one 21:38:03 SM: often beneficial optimized for the technology used on device, e.g. on android, helvetica doesn't render well, so roboto font should be available 21:38:18 ...optimized for readability to use font that is preferred when they are available 21:38:51 JF: I think that comment goes back to the comment on styling. To do this, you would load a different stylesheet based on media query. 21:38:59 ...author requirement not a user requirement, 21:39:13 SM: I don't see it that way. I want the platform to offer this 21:39:29 ...a preferred font, based on what it knows about itself 21:41:34 JS: I think we agree that this should happen and should be supported 21:41:51 SM: CC-11 says user has control. isn't this already covered? 21:42:05 JS: We could expand 9 like we did with 11 21:42:49 SM: to agree with JF, it would be nice to advise authors to do this, not to leave it up to platform 21:43:06 s/platform/user 21:43:23 ...is it valuable for us to say that in the context of CC 11 21:43:28 ...or somewhere else? 21:43:37 JF: sounds like a production note to me 21:43:48 ...in WCAG we have SC requirements and techniques that allow 21:43:53 ....propose a technique 21:44:08 ...we don't really have techniques in there (yet) 21:44:46 SM: a note that says while users have control... preferable that authors tune their content to target device as well using media queries, etc. 21:44:53 JS: I'm happy with that 21:45:14 JF: lets wordsmith this. I think we're all on the same track here. just needs to be worded carefully 21:45:22 SM: Can I run a draft by you JF? 21:45:23 JF: yes 21:46:41 SM: 4.7 use of the viewport 21:47:15 ...VP-5 lower third, where controls are usually rendered. avoid conflicts, esp if controls available on command. 21:47:23 ...i thought that was really strict 21:47:41 JF: its saying we don't want controls to be obscured by captions or vice versa 21:47:51 SM: or you can imagine a situation where those things fight, because there is so much captioning 21:48:52 ...also important to avoid conflicts with other essential content 21:49:25 ...strongly disagree with the stacking requirement in the note 21:49:49 ...our note suggest stacking 21:50:04 ...comment is that the best place is likely at the top of the video, where it won't obscure 21:50:15 ...suggests edit to suggest this 21:50:51 JF: I say replace the existing note with that 21:51:28 SM: he means away from important parts of underlying video 21:51:40 JS: we should get clarification on that 21:52:11 SM: i lik the phrase "editorially important" 21:53:35 JF: I'm not opposed to this. I think consistency is the important thing 21:55:12 ...just saying we want to avoid overlapping content 21:55:52 ...maybe some wordsmithing is required here, but this is pretty good start 21:59:43 http://transition.fcc.gov/cgb/dro/cvaa.html 22:00:18 rrsagent, make minutes 22:00:18 I have made the request to generate http://www.w3.org/2014/12/08-html-a11y-media-minutes.html MarkS 22:00:28 JS: I will be unavailable at this time next week 22:01:17 ...still have to review all this wordsmithing and then tweak the responses to commenters. then we are done. 22:01:24 ...ok to meet without me? 22:04:30 SM: so we're adding a couple of requirements, these will need to trickle down to the checklist. JF, can you do this>? 22:04:45 JF: I can do that, just let me know when you're done adding those 22:05:06 ...there is a must, should, may component that will need to be verified as well 22:05:50 rrsagent, make minutes 22:05:50 I have made the request to generate http://www.w3.org/2014/12/08-html-a11y-media-minutes.html MarkS 22:06:11 zakim, part 22:06:11 leaving. As of this point the attendees were janina, +1.617.319.aaaa, MarkS, JF 22:06:11 Zakim has left #html-a11y-media 22:06:21 rrsagent, make minutes 22:06:21 I have made the request to generate http://www.w3.org/2014/12/08-html-a11y-media-minutes.html MarkS