See also: IRC log
<ben> scribe: becka11y
Announcement: Michael Cooper has joined W3C WAI and will take over as WCAG team contact when Wendy leaves.
<Christophe> Link: http://www.w3.org/WAI/ER/2006/tests/tests-tf
Resolution: Approve the Work statement for the joint Test Samples Development Task Force
<ben> Work Statement: http://www.w3.org/WAI/EO/2006/wcag2eowg_tf
Resolution: Approve the WCAG 2.0 Materials Support Task Force Work Statement
Contact Shawn Henry if you are interested in participating in the WCAG 2.0 Materials Support Task Force.
The approach is to have EO folks write the documents based on their understanding of WCAG 2.0 and have the documents reviewed by WCAG 2.0 working group members for accuracy.
<ben> Unanimous Consent Items:
<ben> Team C 22 June: LC-795, LC-763
<ben> Team A 22 June: LC-593, LC-653, LC-671, LC-766, LC-776, LC-821
<ben> Team B 22 June: LC-702
<ben> Editors 22 June: LC-481, LC-489, LC-495, LC-500, LC-519, LC-525, LC-555, LC-577, LC-578, LC-604, LC-611, LC-681, LC-686, LC-697, LC-744, LC-801, LC-803
Resoluton: Accept items ( see Unanimous Consent Items: posted by Ben) where all survey participants agreed with the proposal.
Resolution: Put issue LC-558 on hold for possible addtional public comments.
Resolution: Adopt Resolution for LC-600 with ammended comment: "Thus, it is important not to rely on CSS to visually position content in a specific sequence if this sequence results in a meaning that is different from the programmatically determined reading order."
Resolution: Update first sentence of resolution to replace "addition" to "use": "This success criterion does not prevent the use of programmatic information which can be used by AT or the user agent to identify and provide error information." Accept the resolution in principle. Action for Christophe to make this information clear in the How to Meet document. Issue stays open until action item is complete.
<scribe> ACTION: Christophe update How To Meet for 2.5.1 to explain the use of programmitic information to provide error text. [recorded in http://www.w3.org/2006/06/22-wai-wcag-irc]
Resolution for Issue LC-630: Group agrees in principle with the response to not update the SC text. Update response text "suggestions for error correct" with "suggetions for error correction", Leave open and assign to Loretta to work out final language for HTM doc.
Resolution: Put issue 631 on hold in the "AT push" category. Assign action to Loretta to address this issue.
Resolution: Put issue 632 on hold in the "AT push" category. Assign action to Loretta to address this issue.
<scribe> ACTION: Loretta to work on Issues 630, 631, and 632. [recorded in http://www.w3.org/2006/06/22-wai-wcag-irc]
Resolution: Do not accept the proposed resolution for LC-587. Action item to Gregg, Bruce, Becky to see if it can be made clearer that 1.3.1
Updated Resolution: Do not accept the proposed resolution for LC-587. Action item to Gregg, Bruce, Becky to see if it can be made clearer that 1.3.1 addresses labelling form elements.
<scribe> ACTION: Gregg, Bruce, Becky to address issue 587 and see if it can be made clearer that 1.3.1 addresses labelling form elements. [recorded in http://www.w3.org/2006/06/22-wai-wcag-irc]
Resolution: Accept proposal for issue LC 534 as edited.
Resolution: Accept issue 587 as proposed but put on hold for overall luminosity review.
Resolution: accept proposal for issue 598 with edits suggested by Bruce.
Resolution: Put issue 614 on hold in category of "level descriptions" so we can look at all the level related issues together.
Resolution: Accept issue 617 as propsed with an action item to implement Christophe's suggestion implemented: "Can we change that bullet in Appendix D from "if style sheets are in your baseline, WCAG 1.0 checkpoint 6.1 is not required;" to "if style sheets are in your baseline, WCAG 1.0 checkpoint 6.1 is not required, but the meaning of the content must not depend on CSS positioning (SC 1.3.3);" in order to avoid confusion in the future?"
Resolution: Issue 637 is referred back to team A.
Resolution: Issue 663 is referred back to team A to review comments from survey.
Issue 718 remains open - we will pick up here next week.