17:59:25 RRSAgent has joined #a11y-bugs 17:59:25 logging to http://www.w3.org/2012/01/11-a11y-bugs-irc 17:59:30 rrsagent, make log world 17:59:32 The passcode does not seem to work for me 18:00:07 agenda: http://lists.w3.org/Archives/Public/public-html-a11y/2012Jan/0055.html 18:00:32 LeonieW has joined #a11y-bugs 18:01:22 It either says "The conference is restricted at this time" or "the passcode is incorrect" 18:04:05 either is fine by me 18:04:37 IS there a limit to how many conferences there can be at a time? 18:05:08 ah ok 18:09:33 regrets: Marco_Ranon, Gez_Lemon, Everett_Zufelt 18:11:28 scribe: hhillen 18:11:42 Zakim, next item 18:11:42 agendum 6. "Fixed bugs" taken up [from lwatson] 18:12:42 drop item 6 18:12:44 drop item 7 18:13:32 agenda+ Invalid bugs 18:13:34 agenda+ Fixed bugs 18:13:36 agenda+ Cynthia's questions 18:13:37 agenda+ Tracker issue identification 18:13:43 zakim, next item 18:13:43 agendum 8. "Invalid bugs" taken up [from MichaelC] 18:14:04 agenda: http://lists.w3.org/Archives/Public/public-html-a11y/2012Jan/0055.html 18:14:35 https://www.w3.org/Bugs/Public/show_bug.cgi?id=7601 18:15:43 MC: No Action 18:16:10 LW: I will take out the a11ytf keyword 18:16:31 https://www.w3.org/Bugs/Public/show_bug.cgi?id=10481 18:17:27 MC: This one already has a tracker issue, so it's already escalated 18:19:40 HH: It's associated with http://www.w3.org/html/wg/tracker/issues/129 18:20:07 LW: Do we still need to track it if it has already been escalated? 18:20:19 MC: That's something that should be discussed 18:20:45 https://www.w3.org/Bugs/Public/show_bug.cgi?id=10482 18:21:00 MC: Already assigned to a tracker issue 18:21:17 https://www.w3.org/Bugs/Public/show_bug.cgi?id=10905 18:22:54 MC: It's an old issue that dropped off the radar. We assigned it to Gregory but maybe we should assign it to Steve 18:23:58 MC: This should be part of the (possibly yet to be created) ARIA mapping tracker issue 18:24:46 https://www.w3.org/Bugs/Public/show_bug.cgi?id=11238 18:25:00 MC: Already has a tracker issue 18:25:11 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13326 18:26:49 MC: Requester already marked it as invalid, so there's no need to track it. I'll remove the a11ytf keyword. 18:27:02 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13504 18:28:12 MC: This should be a feature request 18:28:26 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13533 18:29:29 HH: This is a user agent rather than an HTML feature 18:29:42 MC: Should we remove the a11ytf keyword? 18:30:04 LW: It's out of the scope of this spec so it should be filed somewhere else. 18:30:31 MC: I'll remove the keyword. It's something that should be handled by UAAG 18:31:02 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13535 18:32:36 HH: This is more related to WCAG than HTML 18:33:16 MC: I'll ping Joshue, this bug should be added as a WCAG technique 18:33:34 MC: Removing the a11ytf keyword 18:34:22 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13562 18:35:12 MC: I propose we reassign this to the HTML A11Y API component. 18:35:21 MC: That means assigning it to Cynthia 18:35:29 MC: Marking it as reopend 18:35:45 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13617 18:36:50 MC: I think the HTML spec should address this, but I think it's more informative 18:37:06 MC: I don't want to escalate this bug but I also don't want to drop it 18:39:00 HH: To me this is not an a11y issue but a privacy issue in general 18:39:22 HH: And not related to HTML5 in particular 18:41:35 MC: I'll add a note that this is a valid issue but that we're not sure who the owner should be (perhaps UAAG or Privacy), or that it even belongs in HTML. The issue is not related to accessibility but to privacy in general. 18:42:21 MC: I can alert the person who is handling privacy about this bug 18:42:40 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13619 18:44:26 MC: Some API from the Web Apps WG should handle this 18:45:09 LW: An API would make sense if it's platform neutral 18:46:35 MC: Maybe we can raise this as a question at the task force meeting tomorrow 18:46:53 kliehm has joined #a11y-bugs 18:47:29 LW: It's really a feature request though, a request for something that's absent rather than broken 18:48:05 LW: So our options are treat it as a feature request or escalate it 18:49:57 MC: We'll treat it as a feature request, it's relevant but does not need to be escalated now 18:50:30 MC: We could change the resolution state from 'invalid' to 'later' 18:50:48 MC: I'll make that change now 18:53:28 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13621 18:55:27 MC: Escalating seems problematic, dropping doesn't quite sound right 18:56:10 MC: I'll assign it back to Greg but take of the a11ytf keyword, no other changes 18:56:28 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13647 18:59:36 MC: We need to have a way of not dropping this. It's a relevant issue but related to MathML and not HTML 19:01:28 MC: We should remove the TF keyword, add verify invalid 19:04:40 MC: We may have to consider having another call on Friday 19:04:49 MC: We'll process Cynthia's issue now 19:04:53 Zakim, next item 19:04:53 agendum 9. "Fixed bugs" taken up [from MichaelC] 19:05:12 Zakim, next item 19:05:12 agendum 9 was just opened, hhillen 19:05:21 Zakim, close this item 19:05:21 agendum 9 closed 19:05:22 I see 2 items remaining on the agenda; the next one is 19:05:23 10. Cynthia's questions [from MichaelC] 19:05:24 Zakim, next item 19:05:24 agendum 10. "Cynthia's questions" taken up [from MichaelC] 19:06:04 MC: Bug 8000, Cynthia asked if it could be closed 19:06:06 https://www.w3.org/Bugs/Public/show_bug.cgi?id=8000 19:06:54 MC: We should stay focused on escalation, this one is already escalated and she 's asking about de-escalation. We should email back to Cynthia that we leave this to her judgement 19:07:12 http://lists.w3.org/Archives/Public/public-html-a11y/2011Dec/0318.html 19:07:19 MC: Cynthia's proposing to let this one go 19:07:53 MC: I'll remove the TF keyword 19:08:07 http://lists.w3.org/Archives/Public/public-html-a11y/2011Dec/0317.html 19:08:38 MC: There is nothing we can do for this, it should go back to the task force 19:09:34 http://lists.w3.org/Archives/Public/public-html-a11y/2011Dec/0316.html 19:10:41 13512 19:11:07 MC: We agree with wont fix and out of scope 19:13:31 13659 19:13:53 MC: No objections 19:14:33 13662 19:14:51 MC: We should leave that on Cynthia's plate 19:15:09 13656 19:15:17 That would go back to the task force 19:15:42 13528 19:16:07 MC: That's fine, we don't need to do anything. 19:16:52 MC: We need to figure out if we should drop the a11ytf keyword for bugs that are already verified or that have been add to tracker 19:16:58 13531 19:17:57 MC: Are we going to escalate on an example? This might fall under the 'pick your battles' thing 19:18:22 LW: Yes, the request is correct but probably not worth picking up right now 19:19:13 The above applies to 13542 19:19:23 13548 19:20:02 MC: We're leaving this one alone 19:20:16 13549 19:23:22 MC: If Cynthia wants to escalate this she can do this on her own steam, the bug triage team does not see the need to escalate 19:23:34 13552 19:24:10 MC: I don't think we want to pursue this 19:24:21 13560 19:24:51 MC: We should put this on the list for tomorrow 19:26:09 13559 19:26:55 MC: NOt one for use to escalate 19:27:42 http://lists.w3.org/Archives/Public/public-html-a11y/2011Dec/0329.html 19:27:50 13561 19:29:15 MC: Nothing for us to do 19:29:31 13562 19:29:33 MC: Nothing for us to do 19:29:40 13566 19:32:35 MC: Does not need escalating 19:33:16 MC: Friday we'll look at the fixed and needs info bugs 19:33:27 MC: And go through the tracker issues 19:37:14 RRSAgent, please generate the minutes 19:37:14 I have made the request to generate http://www.w3.org/2012/01/11-a11y-bugs-minutes.html hhillen