13:49:26 RRSAgent has joined #wcag2ict 13:49:26 logging to http://www.w3.org/2012/07/10-wcag2ict-irc 13:49:28 RRSAgent, make logs world 13:49:28 Zakim has joined #wcag2ict 13:49:30 Zakim, this will be 2428 13:49:30 ok, trackbot; I see WAI_(WCAG2ICT)10:00AM scheduled to start in 11 minutes 13:49:31 Meeting: WCAG2ICT Task Force Teleconference 13:49:31 Date: 10 July 2012 13:49:45 chair: Andi_Snow-Weaver 13:52:42 agenda+ Re-survey on 2.4.2 Page Titled https://www.w3.org/2002/09/wbs/55145/JUL102012/results 13:53:22 agenda+ Draft proposed edits to WCAG 2.0 resolution on 1.3.1 Info and Relationships http://lists.w3.org/Archives/Public/public-wcag2ict-tf/2012Jul/0029.html 13:53:50 agenda+ Summary of WCAG 2.0 decision on SC we sent for their review http://lists.w3.org/Archives/Public/public-wcag2ict-tf/2012Jul/0031.html 13:54:04 agenda+ Confirm next meeting time; action items; 13:56:49 WAI_(WCAG2ICT)10:00AM has now started 13:56:56 +Andi_Snow_Weaver 13:57:12 MaryJo has joined #wcag2ict 13:58:15 korn has joined #wcag2ict 13:59:05 +??P3 13:59:16 Loic has joined #wcag2ict 13:59:30 zakim, ??P3 is Gregg_Vanderheiden 13:59:30 +Gregg_Vanderheiden; got it 13:59:31 +Cooper 13:59:33 greggvanderheiden has joined #wcag2ict 13:59:44 +[Oracle] 13:59:51 +??P6 13:59:53 zakim, Oracle has Peter 13:59:53 +Peter; got it 13:59:58 +David_MacDonald 14:00:00 zakim, Oracle has Peter_Korn 14:00:00 +Peter_Korn; got it 14:00:09 +Mary_Jo_Mueller 14:00:28 zakim, ??P6 is Loïc_Martínez_Normand 14:00:28 +Loïc_Martínez_Normand; got it 14:00:32 +[Microsoft] 14:00:40 +Kiran_Keja 14:00:40 Mike has joined #wcag2ict 14:00:44 zakim, Microsoft is Alex_Li 14:00:44 +Alex_Li; got it 14:00:57 +Bruce_Bailey 14:01:26 janina has joined #wcag2ict 14:01:34 +??P15 14:01:35 BBailey has joined #wcag2ict 14:01:37 zakim, who is on the phone? 14:01:37 On the phone I see Andi_Snow_Weaver, Gregg_Vanderheiden, Cooper, [Oracle], Loïc_Martínez_Normand, David_MacDonald, Mary_Jo_Mueller, Alex_Li, Kiran_Keja, Bruce_Bailey, ??P15 14:01:37 [Oracle] has Peter_Korn 14:01:48 zakim, ??P15 is Mike_Pluke 14:01:48 +Mike_Pluke; got it 14:01:49 +Al_Hoffman 14:02:09 alex_ has joined #wcag2ict 14:02:28 Kiran has joined #wcag2ict 14:02:39 +??P17 14:02:41 scribe: MaryJo 14:02:46 zakim, ??P17 is Janina_Sajka 14:02:46 +Janina_Sajka; got it 14:03:11 zakin, next item 14:03:27 zakim, next item 14:03:27 agendum 1. "Re-survey on 2.4.2 Page Titled https://www.w3.org/2002/09/wbs/55145/JUL102012/results" taken up [from Andi] 14:03:41 -Al_Hoffman 14:04:28 +Al_Hoffman 14:05:32 For documents this applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) with the word “document” substituted for Web Page. 14:06:00 For software user interfaces, the precise analog to "web page" in the context of this success criterion is difficult to define. However, since there is almost always a single user interface component associated with top-most explicit groupings of user interface components (things like "windows", "dialog boxes", "frames", and "screens"), and since 4.1.2 requires that every user interface component has a programmatically determined name, conforming to 14:06:09 Pierce's edit: Note: A document's filename, as well as its title attribute, are both considered types of titles. While the filename is more universally presented by assistive technologies, the title attribute is more formally correct. 14:06:53 q+ 14:07:01 PK: Pierce's change to reverse the 2nd sentence looks fine, and Loic's edits look fine too. 14:07:09 q+ 14:07:14 ack korn 14:07:19 q- 14:07:21 q+ 14:07:50 q- 14:07:53 GV: Concerned about ordering of whether to provide title or file name first - one is supported by AT's more and one is more formally correct. Want to make sure we give the right advice. 14:09:18 q+ David_MacDonald 14:09:22 ack david 14:09:25 PK: Can make it clear that doing both increases the chances of this SC being met. Need to come up with right words. 14:10:03 -Gregg_Vanderheiden 14:10:21 q+ 14:10:26 greggvanderheid-1 has joined #wcag2ict 14:11:04 Al: Filenames aren't really aren't equivalent to the proper provision of a title, which is the point Pierce is making. 14:11:20 +??P3 14:11:40 zakim, ??P3 is Gregg_Vanderheiden 14:11:40 +Gregg_Vanderheiden; got it 14:11:48 ack mike 14:12:04 q+ 14:12:10 q+ 14:12:16 MP: There are often more limitations on file names, so the title is preferrable. 14:12:46 Q+ 14:13:06 ack loic 14:13:20 ack korn 14:13:49 Loic: Most people are comfortable with making short file names meaningful. 14:14:31 PK: If there are a large number of documents being named, it is difficult to name the files so they are easy to distinguish from each other in a meaningful way. 14:14:41 ACK g 14:14:53 Note: A document's filename, as well as its title attribute, are both considered types of titles. While the filename is more universally presented by assistive technologies, the title attribute is more formally correct. Using both provides the best accessibility support. 14:15:31 David has joined #wcag2ict 14:15:59 +1 to gv's proposal 14:18:18 Note: A document's filename, as well as its title attribute, are both considered types of titles. While the filename is more universally presented by assistive technologies, the title attribute is more formally correct. Using both provides the best chance of being accessible to the user. 14:18:21 Alex: 'Accessibility support' is a concept we haven't discussed yet in the task force and not a term we have defined. 14:18:45 Note: A document's filename, as well as its title attribute, are both considered types of titles. While the filename is more universally presented by assistive technologies, the title attribute is more formally correct. Using both provides the best chance of being accessible to a user. 14:19:08 Note: A document's filename, as well as its title attribute, are both considered types of titles. While the filename is more universally presented by assistive technologies, the title attribute is more formally correct. Using both provides the best chance of being accessible to different users. 14:19:15 Or "greater liklihood" ? 14:19:43 +1 14:19:54 RESOLUTION: accept note for 2.4.2 as amended 14:21:05 AS: Loic's edit for the software part of 2.4.2. 14:21:07 -Mike_Pluke 14:21:16 q+ 14:21:28 +??P15 14:21:52 q+ 14:22:27 zakim, ??P15 is Mike_Pluke 14:22:27 +Mike_Pluke; got it 14:22:36 q+ 14:22:54 GV: Fundamental difference in this edit is that it implies we know which part needs naming - the topmost grouping. 14:24:01 ack korn 14:25:57 q+ 14:26:13 q+ 14:27:23 Loic: Would really like to see 'interaction context' in the first sentence. In lieu of using that term, thinks that 'top-most explicit groupings of user interface components' is the closest match to that term in this context. 14:27:41 q+ 14:28:21 q- 14:28:40 q- 14:28:42 friendly amendment to make it less verbose? "...conforming to 4.1.2 for the top-most explicit groupings of user interface components would thereby mean conformance to this success criterion if the name described its topic or purpose." 14:28:47 ack mike 14:28:47 MP: We don't want to say this SC is redundant, as 4.1.2 does cover the need for a name, but doesn't cover the aspect of it being a meaningful or descriptive name. 14:28:49 ack gregg 14:30:07 GV: We can make an edit to this to emphasize this aspect. Since you made a name in 4.1.2, if you make the name descriptive then you satisfy this SC. 14:30:16 "...conforming to 4.1.2 for the name of the top-most explicit groupings of user interface components would thereby mean conformance to this success criterion if the name described its topic or purpose." 14:30:57 q+ 14:31:12 q+ 14:31:43 GV: We need to determine which term to use: 'software aspects of prodcts', 'software user interfaces', etc. 14:33:01 ack korn 14:33:45 q+ 14:34:16 PK: A lot of this SC has to do with finding a single web page out of a lot of Web pages. In the software world, there are typically less applications or windows to filter through to find the right one. 14:34:59 PK: Software use cases are different, so we need to have a good analog that makes sense. 14:35:46 For software user interfaces, the precise analog to "web page" in the context of this success criterion is difficult to define. However, since there is almost always a single user interface component associated with top-most explicit groupings of user interface components (things like "windows", "dialog boxes", "frames", and "screens"), and since 4.1.2 requires that every user interface component has a programmatically determined name, 14:35:47 conforming to 4.1.2 would thereby mean that is success criterion was met if the name for the user interface component associated with top-most explicit groupings of user interface components described its topic or purpose. 14:36:12 For software user interfaces, the precise analog to "web page" in the context of this success criterion is difficult to define. However, since there is almost always a single user interface component associated with top-most explicit groupings of user interface components (things like "windows", "dialog boxes", "frames", and "screens"), and since 4.1.2 requires that every user interface component has a programmatically determined name, 14:36:13 conforming to 4.1.2 would thereby mean that this success criterion was met if the name for the user interface component associated with top-most explicit groupings of user interface components described its topic or purpose. 14:36:24 ack loic 14:36:41 PK: We shouldn't be too precise in this, to make sure that future technologies can be covered without having to readress this SC. 14:37:11 Loic: Agrees with the above proposed text from Gregg. 14:37:58 Loic: This is only applicable to software that has a user interface, not DLL's, etc. 14:38:22 "If the names of all explicit groupings of user interface components are descriptive of the title or purpose, it will certainly be the case that all of the top-most ones are" 14:39:48 AS: We have a work item to go back and look at the terms used to make them consistent throughout the document. 14:40:13 ack andi 14:40:17 q+ 14:40:27 ack mike 14:40:28 AS: 'Product' term is a problem, because this SC should also apply to software developed in-house for internal use that is not productized. 14:40:50 q+ 14:41:14 ack gregg 14:42:11 MichaelC has joined #wcag2ict 14:42:39 GV: Agree that we do need to go back and revisit terms we came up with for the SCs to make them consistent. 14:42:59 alex_ has joined #wcag2ict 14:44:43 q+ 14:44:47 since 4.1.2 requires that every user interface component has a programmatically determined name, conforming to 4.1.2 would thereby mean that this success criterion was met if the name for the user interface component associated with top-most explicit groupings of user interface components described its topic or purpose. If the names of all explicit groupings of user interface components are 14:44:47 descriptive of the title or purpose, it will certainly be the case that all of the top-most ones are. 14:45:26 +1 14:45:27 ack korn 14:45:32 +1 14:45:35 ack g 14:46:35 Amended in the meeting: For documents this applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) with the word “document” substituted for Web Page. 14:47:20 Note: A document's filename, as well as its title attribute, are both considered types of titles. While the filename is more universally presented by assistive technologies, the title attribute is more formally correct. Using both provides the best chance of being accessible to different users. 14:47:49 For software user interfaces, the precise analog to "web page" in the context of this success criterion is difficult to define. However, since there is almost always a single user interface component associated with top-most explicit groupings of user interface components (things like "windows", "dialog boxes", "frames", and "screens"), and since 4.1.2 requires that every user interface 14:47:49 component has a programmatically determined name, 14:48:06 since 4.1.2 requires that every user interface component has a programmatically determined name, conforming to 4.1.2 would thereby mean that this success criterion was met if the name for the user interface component associated with top-most explicit groupings of user interface components described its topic or purpose. If the names of all explicit groupings of user interface components are 14:48:06 descriptive of the title or purpose, it will certainly be the case that all of the top-most ones are. 14:48:56 Note: Where the accessibility services of the platform include a description attribute in addition to a name attribute, the description attribute and the name attribute are often used together to provide both a short cue and longer description of the topic or purpose. 14:49:06 RESOLUTION: Accept 2.4.2 as amended in version #5. 14:49:30 zakim, next item 14:49:30 agendum 2. "Draft proposed edits to WCAG 2.0 resolution on 1.3.1 Info and Relationships http://lists.w3.org/Archives/Public/public-wcag2ict-tf/2012Jul/0029.html" taken up [from 14:49:34 ... Andi] 14:49:45 q+ 14:50:46 ack alex 14:53:49 Alex: Concerned that 2.4.2 text doesn't explicitly exclude command line interfaces where the concept of a 'page title' doesn't exist. 14:55:15 +1 to Peter. Only one screen there is nothing to look for. 14:56:00 PK: If multiple CLI windows are being used, the operating system is handling them. 14:56:43 AS: If this is important to use the SC and asses for CLI interfaces, we need to circle back at a later time with this in mind. 14:57:14 q+ 14:57:56 ack gregg 14:58:06 AS: WCAG didn't accept the text exactly as we proposed, but did agree to put part of our proposal in. Peter and Al had concerns and the link points to 2 possible edits to what WCAG agreed to add. 14:58:50 zakim, who's noisy 14:58:50 I don't understand 'who's noisy', David 14:59:08 -Cooper 14:59:41 GV: Likes Andi's wording. Even though it is more verbose, it is clearer in meaning. 15:00:33 q+ 15:01:02 q- 15:01:06 Sighted users perceive structure AND RELATIONSHIPS through various visual 15:01:06 cues — headings are often in a larger, bold font separated from paragraphs 15:01:06 by blank lines; list items are preceded by a bullet and perhaps indented; 15:01:06 paragraphs are separated by a blank line; form fields may be positioned as 15:01:06 groups that share text labels; a different background color may be used to 15:01:06 indicate that several items are related to each other; words that have 15:01:08 special status are indicated by changing the font family and /or bolding, 15:01:10 italicizing, or underlining them; ITEMS THAT SHARE A COMMON CHARACTERISTIC 15:01:12 ARE ORGANIZED INTO A TABLE WHERE THE RELATIONSHIP OF CELLS SHARING THE SAME 15:01:15 ROW OR COLUMN AND THE RELATIONSHIP OF EACH CELL TO ITS ROW AND/OR COLUMN 15:01:17 HEADER ARE NECESSARY FOR UNDERSTANDING; and so on. Having THESE structures 15:01:18 and relationships programmatically determined or available in text ensures 15:01:20 that information important for comprehension will be perceivable by all. 15:02:01 Zakim, who's making noise? 15:02:09 AS: Al or Pierce should try to attend the WCAG meeting to be there when the text is agreed upon or edited. 15:02:23 David, listening for 10 seconds I heard sound from the following: Andi_Snow_Weaver (27%), Gregg_Vanderheiden (13%), David_MacDonald (9%), Alex_Li (15%) 15:03:24 Sighted users perceive structure AND RELATIONSHIPS through various visual 15:03:25 cues — headings are often in a larger, bold font separated from paragraphs 15:03:26 by blank lines; list items are preceded by a bullet and perhaps indented; 15:03:28 paragraphs are separated by a blank line; form fields may be positioned as 15:03:28 RESOLUTION: Accept further modification to the Intent for 1.3.1 as proposed in the meeting. 15:03:29 groups that share text labels; a different background color may be used to 15:03:31 indicate that several items are related to each other; words that have 15:03:32 special status are indicated by changing the font family and /or bolding, 15:03:34 italicizing, or underlining them; ITEMS THAT SHARE A COMMON CHARACTERISTIC 15:03:35 ARE ORGANIZED INTO A TABLE WHERE THE RELATIONSHIP OF CELLS SHARING THE SAME 15:03:37 ROW OR COLUMN AND THE RELATIONSHIP OF EACH CELL TO ITS ROW AND/OR COLUMN 15:03:38 HEADER ARE NECESSARY FOR UNDERSTANDING; and so on. Having THESE structures 15:03:39 and relationships programmatically determined or available in text ensures 15:03:40 that information important for comprehension will be perceivable by all. 15:04:10 http://lists.w3.org/Archives/Public/public-wcag2ict-tf/2012Jul/0029.html 15:04:34 Zakim, who's noisy? 15:04:45 David, listening for 10 seconds I heard sound from the following: Andi_Snow_Weaver (30%), Mary_Jo_Mueller (46%), Alex_Li (5%) 15:04:59 zakim, next item 15:04:59 agendum 3. "Summary of WCAG 2.0 decision on SC we sent for their review http://lists.w3.org/Archives/Public/public-wcag2ict-tf/2012Jul/0031.html" taken up [from Andi] 15:05:42 RESOLUTION: Accept proposal #1 modification to the Intent for 1.3.1 from email http://lists.w3.org/Archives/Public/public-wcag2ict-tf/2012Jul/0029.html. 15:06:04 https://sites.google.com/site/wcag2ict/home/2-operable/21-make-all-functionality-available-from-a-keyboard/211-keyboard 15:06:43 Note: This does not imply that software must directly support OR PROVIDE a keyboard or "keyboard interface". UNDERLYING Platform software may provide device independent input services to applications that enable operation via a keyboard. Software that supports operation via such platform device independent services would be operable by a keyboard and would comply. 15:06:56 q+ 15:07:16 q+ 15:07:35 ack loic 15:08:11 q+ 15:08:16 ack bbailey 15:08:45 q+ 15:08:50 ack gregg 15:09:21 ack g 15:09:28 ack mike 15:10:11 Note: This does not imply that software must directly support a keyboard or "keyboard interface" OR PROVIDE A SOFT KEYBOARD. UNDERLYING Platform software may provide device independent input services to applications that enable operation via a keyboard. Software that supports operation via such platform device independent services would be operable by a keyboard and would comply. 15:10:12 q+ 15:10:33 +1 To Andi's edit 15:10:38 ack korn 15:11:33 Loic: Concerned that 'provide a keyboard' would be misinterpreted as 'provide a hardware keyboard'. 15:12:11 PK: Propose we add this edit to our document and after public comment we can send this and any other further WCAG updates then. 15:12:20 Loic: Would prefer to send this to WCAG now. 15:12:34 zakim, who is talking? 15:12:44 korn, listening for 10 seconds I heard sound from the following: Gregg_Vanderheiden (93%), David_MacDonald (4%) 15:14:55 -Gregg_Vanderheiden 15:15:16 +1 15:15:24 +1 15:15:26 +??P3 15:15:26 This does not imply that software must directly support a keyboard or "keyboard interface". NOR DOES IT REQUIRE THAT SOFTWARE PROVIDE A SOFT KEYBOARD. UNDERLYING Platform software may provide device independent input services to applications that enable operation via a keyboard. Software that supports operation via such platform device independent services would be operable by a keyboard 15:15:26 and would comply. 15:15:34 +1 15:15:47 q+ 15:15:50 zakim, ??P3 is Gregg_Vanderheiden 15:15:50 +Gregg_Vanderheiden; got it 15:16:15 This does not imply that software must directly support a keyboard or "keyboard interface". NOR DOES IT IMPLY THAT SOFTWARE PROVIDE A SOFT KEYBOARD. UNDERLYING Platform software may provide device independent input services to applications that enable operation via a keyboard. Software that supports operation via such platform device independent services would be operable by a keyboard 15:16:15 and would comply. 15:16:58 Again to be parallel, "... nor does it imply that software MUST PROVIDE a soft keyboard" 15:17:09 This does not imply that software must directly support a keyboard or "keyboard interface". NOR DOES IT IMPLY THAT SOFTWARE MUST PROVIDE A SOFT KEYBOARD. UNDERLYING Platform software may provide device independent input services to applications that enable operation via a keyboard. Software that supports operation via such platform device independent services would be operable by a keyboard 15:17:09 and would comply. 15:18:52 RESOLUTION: Send edit proposed in meeting for 2.1.1 to WCAG. 15:19:07 https://sites.google.com/site/wcag2ict/home/2-operable/22-provide-users-enough-time-to-read-and-use-content/222-pause-stop-hide 15:19:57 Proposed: Note: While the success criteria uses the term "information", the WCAG 2.0 INTENT section makes it clear that this is to be applied to all content. Any content, whether informative or decorative, that blinks or moves creates a significant accessibility barrier for some users with cognitive, learning, and other disabilities." 15:20:18 Any content, whether informative or decorative, that IS UPDATED AUTOMATICALLY MAY CREATE AN ACCESSIBILITY BARRIER IF USERS DO NOT KNOW IT HAS UPDATED. FURTHER, ANY CONTENT, WHETHER INFORMATIVE OR DECORATIVE THAT blinks or moves creates a significant accessibility barrier for some users with cognitive, learning, and other disabilities." 15:20:34 WCAG approved: Note: While the success criteria uses the term "information", the WCAG 2.0 INTENT section makes it clear that this is to be applied to all content. Any content, whether informative or decorative, that IS UPDATED AUTOMATICALLY MAY CREATE AN ACCESSIBILITY BARRIER IF USERS DO NOT KNOW IT HAS UPDATED. FURTHER, ANY CONTENT, WHETHER INFORMATIVE OR DECORATIVE THAT blinks or moves 15:20:34 creates a significant accessibility barrier for some users with cognitive, learning, and other disabilities." 15:20:38 AS: The WCAG changes to our proposed text seems editorial. Only the second sentence was changed. 15:20:41 q+ 15:20:45 q- 15:21:00 GV: It added back the aspect about 'automatically updating'. 15:21:37 ack loic 15:21:55 Loic: The explanation for the user to know about updating information is not covered by this SC. This SC is about user control over the updating content. 15:22:59 Any content, wether informative or decorative, that is updated automatically, blinks or moves creates a significant accessibility barrier... 15:23:10 Note: While the success criteria uses the term "information", the WCAG 2.0 INTENT section makes it clear that this is to be applied to all content. Any content, whether informative or decorative, that IS UPDATED AUTOMATICALLY, BLINKS OR MOVES MAY CREATE AN ACCESSIBILITY BARRIER. 15:23:21 GV: Agrees with Loic's suggestion. 15:23:58 RESOLUTION: Send edits proposed in meeting for 2.2.2 to WCAG. 15:25:34 q+ 15:25:57 Conditionally accepted by WCAG: 2.2.1, 3.2.1, 3.2.2, 3.3.4, 4.1.2 15:26:00 ack mike 15:26:06 q+ Al_Hoffman 15:26:14 GV: WCAG group found some situations where our criteria could be met, but content would still fail the SC. 15:26:28 q+ 15:27:10 AS: WCAG wants us to remove the exception we had for documents that can automatically comply. 15:27:17 ack al 15:28:06 Loic: We may need to look at all of these SC to make sure it makes sense with the sentence removed. 15:28:32 q+ 15:28:42 action: Andi to check these five success criteria (2.2.1, 3.2.1, 3.2.2, 3.3.4, 4.1.2) to make sure documents are still covered if we drop the sentence. 15:28:43 Created ACTION-29 - Check these five success criteria (2.2.1, 3.2.1, 3.2.2, 3.3.4, 4.1.2) to make sure documents are still covered if we drop the sentence. [on Andi Snow-Weaver - due 2012-07-17]. 15:28:52 ack loic 15:29:06 ack korn 15:29:19 +1 15:29:23 PK: Did go through the SC and it did make sense, but agrees that Andi should take a 2nd look. 15:31:02 Al: Proposes that an example is added to each one of these. 15:31:29 Al: These examples can be added after our first draft is complete. 15:31:32 q+ 15:32:08 action: Andi to work with Gregg and Peter to gather examples provided by WCAG for 2.2.1, 3.2.1, 3.2.2, 3.3.4, 4.1.2 and draft examples to add after first public working draft 15:32:08 Created ACTION-30 - Work with Gregg and Peter to gather examples provided by WCAG for 2.2.1, 3.2.1, 3.2.2, 3.3.4, 4.1.2 and draft examples to add after first public working draft [on Andi Snow-Weaver - due 2012-07-17]. 15:33:37 Al: Doesn't want to remove useful guidance if the examples are obscure. 15:33:44 q+ 15:33:56 q- 15:34:37 GV: Could add 'Except for unusual cases such as...' and then give the guidance we have. 15:35:15 I'm sorry, but I have to leave now - we are over the meeting time and I have another thing I need to go to. 15:35:35 GV: Or edit our text with something like: "For pages that are nothing but text and simple hypertext links..." 15:35:41 korn has left #wcag2ict 15:37:15 RESOLUTION: Accept WCAG proposed edits for 2.2.1, 3.2.1, 3.2.2, 3.3.4, 4.1.2 and work on examples later. 15:37:41 -Al_Hoffman 15:37:52 -Alex_Li 15:37:54 -Mary_Jo_Mueller 15:37:55 -Mike_Pluke 15:37:55 -Andi_Snow_Weaver 15:37:56 janina has left #wcag2ict 15:37:58 -David_MacDonald 15:38:00 rrsagent, make minutes 15:38:00 I have made the request to generate http://www.w3.org/2012/07/10-wcag2ict-minutes.html Andi 15:38:01 -Bruce_Bailey 15:38:03 -Janina_Sajka 15:38:06 -Loïc_Martínez_Normand 15:38:07 -Gregg_Vanderheiden 15:38:08 -Kiran_Keja 15:38:27 zakim, bye 15:38:27 leaving. As of this point the attendees were Andi_Snow_Weaver, Gregg_Vanderheiden, Cooper, Peter, David_MacDonald, Peter_Korn, Mary_Jo_Mueller, Loïc_Martínez_Normand, 15:38:27 Zakim has left #wcag2ict 15:38:30 ... Kiran_Keja, Alex_Li, Bruce_Bailey, Mike_Pluke, Al_Hoffman, Janina_Sajka 15:38:34 rrsagent, make minutes 15:38:34 I have made the request to generate http://www.w3.org/2012/07/10-wcag2ict-minutes.html Andi 16:03:59 MichaelC has joined #wcag2ict 16:40:07 greggvanderheiden has joined #wcag2ict 17:15:37 greggvanderheiden has joined #wcag2ict 17:18:24 greggvanderheiden has joined #wcag2ict