See also: IRC log
<scribe> scribe: ben
<rscano> hi all! sorry but this evening i can stay only in IRC
(from normative survey) 403, 1772, 1290
(from team C survey) 1383, 1622, 1643, 1645, 1827, 1828, 1883, 1885, 1888, 1890, 1886, 1887, 1889, Providing a text message when the user provides information that is not in list of allowed values
(from 2.4.5 techniques survey) Identifying the purpose of a link using the link context, Providing link text for anchor elements that describes the purpose of a link, Identifying the purpose of a link using link text and text associated with the parent element of the link
(from 2.4 issues survey) 1563, 1741, 1812, 1832, 1710, 955, 1715, 1770, 1720
(from misc. items survey) 1819, 1360, 1839, 810, 1752, 1875, 1696, 1721, 1766, 1845, 1848, 1854
Issue 1728: Scoping
resolution: Accept proposed revisions to scoping section with edits change "inaccessible" to "non-conforming" and replace "process unit" with "if the Web unit is part of a process"
resolution: Move 1.3.4 to Level 1 and close this issue.
resolution: accept proposed definition as, "stopped by user request and not restarted until requested by user"
resolution: do not revise the success criterion, and close issue 1768 with, "invalidating the activity better captures the intent and, according to working group memebers, translates better".
resolution: Close issue 1826 with, "There is not enough experience in applying the techniques with different types of servers and services to move this to level 2 at this time and the group could identify cases involving financial transaction where no one has been able to figure out how to do this without violating regulations regarding storing confidential information on a server after a transaction is completed or terminated."
resolution: Close issue 1653 with, "Audio-only content would not meet the requirements of WCAG under several SC. While WCAG describes accessibility features of audio, audio cannot be used alone without alternatives and be accessible to all users. The guidelines do not forbid using audio feedback about errors. Feedback about errors may be provided in audio, as long as the audio is also associated with text as per guideline 1.1."
resolution: Close issue 1884 with, "This was discussed determined to be a baseline issue - if script in baseline it should be fine. Either client-side or server-side validation is sufficient (depending on baseline). Note for security this is crucial but that's beyond our scope. Techniques for both client-side and server-side validation are suggested in the general techniques for this SC."
resolution: accept How to Meet Success Criterion 2.4.5 as proposed, but rename technique titled, "Identifying the purpose of a link using the link context" to "Identifying the purpose of a link using link text combined with link context"
resolution: Accept General Technique: Providing link text that describes the purpose of a link with edits.
resolution: Remove Plain Text Technique: Identifying the purpose of a link using text in the enclosing sentence (not an accessibility issue)
resolution: Close 1830 by removing technique titled, "structure content so main content preceeds repeated material" and add it to the comments section of the wiki.
<scribe> ACTION: Michael and David to work on failure technique titled, "Failure due to specifying foreground colors without specifying background colors or vice versa." [recorded in http://www.w3.org/2006/03/23-wai-wcag-irc]
resolution: Close 1835 with, "Discussed at the 26 January 2006 Teleconference : This would appear to require authors to know what operating system features would be for users (on different operating systems). We do not know how to write techniques for something like this. Guideline 1.3 ensures that content can be separated from presentation. This enables the operating system to present the information in an alternative manner, for example using high contrast.
... has been assigned
<scribe> ACTION: John to write a rationale for closing this item [recorded in http://www.w3.org/2006/03/23-wai-wcag-irc]
resolution: close 1798 with a combination of Yvette, John and Michael's comments.
resolution: close as proposed plus Michael's comments
resolution: Close issue 1446 as proposed, with revised note from Gregg's comments.
<scribe> ACTION: team B to add something to intent that suggests using multiple forms to address the needs of different groups [recorded in http://www.w3.org/2006/03/23-wai-wcag-irc]
resolution: Accept proposed revisions to level descriptions as proposed, revise second item under level 3 to read, "Can not neccessarily be applied to all Web resources." and revise first note to read, "Because not all level 3 success criteria can be used with all types of content, Triple-A conformance only requires conformance to a portion of level 3 success criteria."
<Sorcha> sorcha moore rejoinging
resolution: revise this paragraph to read, "All WCAG 2.0 success criteria are testable. While some can be tested by computer programs, others must be tested by qualified human testers. Sometimes, a combination of computer programs and qualified human testers may be used. When people who understand WCAG 2.0 test the same content using the same success criteria, the same results should be obtained with high inter-rater reliability."
... close Issue 1358 with, "We revised this section to read, "All WCAG 2.0 success criteria are testable. While some can be tested by computer programs, others must be tested by qualified human testers. Sometimes, a combination of computer programs and qualified human testers may be used. When people who understand WCAG 2.0 test the same content using the same success criteria, the same results should be obtained with high inter-rater reliability." "
<scribe> ACTION: Bruce and John to update conformance examples and version numbers and update them appropriately [recorded in http://www.w3.org/2006/03/23-wai-wcag-irc]
resolution: add a new success criterion (2.3.2) at level 3 that reads, "Web units do not contain any compontents that flash more than 3 times in any one second period."
resolution: accept proposed revisions (below) to 1.2 subject to confirmation from participants in good standing
1.2.1 Captions are provided for prerecorded multimedia.
1.2.2 Audio descriptions of video or a full corrected text screenplay including any interaction are provided for prerecorded multimedia.
definition of "full corrected text screenplay including any interaction" as, "a document describing all visual context, action of the actors, dialog, sounds etc that are typically included in screenplays presented in a multimedia presentation that includes a means for achieving any outcomes that are acheived using interaction during the mulitmedia"
NOTE: A screenplay used to create the multimedia content would meet this definition only if it was corrected to accurately represent the final multimedia as it occurred and after editing etc.
1.2.3 Audio descriptions of video are provided for prerecorded multimedia.
resolution: advance WCAG 2.0 guidelines document (as ammended by today's decisions) as a last call working draft.