W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2013

Minutes WCAG 31 Jan 2013

From: Michael Cooper <cooper@w3.org>
Date: Fri, 01 Feb 2013 08:56:49 -0500
Message-ID: <510BC9A1.3050103@w3.org>
To: Loretta Guarino Reid <lorettaguarino@google.com>
CC: WCAG <w3c-wai-gl@w3.org>
Minutes of the 31 January 2013 WCAG meeting are posted to
http://www.w3.org/2013/01/31-wai-wcag-minutes.html and copied below.


  Web Content Accessibility Guidelines Working Group Teleconference


    31 Jan 2013

See also: IRC log <http://www.w3.org/2013/01/31-wai-wcag-irc>


    Attendees

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
Chair
    Loretta_Guarino_Reid
Scribe
    robin


    Contents

    * Topics <http://www.w3.org/2013/01/31-wai-wcag-minutes.html#agenda>
         1. Comment LC-2673
            <http://www.w3.org/2013/01/31-wai-wcag-minutes.html#item01>
         2. Comment LC-2663
            <http://www.w3.org/2013/01/31-wai-wcag-minutes.html#item02>
         3. Comment LC-2673
            <http://www.w3.org/2013/01/31-wai-wcag-minutes.html#item03>
         4. Comment LC-2652
            <http://www.w3.org/2013/01/31-wai-wcag-minutes.html#item04>
         5. Comment LC-2669
            <http://www.w3.org/2013/01/31-wai-wcag-minutes.html#item05>
    * Summary of Action Items
      <http://www.w3.org/2013/01/31-wai-wcag-minutes.html#ActionSummary>

------------------------------------------------------------------------

<trackbot> Date: 31 January 2013

<MichaelC> scribe: robin

<greggvanderheiden> https://sites.google.com/site/wcag2ict/


      Comment LC-2673

Comment LC-2673: tabled to later


      Comment LC-2663

<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*


      Comment LC-2673

<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*


      Comment LC-2652

*RESOLUTION: Response accepted as amended*


      Comment LC-2669

<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>.
<http://www.w3.org/WAI/GL/track/users%3E.>

<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].


    Summary of Action Items

*[NEW]* *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]
*[NEW]* *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]
 
[End of minutes]
------------------------------------------------------------------------
Minutes formatted by David Booth's scribe.perl
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/scribe/scribedoc.htm>
version 1.137 (CVS log <http://dev.w3.org/cvsweb/2002/scribe/>)
$Date: 2013-01-31 22:36:02 $


-- 

Michael Cooper
Web Accessibility Specialist
World Wide Web Consortium, Web Accessibility Initiative
E-mail cooper@w3.org <mailto:cooper@w3.org>
Information Page <http://www.w3.org/People/cooper/>
Received on Friday, 1 February 2013 13:57:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 1 February 2013 13:57:39 GMT