See also: IRC log
<trackbot> Date: 31 January 2013
<MichaelC> scribe: robin
<greggvanderheiden> https://sites.google.com/site/wcag2ict/
Comment LC-2673: tabled to later
<AWK> Alex is going to join, unless he can get Cherie to do so
<Loretta> 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.
<greggvanderheiden> 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]
<greggvanderheiden> 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."
RESOLUTION: Accepted as amended
<Zakim> Judy, you wanted to ask a clarification about what the "this" is and to
<AWK> 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)
<Loretta> Jud, I'm ont sure what document you are reviewing.
<Loretta> My error - I was looking at the wrong issue number.
<greggvanderheiden> 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.
<greggvanderheiden> 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.
<greggvanderheiden> change the last sentence of the first paragraph
<greggvanderheiden> 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.
<greggvanderheiden> 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.
<greggvanderheiden> 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.
<greggvanderheiden> 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.
<greggvanderheiden> 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]
<greggvanderheiden> 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."
<greggvanderheiden> 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
<greggvanderheiden> 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."
<greggvanderheiden> ================== [WCAG WG] Comments ==============
<greggvanderheiden> change the last sentence of the first paragraph
<greggvanderheiden> 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.
<greggvanderheiden> and a NEW second paragraph
<greggvanderheiden> 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
<greggvanderheiden> 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."
<greggvanderheiden> change the last paragraph to
<greggvanderheiden> 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]
<greggvanderheiden> what the WCAG2ICT was formed to provide.
RESOLUTION: Response accepted as amended
RESOLUTION: Response accepted as amended
<Loretta> http://www.w3.org/TR/WCAG/#navigation-mechanisms
<scribe> ACTION: Comment LC-2669 Loretta and Gregg to noodle out navigation mechanism [recorded in http://www.w3.org/2013/01/31-wai-wcag-minutes.html#action01]
<trackbot> Error finding 'Comment'. You can review and register nicknames at <http://www.w3.org/WAI/GL/track/users>.
<scribe> ACTION: Gregg to noodle with Loretta and Andrew a navigation mechanism related to comment LC-2669 [recorded in http://www.w3.org/2013/01/31-wai-wcag-minutes.html#action02]
<trackbot> Created ACTION-192 - Noodle with Loretta and Andrew a navigation mechanism related to comment LC-2669 [on Gregg Vanderheiden - due 2013-02-07].
This is scribe.perl Revision: 1.137 of Date: 2012/09/20 20:19:01 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found embedded ScribeOptions: -final *** RESTARTING DUE TO EMBEDDED OPTIONS *** Found Scribe: robin Inferring ScribeNick: robin Default Present: Gregg_Vanderheiden, Robin_Tuttle, Michael_Cooper, Katie_Haritos_Shea, Loretta_Guarino_Reid, Judy, Andrew_Kirkpatrick, David_MacDonald, James_Nurthen, Alex_Li Present: Gregg_Vanderheiden Robin_Tuttle Michael_Cooper Katie_Haritos_Shea Loretta_Guarino_Reid Judy Andrew_Kirkpatrick David_MacDonald James_Nurthen Alex_Li Regrets: Kerstin_Probiesch Gian_Wild Kathy_Wahlbin Found Date: 31 Jan 2013 Guessing minutes URL: http://www.w3.org/2013/01/31-wai-wcag-minutes.html People with action items: comment gregg lc-2669 loretta WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]