20:55:56 RRSAgent has joined #wai-wcag 20:55:56 logging to http://www.w3.org/2013/01/31-wai-wcag-irc 20:55:58 RRSAgent, make logs public 20:55:58 Zakim has joined #wai-wcag 20:56:00 Zakim, this will be WAI_WCAG 20:56:00 ok, trackbot; I see WAI_WCAG()4:00PM scheduled to start in 4 minutes 20:56:01 Meeting: Web Content Accessibility Guidelines Working Group Teleconference 20:56:01 Date: 31 January 2013 20:57:17 WAI_WCAG()4:00PM has now started 20:57:24 +Gregg_Vanderheiden 20:57:48 greggvanderheiden has joined #wai-wcag 21:00:25 Ryladog has joined #wai-wcag 21:00:27 +Robin_Tuttle 21:00:59 +??P2 21:01:08 robin has joined #wai-wcag 21:01:33 +[Oracle] 21:01:43 jamesn has joined #wai-wcag 21:01:51 Loretta has joined #WAI-WCAG 21:01:53 +Katie_Haritos_Shea 21:02:04 zakim, who is on the call? 21:02:04 On the phone I see Gregg_Vanderheiden, Robin_Tuttle, Michael_Cooper, [Oracle], Katie_Haritos_Shea 21:02:15 +Loretta_Guarino_Reid 21:02:22 Judy has joined #wai-wcag 21:02:49 +Judy 21:03:26 zakim, who is here? 21:03:26 On the phone I see Gregg_Vanderheiden, Robin_Tuttle, Michael_Cooper, [Oracle], Katie_Haritos_Shea, Loretta_Guarino_Reid, Judy 21:03:28 On IRC I see Judy, Loretta, jamesn, robin, Ryladog, greggvanderheiden, Zakim, RRSAgent, MichaelC, trackbot 21:04:10 regrets+ Kerstin_Probiesch 21:04:33 regrets+ Gian_Wild 21:04:53 regrets+ Kathy_Wahlbin 21:05:06 +Andrew_Kirkpatrick 21:06:44 scribe: robin 21:06:49 +David_MacDonald 21:08:14 https://sites.google.com/site/wcag2ict/ 21:08:25 David has joined #wai-wcag 21:09:25 TOPIC: Comment LC-2673 21:14:14 AWK has joined #wai-wcag 21:14:30 q+ 21:19:01 ack j 21:19:54 zakim, who is on the phone? 21:19:54 On the phone I see Gregg_Vanderheiden, Robin_Tuttle, Michael_Cooper, [Oracle], Katie_Haritos_Shea, Loretta_Guarino_Reid, Judy, Andrew_Kirkpatrick, David_MacDonald 21:20:13 zakim, Oracle has James_Nurthen 21:20:13 +James_Nurthen; got it 21:25:47 Comment LC-2673: tabled to later 21:26:02 TOPIC: Comment LC-2663 21:27:41 Alex is going to join, unless he can get Cherie to do so 21:30:15 This document does not seek to determine which WCAG 2.0 provisions (principles, guidelines, or success criteria) should or should not apply to non-web ICT, but rather how they would apply, if applied. 21:32:01 +[Microsoft] 21:32:30 zakim, Microsoft has Alex_Li 21:32:30 +Alex_Li; got it 21:33:25 Please note paragraph 2 of the introduction which points out that " This document does not seek to determine which WCAG 2.0 provisions (principles, guidelines, or success criteria) should or should not apply to non-web ICT, but rather how they would apply, if applied." also that " Although this document covers a wide range of issues, it is not able to address all the needs of all people with disabilities. Because WCAG 2.0 was develo[CUT] 21:33:25 the Web, addressing accessibility for non-Web documents and software may involve provisions beyond those included in this document. Authors and developers are encouraged to seek relevant advice about current best practices to ensure that non-Web documents and software are accessible, as far as possible, to people with disabilities." 21:37:59 RESOLUTION: Accepted as amended 21:38:24 TOPIC: Comment LC-2673 21:40:34 q+ 21:40:45 q+ to ask a clarification about what the "this" is 21:41:26 q+ 21:42:37 q+ 21:44:49 q+ 21:44:54 ack j 21:44:54 Judy, you wanted to ask a clarification about what the "this" is and to 21:45:34 q- 21:46:13 ack d 21:47:24 q+ 21:49:40 How about: "WCAG2ICT was initiated in response to the US Access Board’s ANPRM for new Section 508 standards which apply WCAG 2.0 standards to web content and ICT in general, and at the request of multiple W3C members who sought to provide guidance around how this would be accomplished – the WCAG2ICT document is the document which was created to meet this identified need." (instead of the first paragraph) 21:50:53 Jud, I'm ont sure what document you are reviewing. 21:53:10 My error - I was looking at the wrong issue number. 21:54:43 The W3C created a task force the brought in ICT companies to join with WCAG member to create this guidance because it would both identify specific issues in apply WCAG 2.0 to ICT (documents and software) and increase the likelihood that these applications of WCAG 2.0 will be consistent, and in keeping with the Principles, Guidelines, and Intent of WCAG 2.0. 21:54:57 q+ 21:55:08 q- 21:56:49 The W3C created a task force that brought in ICT companies, and M376 committee to join with WCAG member to create this guidance because it would both identify specific issues in apply WCAG 2.0 to ICT (documents and software) and increase the likelihood that these applications of WCAG 2.0 will be consistent, and in keeping with the Principles, Guidelines, and Intent of WCAG 2.0. 21:58:30 ack a 22:01:15 alex has joined #wai-wcag 22:01:42 change the last sentence of the first paragraph 22:01:43 The W3C created a task force that brought in ICT companies, and M376 committee to join with WCAG member to create this guidance because it would both identify specific issues in apply WCAG 2.0 to ICT (documents and software) and increase the likelihood that these applications of WCAG 2.0 will be consistent, and in keeping with the Principles, Guidelines, and Intent of WCAG 2.0. 22:02:22 By doing this we increase the likelihood that these applications of WCAG 2.0 will be consistent, and in keeping with the Principles, Guidelines, and Intent of WCAG 2.0. 22:02:40 Through this task force, the W3C is developing a common understanding of how WCAG 2.0 might apply to non-web ICT for organizations and entities who are already seeking to so adopt and apply WCAG 2.0. By doing this we increase the likelihood that these applications of WCAG 2.0 will be consistent, and in keeping with the Principles, Guidelines, and Intent of WCAG 2.0. 22:03:51 The W3C created a task force that brought in ICT companies, and the M376 committee, and Access Board to join with WCAG member to create this guidance because it would both identify specific issues in apply WCAG 2.0 to ICT (documents and software) and increase the likelihood that these applications of WCAG 2.0 will be consistent, and in keeping with the Principles, Guidelines, and Intent of WCAG 2.0. 22:04:36 Please note paragraph 2 of the introduction which points out that " This document does not seek to determine which WCAG 2.0 provisions (principles, guidelines, or success criteria) should or should not apply to non-web ICT, but rather how they would apply, if applied." also that " Although this document covers a wide range of issues, it is not able to address all the needs of all people with disabilities. Because WCAG 2.0 was develo[CUT] 22:04:37 the Web, addressing accessibility for non-Web documents and software may involve provisions beyond those included in this document. Authors and developers are encouraged to seek relevant advice about current best practices to ensure that non-Web documents and software are accessible, as far as possible, to people with disabilities." 22:05:31 Please note that the introduction points out (in paragraphs 7 and 2) that " This document does not seek to determine which WCAG 2.0 provisions (principles, guidelines, or success criteria) should or should not apply to non-web ICT, but rather how they would apply, if applied." also that " Although this document covers a wide range of issues, it is not able to address all the needs of all people with disabilities. Because WCAG 2.0 was 22:05:31 developed for the Web, addressing accessibility for non-Web documents and software may involve provisions beyond those included in this document. Authors and developers are encouraged to seek relevant advice about current best practices to ensure that non-Web documents and software are accessible, as far as possible, to people with disabilities." 22:13:54 Loretta has joined #WAI-WCAG 22:14:09 ================== [WCAG WG] Comments ============== 22:14:09 change the last sentence of the first paragraph 22:14:11 The W3C created a task force that brought in ICT companies, and the M376 committee, and Access Board to join with WCAG member to create this guidance because it would both identify specific issues in apply WCAG 2.0 to ICT (documents and software) and increase the likelihood that these applications of WCAG 2.0 will be consistent, and in keeping with the Principles, Guidelines, and Intent of WCAG 2.0. 22:14:12 and a NEW second paragraph 22:14:14 Please note that the introduction points out (in paragraphs 7 and 2) that " This document does not seek to determine which WCAG 2.0 provisions (principles, guidelines, or success criteria) should or should not apply to non-web ICT, but rather how they would apply, if applied." also that " Although this document covers a wide range of issues, it is not able to address all the needs of all people with disabilities. Because WCAG 2.0 was 22:14:15 developed for the Web, addressing accessibility for non-Web documents and software may involve provisions beyond those included in this document. Authors and developers are encouraged to seek relevant advice about current best practices to ensure that non-Web documents and software are accessible, as far as possible, to people with disabilities." 22:14:17 change the last paragraph to 22:14:18 If by "technologies and contexts never envisioned by WCAG 2.0’s authors" you are referring to PDF; PDF documents are web-content, and according to WCAG working group members PDF were always envisioned as being covered by WCAG 2.0 during its development -- and techniques have been documented for PDF. However the Access Board is now considering applying them beyond the web which is why additional review and guidance was needed - w[CUT] 22:14:18 what the WCAG2ICT was formed to provide. 22:14:45 AWK has joined #wai-wcag 22:15:36 RESOLUTION: Response accepted as amended 22:16:09 TOPIC: Comment LC-2652 22:16:15 -Judy 22:16:17 +Judy 22:16:32 q? 22:17:16 RESOLUTION: Response accepted as amended 22:17:42 TOPIC: Comment LC-2669 22:24:13 http://www.w3.org/TR/WCAG/#navigation-mechanisms 22:32:10 ACTION: Comment LC-2669 Loretta and Gregg to noodle out navigation mechanism 22:32:10 Error finding 'Comment'. You can review and register nicknames at . 22:33:46 ACTION: Gregg to noodle with Loretta and Andrew a navigation mechanism related to comment LC-2669 22:33:46 Created ACTION-192 - Noodle with Loretta and Andrew a navigation mechanism related to comment LC-2669 [on Gregg Vanderheiden - due 2013-02-07]. 22:33:49 -[Oracle] 22:34:50 -Katie_Haritos_Shea 22:35:00 -[Microsoft] 22:35:22 -Andrew_Kirkpatrick 22:35:27 -Judy 22:35:28 -Loretta_Guarino_Reid 22:35:28 -Michael_Cooper 22:35:29 -Robin_Tuttle 22:35:30 -David_MacDonald 22:35:32 -Gregg_Vanderheiden 22:35:34 WAI_WCAG()4:00PM has ended 22:35:34 Attendees were Gregg_Vanderheiden, Robin_Tuttle, Michael_Cooper, Katie_Haritos_Shea, Loretta_Guarino_Reid, Judy, Andrew_Kirkpatrick, David_MacDonald, James_Nurthen, Alex_Li 22:35:47 chair: Loretta_Guarino_Reid 22:35:54 scribeOptions: -final 22:35:56 rrsagent, make minutes 22:35:56 I have made the request to generate http://www.w3.org/2013/01/31-wai-wcag-minutes.html MichaelC