See also: IRC log
<MichaelC> agendum 1 = Simplification Survey (part 1) for 26 April 2007 <http://www.w3.org/2002/09/wbs/35422/20070426simplify/results>
<MichaelC> scribe: Christophe_Strobbe
<MichaelC> scribeNick: Christophe
URL: http://www.w3.org/2002/09/wbs/35422/20070426simplify/results
<Zakim> Christophe, you wanted to say that their are editorial conventions to indidate that "must" is according to RFC 2119
Resolution: accepted as amended ("needs to" changed back to "must")
Resolution: accepted as amended: change GL 1.1 to "Provide text alternatives for any non-text content so that it can be changed into other forms people need such as large print, braille, speech, symbols, pictures or simpler language."
Resolution: keep the oringinal wording of GL 1.2 text
Resolution: change GL 1.3 text to: " Create content that can be presented in different ways (for example spoken aloud, simpler layout, etc.) without losing information or structure"
<Zakim> Christophe, you wanted to say that the concepts of foreground and background are not difficult enough to replace them with the harder syntax proposed here
Resolution: change GL 1.4 text to: "Make it easier for people with disabilities to see and hear content, including separating foreground from background"
Resolution: change text of GL 2.1 to "Make all functionality available from a keyboard"
Resolution: change GL 2.2 text to: "Provide users with disabilities enough time to read and use content"
Resolution: change GL 2.3 text to: "Do not create content that is known to cause seizures."
Resolution: change GL 2.4 text to: " Provide ways to help users with disabilities navigate, find content and determine where they are."
Resolution: as proposed: "Make Web pages appear and operate in predictable ways."
Resolution: change GL 3.3 text: "Help users avoid and correct mistakes."
Resolution: change GL 4.1 text to: "Maximize compatibility with current and future user agents, including assistive technologies"
Resolution: change note to: "This success criterion is primarily for Web authors who develop or script their own user interface controls. For example, standard HTML controls already meet this provision when used according to specification."
Resolution: change SC 1.4.5 to: "Audio content that contains speech in the foreground does not contain background sounds, background sounds can be turned off, or ..."
Resolution: definition of CAPTCHA accepted as amended.
Resolution: accept definition of "name" as amended by Cynthia's proposal
Resolution: accepted as proposed.
Resolution: Move SC 1.3.2 to SC 1.4.1 (no change in wording)
Resolution: accept definition of abbreviation as amended
Resolution: definition of assistive technology accepted as amended.
Resolution: accepted as amended.
Resolution: accept definition of "full text alternative for multimedia including any interaction" as amended.
Resolution: accept proposal to revise example 1 in definition of "process"
Resolution: accept revision of examples in definition of "programmatically determined" as amended ("using ...")
Resolution: accept definition of "programmatically determined link context" as amended.
<scribe> ACTION: Loretta to add item to survey regarding headings and programmatically determined link text [recorded in http://www.w3.org/2007/04/26-wai-wcag-irc]
Resolution: accepted as proposed.
Resolution: accept definition of "real-time event"
Resolution: accept example for definition of "text alternative" as amended.
Resolution: accept change of "renders" to "presents" in definition of "user agent" and "viewport"
Resolution: accept revised example 1 in definition of "Web page"
Resolution: accept LC-721 as proposed (unanimous)
Resolution: accepted as amended
Resolution: send LC-1028 and LC-1029 back for tuning.
Resolution: accept LC-1158 as emended
Resolution: accept LC-1206: Principles under which some SC fall
... change LC-1158 to "partial accept"
Resolution: accept How to Meet Success Criterion 1.4.3 as amended
Resolution: accept How to Meet Success Criterion 1.4.6 as amended
Resolution: accept as amended: sufficient technique for 1.4.3: Using a technology that has commonly-available user agents that support zoom
Resolution: accept as amended: sufficient technique for 1.4.3 and 1.4.6: Using percent for font sizes
Resolution: accept as amended: sufficient technique for 1.4.3 and 1.4.6: Using named font sizes
Resolution: accept as amended: sufficient technique for 1.4.3 and 1.4.6: Using em units for font sizes
<scribe> ACTION: Loretta to move this to the next survey [recorded in http://www.w3.org/2007/04/26-wai-wcag-irc]
Resolution: accept as amended: Failure of 1.4.3 and 1.4.6 when resizing visually rendered text up to 200 per cent causes the text to be clipped, truncated or obscured
<scribe> ACTION: Cynthia to add an example to Failure technique: Failure of 1.4.3 and 1.4.6 when resizing visually rendered text up to 200 per cent causes the text to be clipped, truncated or obscured [recorded in http://www.w3.org/2007/04/26-wai-wcag-irc]
Resolution: accepted proposed change to 3.3.4. Note: this does not require every field to have a label or instruction.
<scribe> ACTION: Loretta to examine limiting scope of the new SC 1.4.1 (not color alone) [recorded in http://www.w3.org/2007/04/26-wai-wcag-irc]
Resolution: leave LC-1080 (Link underlines) open
Resolution: Accept 582, 590, 644, 664, 689, 884, 1010, 1330, 735, 754 , 843, 651, 658, 1007, 1312, 1370, 857(with editorial change) as proposed