Re: [TECHS] Object tag test files.

Jason suggested:
> I would expect each test file to be absolutely minimal, demonstrating
> just the single pertinent feature that is desired. In a markup
> language the test would be surrounded by just enough markup to be
> valid but would not contain any extraneous information. This, I am
> sure, is the approach taken here (I haven't checked out the test files).
>
Yes, this is the approach we've been taking.

In an earlier message Chris said:
> The test files are designed to highlight a single accessibility problem
> or its absence. They are not meant to be good examples of accessible
> documents. Those sorts of documents can be contained in the
> techniques documents or other places. The "passing" test files
> are just meant to show that the accessibility problem is not there.
>

Jason agreed and added:
> I agree this is the right way to design test files. I suggest that the
> above qualifications be captured clearly and prominently in the
> documentation accompanying the tests.
>

Here's the text we currently have for each test file:
"These test files contain examples of the accessibility problem detectable 
by this test. They may also contain more accessibility problems than the one 
described in this test. Please ignore any extraneous accessibility problems 
in these files."

Here's some suggested new text:
These test files contain examples of the accessibility problem detectable by 
this test. They are not meant to be good examples of accessible documents 
and may contain more accessibility problems than the one described in this 
test. Please ignore any extraneous accessibility problems in these files.

Can you suggest other text?

Cheers,
Chris

Received on Monday, 11 April 2005 11:17:59 UTC