19:55:18 RRSAgent has joined #wai-wcag 19:55:18 logging to http://www.w3.org/2012/06/21-wai-wcag-irc 19:55:20 RRSAgent, make logs public 19:55:20 Zakim has joined #wai-wcag 19:55:22 Zakim, this will be WAI_WCAG 19:55:22 ok, trackbot; I see WAI_WCAG()4:00PM scheduled to start in 5 minutes 19:55:23 Meeting: Web Content Accessibility Guidelines Working Group Teleconference 19:55:23 Date: 21 June 2012 20:00:00 korn has joined #wai-wcag 20:00:01 WAI_WCAG()4:00PM has now started 20:00:08 +Bruce_Bailey 20:00:11 +Cooper 20:00:24 Andi has joined #wai-wcag 20:00:28 +[Oracle] 20:00:36 Zakim, Oracle is Peter_Korn 20:00:36 +Peter_Korn; got it 20:00:49 +??P2 20:00:59 +Andi_Snow_Weaver 20:00:59 zakim, ??P2 is Gregg_Vanderheiden 20:01:01 +Gregg_Vanderheiden; got it 20:01:02 marcjohlic has joined #wai-wcag 20:01:20 greggvanderheiden has joined #wai-wcag 20:01:30 +Marc_Johlic 20:01:45 +David_MacDonald 20:02:23 adam has joined #wai-wcag 20:02:41 +??P6 20:02:50 David has joined #wai-wcag 20:02:55 zakim, ??P6 is Adam_Solomon 20:02:55 +Adam_Solomon; got it 20:03:07 +James_Nurthen 20:03:24 robin has joined #wai-wcag 20:03:51 + +1.206.544.aaaa 20:03:52 regrets: Loretta_Guarino_Reid, Moe_Kraft, Kathleen_Wahlbin 20:04:00 zakim, aaaa is Robin_Tuttle 20:04:00 +Robin_Tuttle; got it 20:04:04 +[Microsoft] 20:04:20 zakim, Microsoft is Cherie_Eckholm 20:04:20 +Cherie_Eckholm; got it 20:04:21 +Andrew_Kirkpatrick 20:04:29 -Andrew_Kirkpatrick 20:04:36 +[Microsoft] 20:04:46 zakim, Microsoft is Alex_Li 20:04:46 +Alex_Li; got it 20:05:09 + +1.617.584.aabb 20:05:34 zakim, aabb is Andrew_Kirkpatrick 20:05:34 +Andrew_Kirkpatrick; got it 20:07:21 scribeNick: jamesn 20:07:42 +Andrew_Kirkpatrick.a 20:07:45 -Andrew_Kirkpatrick 20:08:20 https://www.w3.org/2002/09/wbs/35422/WCAG2ICT2/ 20:09:52 TOPIC: 1. SC 1.3.3 in Understanding WCAG 2.0 20:15:14 WCAG was designed to apply only to controls that were displayed on a web page. The intent was to avoid describing controls solely via references to visual or auditory cues. When applying this to instructions for operating physical hardware controls (e.g. a web kiosk with dedicated content), tactile cues on the hardware might be described (e.g. the arrow shaped key, the round key on the right side). This success criterion is not intended to 20:15:15 prevent the use of tactile cues in instructions. 20:15:52 Add the following to the intent of SC 1.3.3 in Understanding WCAG: WCAG was designed to apply only to controls that were displayed on a web page. The intent was to avoid describing controls solely via references to visual or auditory cues. When applying this to instructions for operating physical hardware controls (e.g. a web kiosk with dedicated content), tactile cues on the hardware might be described (e.g. the arrow shaped key, the 20:15:53 round key on the right side). This success criterion is not intended to prevent the use of tactile cues in instructions. 20:16:21 RESOLUTION: Add the text above to SC1.3.3 in Understanding WCAG2 20:16:38 Add the following note to the INTENT section of SC 2.4.6. Note: This success criterion does not REQUIRE heading and labels, just that, if they are provided, they be descriptive. Also note that, if headings are provided, they must be programmatically determinable per 1.3.1. 20:16:49 TOPIC: SC 2.4.6 in Understanding WCAG 2.0 20:24:38 RESOLUTION: Add Note to 2.4.6 Understanding doc - "Note: This success criterion does not REQUIRE heading and labels, just that, if they are provided, they be descriptive. Also note that, if headings are provided, they must be programmatically determinable per 1.3.1." 20:24:54 TOPIC: SC 3.2.1 and 3.2.2 in Understanding WCAG 2.0 20:30:14 -Robin_Tuttle 20:34:47 The following sentence be added to the INTENT section of SC 3.2.1 20:34:47 Note: What is meant by 'component' here is also sometimes called 'user interface element' or 'user interface component'. -- And -- the following sentence be added to the INTENT section of SC 3.2.2. Note: What is meant by 'component' and 'user interface component' here is also sometimes called 'user interface element'. 20:35:16 The following sentence be added to the INTENT section of SC 3.2.1 Note: What is meant by 'component' here is also sometimes called 'user interface element' or 'user interface component'. -- And -- the following sentence be added to the INTENT section of SC 3.2.2. Note: What is meant by 'component' and 'user interface component' here is also sometimes called 'user interface element'. 20:35:52 RESOLUTION: The following sentence be added to the INTENT section of SC 3.2.1 Note: What is meant by 'component' here is also sometimes called 'user interface element' or 'user interface component'. -- And -- the following sentence be added to the INTENT section of SC 3.2.2. Note: What is meant by 'component' and 'user interface component' here is also sometimes called 'user interface element'. 20:35:55 That the erratum for WCAG 2.0 reflect that in SC 3.2.1 the word component should be changed to “user interface component” and the following note added to the definition: Note: What is meant by 'component' or 'user interface component' here is also sometimes called 'user interface element'. 20:36:33 RESOLUTION: That the erratum for WCAG 2.0 reflect that in SC 3.2.1 the word component should be changed to user interface component and the following note added to the definition: Note: What is meant by 'component' or 'user interface component' here is also sometimes called 'user interface element'. 20:37:12 TOPIC: SC 3.2.4 in Understanding WCAG 2.0 20:41:16 q+ 20:41:29 -> http://www.w3.org/WAI/WCAG20/errata/ WCAG 2.0 Errata 20:44:50 -Cooper 20:45:06 +Cooper 20:48:20 Add to errata “fix the link for “set of web pages” in SC 3..2.4 to point to the “set of web pages” definition instead of “Web Pages” and add to INTENT – “Note: the link above to Web pages should have been a link to “set of web pages”. 20:48:56 q- 20:48:58 RESOLUTION: Add to errata fix the link for set of web pages in SC 3.2.4 to point to the set of web pages definition instead of Web Pages and add to INTENT Note: the link above to Web pages should have been a link to set of web pages. 20:50:38 a b 20:50:40 ack b 20:51:18 TOPIC: SC 3.3.2 in Understanding WCAG 2.0 20:52:46 q+ 20:53:40 q- 20:56:03 q+ 20:57:07 -Andrew_Kirkpatrick.a 20:59:02 -Bruce_Bailey 21:00:00 +Bruce_Bailey 21:00:18 Note: if labels are provided, the label relationship to the object labeled must be programmatically determined or described in text per SC 1.3.1. 21:00:37 queue 21:00:41 queue 21:00:46 q? 21:01:15 ack k 21:02:35 -Bruce_Bailey 21:03:08 -Adam_Solomon 21:03:17 RESOLUTION: Add note to 3.3.2 of " Note: if labels are provided, the label relationship to the object labeled must be programmatically determined or described in text per SC 1.3.1." 21:03:39 +Bruce_Bailey 21:06:07 TOPIC: 4.1.1 i nUnderstanding WCAG 2.0 21:06:59 q+ 21:08:38 q+ 21:12:27 q+ 21:13:26 q- 21:13:28 ack David 21:14:44 ack k 21:15:20 -Peter_Korn 21:15:32 q+ 21:15:53 -Bruce_Bailey 21:16:25 +Bruce_Bailey 21:22:31 q+ 21:23:35 -Bruce_Bailey 21:24:00 +Bruce_Bailey 21:24:17 ack me 21:31:53 ack a 21:32:02 ack b 21:32:03 ack b 21:36:06 -James_Nurthen 21:36:18 If authors do not write or edit markup languages directly they can assume this provision is met. 21:36:42 scribe:David 21:37:36 resolution: the WCAG group does not accept the following note: If authors do not write or edit markup languages directly they can assume this provision is met. 21:38:06 s/resolution/Resolution 21:39:23 s/Resolution/RESOLUTION: 21:39:24 This is not meant to apply to markup languages that are not parsed by general purpose web browsers and assistive technologies. 21:40:44 RESOLUTION: The working group agrees with the sentiment but cannot find the right wording so returns it... for more consideration. "This is not meant to apply to markup languages that are not parsed by general purpose web browsers and assistive technologies." 21:44:07 https://www.w3.org/2002/09/wbs/35422/20120621_PF-UA/results 21:44:28 -Alex_Li 21:46:50 NOTE: With the exception of one success criterion (1.4.4 - that specifically mentions that the effect specified by the success criterion must be achieved without relying on an assistive technology) authors can meet the success criteria with content that assumes use of an assistive technology (or access features in use agents) by the user, where such assistive technologies (or access features in user agents) exist and are available to the 21:46:50 user. 21:52:39 -Cherie_Eckholm 21:52:40 -Cooper 21:52:41 -Andi_Snow_Weaver 21:52:44 RESOLUTION: add the note... NOTE: With the exception of one success criterion (1.4.4 - that specifically mentions that the effect specified by the success criterion must be achieved without relying on an assistive technology) authors can meet the success criteria with content that assumes use of an assistive technology (or access features in use agents) by the user, where such assistive... 21:52:46 ...technologies (or access features in user agents) exist and are available to the user. 21:53:07 -Bruce_Bailey 21:53:17 -Marc_Johlic 21:53:25 -Gregg_Vanderheiden 21:53:42 zakim, bye 21:53:42 leaving. As of this point the attendees were Bruce_Bailey, Cooper, Peter_Korn, Andi_Snow_Weaver, Gregg_Vanderheiden, Marc_Johlic, David_MacDonald, Adam_Solomon, James_Nurthen, 21:53:42 Zakim has left #wai-wcag 21:53:45 ... +1.206.544.aaaa, Robin_Tuttle, Cherie_Eckholm, Andrew_Kirkpatrick, Alex_Li, +1.617.584.aabb 21:53:55 rrsagent, make log public 21:54:34 rrsagent, make minutes 21:54:34 I have made the request to generate http://www.w3.org/2012/06/21-wai-wcag-minutes.html David 22:52:20 MichaelC_ has joined #wai-wcag 22:53:10 chair: Gregg_Vanderheiden 22:53:26 rrsagent, make minutes 22:53:26 I have made the request to generate http://www.w3.org/2012/06/21-wai-wcag-minutes.html MichaelC_ 22:56:33 rrsagent, bye 22:56:33 I see no action items 22:56:35 zakim, bye