14:00:38 RRSAgent has joined #wcag2ict 14:00:38 logging to http://www.w3.org/2013/04/05-wcag2ict-irc 14:00:40 RRSAgent, make logs world 14:00:40 Zakim has joined #wcag2ict 14:00:42 Zakim, this will be 2428 14:00:42 ok, trackbot; I see WAI_(WCAG2ICT)10:00AM scheduled to start now 14:00:43 Meeting: WCAG2ICT Task Force Teleconference 14:00:43 Date: 05 April 2013 14:00:50 zakim, who is on the phone? 14:00:51 WAI_(WCAG2ICT)10:00AM has not yet started, andisnow 14:00:51 On IRC I see RRSAgent, Loic, Mike_P, alex_, andisnow, Kiran_Kaja, korn, shadi, MichaelC, trackbot 14:01:02 Zakim, Oracle has Peter_Korn 14:01:02 sorry, korn, I do not recognize a party named 'Oracle' 14:01:30 zakim, who is on the phone? 14:01:30 WAI_(WCAG2ICT)10:00AM has not yet started, andisnow 14:01:31 On IRC I see RRSAgent, Loic, Mike_P, alex_, andisnow, Kiran_Kaja, korn, shadi, MichaelC, trackbot 14:02:57 greggvanderheiden has joined #wcag2ict 14:03:04 greggvanderheiden has left #wcag2ict 14:03:17 MaryJo has joined #wcag2ict 14:03:28 greggvanderheiden has joined #wcag2ict 14:03:42 agenda+ Discuss the 'Closed Functionality - compare/contrast with M376' survey [2] starting at 1.4.5 14:04:07 agenda+ Discuss the survey on WCAG2ICT Conformance Note proposal [3] 14:04:23 Judy has joined #wcag2ict 14:04:33 agenda+ priorities for remaining items to address 14:04:39 Zakim, who is here? 14:04:39 WAI_(WCAG2ICT)10:00AM has not yet started, korn 14:04:40 On IRC I see Judy, greggvanderheiden, MaryJo, Zakim, RRSAgent, Loic, Mike_P, alex_, andisnow, Kiran_Kaja, korn, shadi, MichaelC, trackbot 14:04:51 zakim, how are you feeling? 14:04:51 I don't understand your question, Judy. 14:05:04 agenda+ confirming next meetings 14:05:10 Zakim, take two aspirin! 14:05:11 I don't understand 'take two aspirin!', korn 14:05:47 Zakim, open the pod bay doors 14:05:47 I don't understand 'open the pod bay doors', korn 14:06:28 s/zakim, how are you feeling?// 14:06:49 zakim, this is WAI_(WCAG2ICT) 14:06:49 ok, Judy; that matches WAI_(WCAG2ICT)10:00AM 14:07:07 zakim, who is on the phone? 14:07:07 On the phone I see [Oracle], Andi_Snow_Weaver, [Microsoft], ??P16, ??P17, Kiran_Kaja, Ben_and_Gregg, Judy, Mary_Jo_Mueller 14:07:14 Zakim, Oracle has Peter_Korn 14:07:14 +Peter_Korn; got it 14:07:33 Zakim, ??P17 is me 14:07:33 +Loic; got it 14:07:47 q- 14:07:58 ack ??p17 14:08:03 ZAkim, ??P16 is me 14:08:03 +Mike_P; got it 14:08:27 +David_MacDonald 14:08:32 scribe: Mary_Jo_Mueller 14:08:37 scribenick: MaryJo 14:08:41 https://www.w3.org/2002/09/wbs/55145/20130321/results#x95 14:09:02 zakim, next item 14:09:02 agendum 1. "Discuss the 'Closed Functionality - compare/contrast with M376' survey [2] starting at 1.4.5" taken up [from andisnow] 14:10:35 q+ 14:10:59 q+ 14:11:16 q+ 14:11:35 q+ 14:12:00 ack 14:12:13 David has joined #wcag2ict 14:12:47 +q 14:14:08 q- 14:14:13 q- 14:14:13 ack L 14:14:14 ack g 14:14:25 SC 1.4.5 was put on the list because it was meant to cover AT's having text for non-text content. 14:14:42 Closed products don't have AT 14:14:47 ack alex 14:15:38 ack alex 14:16:58 q+ 14:17:13 WCAG2ICT text describes the problematic issue when applying this SC to closed functionality of non-web ICT. The M376 standard includes several separate provisions (such as 5.1.3.1, 5.1.3.6) to address the problematic issue. No change. Rationale: WCAG2ICT does not have specific provisions for closed functionality. 14:17:35 ack mike 14:18:05 q+ 14:18:09 ack korn 14:19:55 Proposal was made to use Andi's edits and change others to remain consistent. 14:19:59 ack ag 14:20:04 ackg 14:20:07 ack g 14:20:09 ack g 14:20:14 s /ackg// 14:20:20 s /ack ag// 14:22:13 WCAG2ICT text describes the problematic issue when applying this SC to closed functionality of non-web ICT. The M376 standard includes several separate provisions (such as 5.1.3.1, 5.1.3.6) to address the problematic issue.  WCAG2ICT describes potential text rendering limitations in closed. 14:22:13 No change. 14:22:13 Rationale: WCAG2ICT does not have specific provisions for closed functionality.WCAG2ICT text is helpful. 14:22:13 -5Apr13 14:23:28 WCAG2ICT explains why this SC connects to AT 14:26:50 SC 2.1.1 Keyboard - https://www.w3.org/2002/09/wbs/55145/20130321/results#x323 14:27:20 The language we just adopted would work on this SC too. 14:28:11 So 2.1.1 would be almost identical to 1.4.5 14:28:50 WCAG2ICT text describes the problematic issue when applying this SC to closed functionality of non-web ICT. M376 notes a 5.x.y.z provision addressing the closed requirement raised by this SC.  WCAG2ICT describes why this SC connects to AT. 14:28:50 No change. 14:28:50 Rationale: WCAG2ICT does not have specific provisions for closed functionality.  WCAG2ICT text is helpful. 14:28:50 -5Apr13 14:31:32 SC 2.1.2 No Keyboard Trap - https://www.w3.org/2002/09/wbs/55145/20130321/results#xFulltext 14:33:41 Peter made a suggested update to the rationale from Gregg's proposal in the survey. 14:34:21 WCAG2ICT does not put this on the Closed List. M376 does, and notes a 5.x.y.z provision addressing the closed requirement raised by this SC. No change. Rationale: Nothing in 2.1.2 relates to 'making information available in text (which can be read by assistive technologies) or making it "programmatically determinable" (rendered by a user agent, and readable by assistive technologies) or discuss[es] doing something else to make content compatible with as[CUT] 14:34:56 WCAG2ICT does not put this on the Closed List. M376 does, and notes a 5.x.y.z provision addressing the closed requirement raised by this SC. 14:34:56 No change. 14:35:16 WCAG2ICT does not put this on the Closed List. M376 does, and notes a 5.x.y.z provision addressing the closed requirement raised by this SC. 14:35:24 No change. 14:35:43 Rationale: Nothing in 2.1.2 relates to 'making information available in text (which can be read by assistive technologies) or making it "programmatically determinable" (rendered by a user agent, and readable by assistive technologies) or discuss[es] doing something else to make content compatible with assistive technologies.' 14:35:54 Furthermore, it applies equally to closed and non-closed functionality or controls. If closed functionality control has a keyboard interface - then it shouldn't trap. And if the control doesn't then there is no problem. So there is no need to change this success criterion for a closed product. 14:35:55 korn has joined #wcag2ict 14:36:04 -5Apr13. 14:36:54 q+ 14:37:00 SC 2.1.3 Keyboard (no exceptions) - https://www.w3.org/2002/09/wbs/55145/20130321/results#x145 14:39:32 q+ 14:39:50 ack g 14:39:53 q+ 14:39:56 q+ 14:40:03 There are a few AAA SCs we have in the closed products list. We had discussed last meeting that we won't be doing an analysis of AAA SCs so we don't need to have them listed here. 14:40:31 ack d 14:40:58 q+ 14:41:37 q+ 14:41:41 ack a 14:42:17 q+ 14:42:42 q+ 14:43:01 ack j 14:43:42 +1 14:43:59 q+ 14:44:03 There is concern that if we don't have AAA SCs listed in WCAG2ICT, they will be forgotten altogether by people looking at this document. 14:44:24 q+ to clarify my earlier comment 14:44:29 ack k 14:44:45 It might be confusing to readers to have some AAA SCs addressed in the closed section, but nowhere else in the document. 14:46:23 We'll have to look at the introduction to make sure we have the appropriate level of discussion on the AAA SCs. The introduction should be looked at to make sure it is complete enough. 14:47:01 q+ 14:48:11 ack g 14:49:45 q+ 14:51:41 ack da 14:51:44 The level AAA SCs will also likely be difficult and time consuming for the task force to get through. Just trying to explore the SCs and figure out what they mean would be a long process. 14:51:44 ack mi 14:55:13 q+ 14:55:34 We need to put this decision in a survey so that we can document a resolution for it and take the decision forward to the WCAG working group. 14:55:50 ack judy 14:55:50 Judy, you wanted to clarify my earlier comment and to 14:56:21 ack korn 14:56:37 q- 14:57:09 So to be consistent, it is best to remove the AAA SCs from the closed products section. 14:57:18 M376 doesn't include this on the list. This is an AAA SC. 14:57:18 RESOLUTION: drop this SC from the list. 14:57:18 Rationale: This version of WCAG2ICT doesn't address any AAA SC. 14:57:18 -5Apr13. 14:58:51 In the introduction we can say that we aren't covering AAA SCs in this document, and state that there may be useful techniques in these SC that are applicable to non-web content. 14:59:18 SC 2.4.2 Page Titled - https://www.w3.org/2002/09/wbs/55145/20130321/results#x245 14:59:26 M376 doesn't include this on the list, and further doesn't apply this SC to software. 14:59:26 No Change. 14:59:26 Rationale: This SC is applied by WCAG2ICT, and is about 'making information available in text', which is one of our criteria for being on the "Closed List". 14:59:26 -5Apr13. 14:59:51 q+ 15:00:46 "M376 draft doesn't..."? 15:01:24 q+ 15:01:30 q+ 15:01:31 We need to put in the beginning of our comparison that what version of M376 we were comparing to. 15:02:24 -Mike_P 15:02:55 WCAG2ICT text describes the problematic issue when applying this SC to closed functionality of non-web ICT. M376 does not include this SC on the closed functionality list and does not apply it to software or documents. WCAG2ICT describes why this SC connects to AT. 15:04:10 ack a 15:04:45 +??P1 15:04:47 ack k 15:06:16 +1 15:06:38 ack g 15:06:46 We're going to add 'draft' when referring to M376 and WCAG2ICT documents. 15:08:19 This only needs to be done in the last column of the table. 15:08:49 WCAG2ICT draft text describes the problematic issue when applying this SC to closed functionality of non-web ICT. M376 draft does not include this SC on the closed functionality list and does not apply it to software or documents. WCAG2ICT draft describes why this SC connects to AT. 15:08:49 No Change. 15:08:49 Rationale: This SC is applied by draft WCAG2ICT, and is about 'making information available in text', which is one of our criteria for being on the "Closed List". 15:08:49 -5Apr13. 15:09:15 WCAG2ICT draft text describes the problematic issue when applying this SC to closed functionality of non-web ICT. M376 draft does not include this SC on the closed functionality list and does not apply it to software or documents. WCAG2ICT draft describes why this SC connects to AT. 15:09:15 No Change. 15:09:15 Rationale: This SC is applied by WCAG2ICT draft, and is about 'making information available in text', which is one of our criteria for being on the "Closed List". 15:09:15 -5Apr13. 15:09:36 ----------- Look above ------------ 15:11:09 SC 3.1.1 Language of page - https://www.w3.org/2002/09/wbs/55145/20130321/results#x155 15:11:13 q+ 15:11:29 -David_MacDonald 15:11:32 David_ has joined #wcag2ict 15:12:01 WCAG2ICT draft text describes the problematic issue when applying this SC to closed functionality of non-web ICT.  M376 draft notes a 5.x.y.z provision addressing the closed requirement raised by this SC. WCAG2ICT describes potential text rendering limitations in closed. 15:12:02 No change.  15:12:02 Rationale: WCAG2ICT draft does not have specific provisions for closed functionality. WCAG2ICT draft text is helpful. 15:12:02 -5Apr13.  15:13:17 +David_MacDonald 15:13:39 WCAG2ICT draft text describes the problematic issue when applying this SC to closed functionality of non-web ICT.  M376 draft notes a 5.x.y.z provision addressing the closed requirement raised by this SC.  WCAG2ICT draft describes why this SC connects to AT. 15:13:39 No change.  15:13:39 Rationale: WCAG2ICT draft does not have specific provisions for closed functionality. WCAG2ICT draft text is helpful. 15:13:39 -5Apr13.  15:14:33 SC 3.1.2 Language of parts - https://www.w3.org/2002/09/wbs/55145/20130321/results#xq10 15:14:57 This looks a lot like 2.4.2 15:16:18 The final column in the wiki shows the text we'll be using. 15:18:43 We will apply the same text to 3.3.1. 15:20:06 WCAG2ICT draft text describes the problematic issue when applying this SC to closed functionality of non-web ICT.  WCAG2ICT draft describes why this SC connects to AT. 15:20:07 No change.  15:20:07 Rationale: WCAG2ICT draft text is helpful. 15:20:07 -5Apr13.  15:20:26 SC 4.1.1 Parsing and 4.1.2 Name, Role, Value - https://www.w3.org/2002/09/wbs/55145/20130321/results#x411 and https://www.w3.org/2002/09/wbs/55145/20130321/results#x412 15:20:39 Above text would be for these last two SC. 15:24:10 General Comments - https://www.w3.org/2002/09/wbs/55145/20130321/results#xGeneral 15:24:18 q+ 15:25:13 ack g 15:25:20 q+ 15:26:54 q+ 15:27:25 q- 15:27:28 q+ 15:28:16 Anyone who participates in the national bodies reviewing Me76 can use the comments, but should not quote these rationales as coming from the WCAG2ICT task force. 15:28:38 q+ 15:28:58 ack m 15:29:08 s /Me76/M376/ 15:30:05 +1 15:30:26 -[Microsoft] 15:34:58 There shouldn't be any general introductory comments/observations on M376 that we add to the document. 15:35:11 -Kiran_Kaja 15:35:25 -Judy 15:36:04 topic: Remaining items to address 15:36:19 Remaining 4 SC for software and documents 15:37:00 -Loic 15:37:01 -[Oracle] 15:37:01 -David_MacDonald 15:37:02 -Andi_Snow_Weaver 15:37:03 -Ben_and_Gregg 15:37:07 -??P1 15:37:09 -Mary_Jo_Mueller 15:37:10 WAI_(WCAG2ICT)10:00AM has ended 15:37:10 Attendees were Andi_Snow_Weaver, [Microsoft], Kiran_Kaja, Ben_and_Gregg, Judy, Mary_Jo_Mueller, Peter_Korn, Loic, Mike_P, David_MacDonald 15:37:18 korn has left #wcag2ict 15:38:12 andisnow has left #wcag2ict 15:38:19 zakim, bye 15:38:19 Zakim has left #wcag2ict 15:38:24 rrsagent, make minutes 15:38:24 I have made the request to generate http://www.w3.org/2013/04/05-wcag2ict-minutes.html MaryJo 15:40:19 s /ack ??p17// 15:43:11 chair: Mike_Pluke 15:43:25 rrsagent, make minutes 15:43:25 I have made the request to generate http://www.w3.org/2013/04/05-wcag2ict-minutes.html MaryJo 15:47:45 Mike_P has left #wcag2ict 16:44:50 greggvanderheiden has left #wcag2ict