See also: IRC log
CS: opportunity to look samples?
DO: no, probs with CVS access
CV: for eclipse you need only to locate private key home directory
EV: for eclipse see preferences>Team>CVS>SSH2 Connection method
<Christophe> http://www.w3.org/WAI/GL/WCAG20/tests/ctprocess.html
CS: discuss the test process for test samples
SAZ: need experience from previous task forces
and bentoweb
... what are the critical issues
... WCAG good example
CS: experience for bentoweb: test case
developers when these are done-> evaluation team for review process in
several stages-
... if change needed go back to developer otherwise go to second
reviewer-> accepted
... user testing : users review tests through html forms input
... automated testing: not done so far.. for colour contrast with tool for
instance
SAZ: for task force this mean evaluating technique?
CS: yes, other purpose between bentoweb and TF
SAZ: for this task force focus on test samples and not techniques
<Zakim> Michael_Cooper, you wanted to ask about meaning of "accepting" a test case in our context
MC: need to have some criteria how to accept
CR: the WCAG group would need to have a look at them
MC: problem would be dependency
CR: maybe couple of tests in WCAG need review to make sure are correct
SAZ: what we need to produce accepted test
samples ok by WCAG WG
... before formally accepted maybe both WCAg and ERT group have chance to
look and send any comments
MC: ok, set a timeline
... WCAG pooling to surveys to accept or reject and moves on
... this tf needs a procedure
SAZ: what the acceptance really means? accepted for the draft technique?
CS: technique might change and a test could be accepted
MC: aggree mapping with url is the approach we need
SAZ: clarify that test samples cannot be more
stable that techniques
... need specify procedures when ex a new test sample is uploaded
... write a proposal for criteria procedures (ex validate, check
metadata...)
CS: I could have a try
<scribe> ACTION: CS proposal for internal test case review process [recorded in http://www.w3.org/2006/10/31-tsdtf-minutes.html#action01]
SAZ: important to look procedure before looking actual test samples
SAZ: discuss the overall requirements and then
with chris help could do that
... one audience public: maybe download test samples
... other: us for see what we have what do we develop...
... somebody want to test an evaluation tool
MC: every way.. by technology/ by tech feature
CR: dont think find organisation of WCAG script not so helpful
SAZ: wcag widget select certain things like level, technologies and give a view technique (wcag quick reference)
<Christophe> WCAG 2.0 Quick Reference: http://www.w3.org/WAI/WCAG20/quickref/
http://www.w3.org/WAI/ER/tools/complete
SAZ: List of Web Accessibility Evaluation Tools : might look like this
<scribe> ACTION: SAZ and CR first prototype implementation and send to list [recorded in http://www.w3.org/2006/10/31-tsdtf-minutes.html#action02]