WCAG Team C

630 and 632

http://www.w3.org/WAI/GL/WCAG20/issue-tracking/viewdata_individual.php?id=630

http://www.w3.org/WAI/GL/WCAG20/issue-tracking/viewdata_individual.php?id=632

We had indicated techniques to create bu not what the techniques were

http://trace.wisc.edu/wcag_wiki/index.php?title=How_to_Meet_Success_Criterion_2.5.2

http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20070220/Overview.html#minimize-error-suggestions

<scribe> ACTION: Michael to document ARIA techniques for required fields for 630 and 632 [recorded in http://www.w3.org/WAI/GL/2007/03/19-wcag-teamc-minutes.html#action01]

<scribe> ACTION: Michael to document ARIA techniques for allowable field values for 630 and 632 (range is only ARIA constraint known possible) [recorded in http://www.w3.org/WAI/GL/2007/03/19-wcag-teamc-minutes.html#action02]

1078

http://www.w3.org/WAI/GL/WCAG20/issue-tracking/viewdata_individual.php?id=1078

Technique for 2.5.1 "Creating a mechanism that allows users to jump to errors"

http://trace.wisc.edu/wcag_wiki/index.php?title=Creating_a_mechanism_that_allows_users_to_jump_to_errors

david will take further edits to next week

<scribe> scribeNick: MichaelC

<scribe> scribe: Michael_Cooper