W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2003

Re: [TECH] Requirements for Techniques v0.3

From: Jason White <jasonw@ariel.ucs.unimelb.edu.au>
Date: Tue, 7 Jan 2003 08:07:00 +1100
Message-ID: <15897.61428.923914.280920@jdc.local>
To: Lisa Seeman <lisa@UBaccess.com>
Cc: w3c-wai-gl@w3.org

Lisa Seeman writes:
 > 
 > Thanks for explaing it to me Jason. There is a need for testable techniques,
 > but may I recommend that:
 > a, test cases etc be available only in a specific rendering of the
 > techniques (so we do not confuse everybody) - as you suggested
 > and

I think that is what was intended. The requirements document sets out
what is to be included; a separate section will be provided to
identify the requirements of each of the intended views.

 > b, techniques that are not testable be included anyway.
 > It seems a bit daft to exclude useful techniques because they do not fit
 > with the needs of authoring tools and evaluation and repair tools etc.

My original suggestion on this point was that the testability status
of every technique be explicitly identified in the XML source from
which the checklists and other documents are generated, indicating
whether the technique is machine testable, human testable or not
testable at all. There has been no intention to exclude non-testable
techniques as such. Also, by providing such markup it becomes possible
to filter the techniques on the basis of testability, which may be
desirable for certain purposes.

It should also be noted that many content authors want testable
techniques to be provided wherever possible, without which they can't
reliably determine whether their content meets the pertinent
requirement. Thus, offering testable techniques where possible and
clear guidance where not, is the underlying strategy to be followed,
in the techniques as well as in the guidelines proper.
Received on Monday, 6 January 2003 16:07:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:21 GMT