Minutes WCAG 3 February 2011

Minutes of the 3 February 2011 WCAG meeting are posted to
http://www.w3.org/2011/02/03-wai-wcag-minutes.html and copied below.


  Web Content Accessibility Guidelines Working Group Teleconference


    03 Feb 2011

Agenda <http://lists.w3.org/Archives/Public/w3c-wai-gl/2011JanMar/0015.html>

See also: IRC log <http://www.w3.org/2011/02/03-wai-wcag-irc>


    Attendees

Present
    Mary_Utt, Andrew_Kirkpatrick, Bruce_Bailey, Loretta_Guarino_Reid,
    Michael_Cooper, Wolf_Schmidt, Marc_Johlic, Tim_Boland,
    +1.617.584.aaaa, Gregg_Vanderheiden
Regrets
    Adam_Solomon, Daman_Wandke, James_Nurthen
Chair
    Loretta_Guarino_Reid
Scribe
    marcjohlic


    Contents

    * Topics <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#agenda>
         1. Issue LC-2454: WCAG 2 conformance claim: validating code
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item01>
         2. Issue LC-2429: SC 3.2.1 Keyboard users only?
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item02>
         3. Issue LC-2462: Understanding WCAG 2- SC 1.3.1
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item03>
         4. Issue LC-2463: WCAG 2 techniques for SC 1.3.2 and 2.4.3
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item04>
         5. Issue LC-2461: Understanding WCAG 2- SC 2.4.3
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item05>
         6. Issue LC-2455: Note at end of sufficient techniques for
            3.3.2 is ambiguous
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item06>
         7. Issue LC-2453: techniques link to 20081211 version
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item07>
         8. Issue LC-2431: G93: SC 1.2.4
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item08>
         9. Issue LC-2430: G97: Only "immediately following the expanded
            form"?
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item09>
        10. Issue LC-2428: G150: procedure and policy
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item10>
        11. Issue LC-2432: SM7: Expected Results
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item11>
        12. Issue LC-2444: Test does not check top position of link or
            mechanism
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item12>
        13. Issue LC-2446: Equivalence of content of noembed element not
            explicitly checked
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item13>
        14. Issue LC-2436: Formatting Convention
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item14>
        15. Issue LC-2426: Table of Content needs summary of collections
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item15>
        16. Issue LC-2440: last line of test redundant
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item16>
        17. Issue LC-2458: Wording of G164
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item17>
        18. Issue LC-2435: FLASH34 Using screen reader detection to turn
            off sounds that play automatically
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item18>
        19. Issue LC-2434: FLASH17 wrong success criteria association
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item19>
        20. Sufficient PDF Technique for SC 1.3.2, 2.1.1, 2.1.3, 2.4.3:
            Ensuring correct tab and reading order in PDF documents
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item20>
        21. Sufficient PDF Technique for SC 1.3.1, 2.4.8, 3.2.3:
            Specifying consistent page numbering for PDF documents in
            Adobe Acrobat Pro or Reader
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item21>
        22. Add link to Related Techniques for G91: Providing link text
            that describes the purpose of a link
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item22>
        23. Add example to G130: Providing descriptive headings
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item23>
        24. Sufficient Silverlight Technique for SC 2.4.7: Designing a
            Focused Visual State for Custom Silverlight Controls
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item24>
        25. Sufficient Silverlight Technique for SC 1.1.1, 3.3.2:
            Displaying HelpText in Silverlight User Interfaces
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item25>
        26. Sufficient Silverlight Technique for SC 2.1.1: Providing
            Keyboard Shortcuts for a Silverlight Application as a Whole
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item26>
        27. Sufficient Silverlight Technique for SC 4.1.2: Using
            Silverlight Text Elements for Appropriate Accessibility Role
            <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#item27>
    * Summary of Action Items
      <http://www.w3.org/2011/02/03-wai-wcag-minutes.html#ActionSummary>

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

<trackbot> Date: 03 February 2011

<Loretta> regrets from Adam, Daman, James

<scribe> scribe: marcjohlic

<MichaelC> scribe: marcjohlic


      Issue LC-2454: WCAG 2 conformance claim: validating code

*RESOLUTION: Accepted as amended*


      Issue LC-2429: SC 3.2.1 Keyboard users only?

*RESOLUTION: Accepted as amended*


      Issue LC-2462: Understanding WCAG 2- SC 1.3.1

<Loretta> There may also be cases where it may be a judgment call about
what information should appear in text and what would need to be
directly associated, and it may be most appropriate to duplicate some
information (for instance, in an HTML table, providing the summary both
in the paragraph before the table and in the summary attribute of the
table itself). However, wherever possible it is necessary for the
information to be programmatically determined rather tha

*RESOLUTION: Accepted as proposed*


      Issue LC-2463: WCAG 2 techniques for SC 1.3.2 and 2.4.3

*RESOLUTION: Accepted as amended*


      Issue LC-2461: Understanding WCAG 2- SC 2.4.3

<Loretta> RESPONSE: We have removed the first example. We do not believe
that Example 5 fails 2.4.3, since the tab order still follows the
reading order, and the reading order follows a logical order.

*RESOLUTION: Accepted as amended*


      Issue LC-2455: Note at end of sufficient techniques for 3.3.2 is
      ambiguous

*RESOLUTION: Accepted as amended*


      Issue LC-2453: techniques link to 20081211 version

*RESOLUTION: Accepted as amended*


      Issue LC-2431: G93: SC 1.2.4

*RESOLUTION: Accepted as proposed*


      Issue LC-2430: G97: Only "immediately following the expanded form"?

<Loretta>
http://www.w3.org/TR/2010/NOTE-UNDERSTANDING-WCAG20-20101014/meaning-located.html

*RESOLUTION: Accepted as amended*


      Issue LC-2428: G150: procedure and policy

<Loretta> Sample some real-time content and check whether the procedure
is being applied.

*RESOLUTION: Accepted as amended*


      Issue LC-2432: SM7: Expected Results

*RESOLUTION: Accepted as proposed*

<MichaelC> 2432

<MichaelC> 2444

<MichaelC> 2446

<MichaelC> 2436

<MichaelC> 2426

<MichaelC> 2440

<MichaelC> 2458

<MichaelC> 2435

<MichaelC> 2434


      Issue LC-2444: Test does not check top position of link or mechanism

*RESOLUTION: Accepted as proposed*


      Issue LC-2446: Equivalence of content of noembed element not
      explicitly checked

*RESOLUTION: Accepted as proposed*


      Issue LC-2436: Formatting Convention

*RESOLUTION: Accepted as proposed*


      Issue LC-2426: Table of Content needs summary of collections

*RESOLUTION: Accepted as proposed*


      Issue LC-2440: last line of test redundant

*RESOLUTION: Accepted as proposed*


      Issue LC-2458: Wording of G164

*RESOLUTION: Accepted as proposed*


      Issue LC-2435: FLASH34 Using screen reader detection to turn off
      sounds that play automatically

*RESOLUTION: Accepted as proposed*


      Issue LC-2434: FLASH17 wrong success criteria association

*RESOLUTION: Accepted as proposed*


      Sufficient PDF Technique for SC 1.3.2, 2.1.1, 2.1.3, 2.4.3:
      Ensuring correct tab and reading order in PDF documents

*RESOLUTION: Accepted as amended*


      Sufficient PDF Technique for SC 1.3.1, 2.4.8, 3.2.3: Specifying
      consistent page numbering for PDF documents in Adobe Acrobat Pro
      or Reader

<scribe> *ACTION:* AWK [recorded in
http://www.w3.org/2011/02/03-wai-wcag-minutes.html#action01]

<trackbot> Sorry, bad ACTION syntax

<scribe> *ACTION:* AWK confirm that screen reader can actually read the
displayed page number [recorded in
http://www.w3.org/2011/02/03-wai-wcag-minutes.html#action02]

<trackbot> Created ACTION-120 - Confirm that screen reader can actually
read the displayed page number [on Andrew Kirkpatrick - due 2011-02-10].

*RESOLUTION: Accepted as proposed providing that Andrew can confirm that
screen reader can actually read the displayed page number*


      Add link to Related Techniques for G91: Providing link text that
      describes the purpose of a link

*RESOLUTION: Accepted as proposed*


      Add example to G130: Providing descriptive headings

*RESOLUTION: Accepted as proposed*


      Sufficient Silverlight Technique for SC 2.4.7: Designing a Focused
      Visual State for Custom Silverlight Controls

*RESOLUTION: Accepted as amended*


      Sufficient Silverlight Technique for SC 1.1.1, 3.3.2: Displaying
      HelpText in Silverlight User Interfaces

*RESOLUTION: Accepted as amended*


      Sufficient Silverlight Technique for SC 2.1.1: Providing Keyboard
      Shortcuts for a Silverlight Application as a Whole

<scribe> *ACTION:* Wolf review the wording of test procedure [recorded
in http://www.w3.org/2011/02/03-wai-wcag-minutes.html#action03]

<trackbot> Created ACTION-121 - Review the wording of test procedure [on
Wolf Schmidt - due 2011-02-10].

*RESOLUTION: Leave open*


      Sufficient Silverlight Technique for SC 4.1.2: Using Silverlight
      Text Elements for Appropriate Accessibility Role

*RESOLUTION: Accepted as proposed*

<MichaelC> trackbot, end meeting


    Summary of Action Items

*[NEW]* *ACTION:* AWK [recorded in
http://www.w3.org/2011/02/03-wai-wcag-minutes.html#action01]
*[NEW]* *ACTION:* AWK confirm that screen reader can actually read the
displayed page number [recorded in
http://www.w3.org/2011/02/03-wai-wcag-minutes.html#action02]
*[NEW]* *ACTION:* Wolf review the wording of test procedure [recorded in
http://www.w3.org/2011/02/03-wai-wcag-minutes.html#action03]
 
[End of minutes]
------------------------------------------------------------------------
Minutes formatted by David Booth's scribe.perl
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/scribe/scribedoc.htm>
version 1.135 (CVS log <http://dev.w3.org/cvsweb/2002/scribe/>)
$Date: 2011/02/03 23:06:49 $


-- 

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 Saturday, 5 February 2011 12:48:36 UTC