- From: John M Slatin <john_slatin@austin.utexas.edu>
- Date: Wed, 28 Dec 2005 15:52:40 -0600
- To: "Tim Boland" <frederick.boland@nist.gov>, <w3c-wai-gl@w3.org>
Tim,
You asked whether there's a template for tests. I think the short answer
is no-- the idea is to include the test procedures in the "Tests"
section of the Techniques template.
But maybe there could be a "test template" in that section, to provide
the kind of guidance and consistency you're suggesting.
Could you draft something and send it to the list (or point us to an
existing template that you feel we could usefully adapt)?
Thanks!
John
"Good design is accessible design."
Dr. John M. Slatin, Director
Accessibility Institute
University of Texas at Austin
FAC 248C
1 University Station G9600
Austin, TX 78712
ph 512-495-4288, fax 512-495-4524
email jslatin@mail.utexas.edu
Web http://www.utexas.edu/research/accessibility
-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On
Behalf Of Tim Boland
Sent: Wednesday, December 28, 2005 3:24 PM
To: w3c-wai-gl@w3.org
Subject: Re: Instructions and team assignments for getting to Last Call
Will there be any consideration of a template for tests, in addition to
the
Techniques
template mentioned in the excerpted message following? Is a test
template
appropriate or necessary?
I think that possibly including such a test template, or at least some
additional specific instructions for test creators,
might serve to enhance the consistency of test format across the various
SCs, as well as simply
the process of test description and maintenance. Since tests are to
evaluate the implementation of
related techniques (which have a template), perhaps tests should also
have
a template?
Just a thought..
Thanks and happy new year!
Tim Boland NIST
At 03:05 PM 12/21/2005 -0600, you wrote:
>4. Draft new techniques and edit existing ones as required, using
>the Techniques template in the WIKI <http://tinyurl.com/dgcd7>. Refer
>to Tips for editing techniques <http://tinyurl.com/78v78> for detailed
>instructions.
>5. Include both pass and fail tests in the tests section of each
>technique. ("Pass" shows correct implementation of the technique;
>"Fail" shows incorrect implementation.) 6.
Received on Wednesday, 28 December 2005 21:52:51 UTC