- From: Chris Ridpath <chris.ridpath@utoronto.ca>
- Date: Mon, 11 Apr 2005 03:38:31 -0400
- To: "David MacDonald" <befree@magma.ca>, <w3c-wai-gl@w3.org>
- Message-ID: <00ae01c53e69$77478070$957ba8c0@traveler>
> Can we not create passing test files that > are WCAG compliant in other respects. > 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. There are several reasons that the "passing" test files are not designed to comply with the WCAG2: Right now, no one is sure what WCAG 2 compliant means so it's not possible to create test files that comply. The test files are designed to be independent of accessibility guidelines and can be used by several guidelines. So making them WCAG compliant may still not make them compliant with other guidelines. Which level of WCAG2? It may be impossible for many of the test files to be WCAG2 level 3 compliant. Cheers, Chris ----- Original Message ----- From: David MacDonald To: w3c-wai-gl@w3.org Sent: Thursday, April 07, 2005 11:14 AM Subject: [TECHS] Object tag test files. I was given the task to review tests that apply to the object tag. #75, 76, 77, 78¸ 79, 27, 128, 129, 183. I am in the middle of the assessments and will be finishing them before our call today. But there is something that I have to get clear on. In general I have a problem with tests that are designed to pass a certain accessibility principle but are inaccessible in other respects. I realize that there is a disclaimer above the test files saying that they may contain accessibility problems peripheral to the issue being tested, but I still have a problem with an inaccessible file getting a "passing" grade. I think it gives a confusing message to web designers. If the tests were only being looked at by machines it would not be as important to me, but when humans look at these tests I think it gives a mixed message. Can we not create passing test files that are WCAG compliant in other respects. If not I would dump inaccessible test files that are supposed to pass a certain WCAG criteria, unless they are not going to be looked at by humans. David MacDonald .access empowers people. .barriers disable them. www.eramp.com
Received on Monday, 11 April 2005 07:38:37 UTC