- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Tue, 20 Mar 2001 00:28:34 -0600
- To: "'Kynn Bartlett'" <kynn-edapta@idyllmtn.com>, <gv@trace.wisc.edu>
- Cc: "'GL - WAI Guidelines WG (E-mail)'" <w3c-wai-gl@w3.org>
KYNN WROTE >2) There are a series of documents which we call Technology Specific >Checkpoint Solutions >These documents use the Level 1 Guidelines as divisions >The level 2 items are checkpoints in the document Very good. We also need a series of documents which we call "Technology NON-Specific Checkpoint Solutions" or the like, right? For things which do not, strictly speaking, fall under any given technology? Or are we assuming we will include those on the TSCS? Such a document might be worth making anyway, even if it's not released, for internal use -- in other words, something that says to us making TSCS docs, "Here's what you need to include that are solutions, but which can be used with a number of technologies." Or we might be assuming that those will fit into the level 2 Checkpoint hierarchy? GREGG: YES - THAT IS ALREADY AT LEVEL 2 >3) Under each Checkpoint are a series of conditionals that read like >- If you use the IMG tag than you must do one of the following Is there more than one conditional per checkpoint? Gregg: THERE CAN BE -- YES >Under that conditional - you list all of the things that are acceptable >checkpoint solutions (which could be a set of things) for that checkpoint >and that condition. > - The second last item in the list is always: "Alternate >Equivalent Solution" ...... though if you use an equivalent method you must >document it on your website.) > - The last item is a statement that this element is not used. Such >as "IMG tag is not used" >For EACH conditional they MUST then do one of the items or item sets in the >list (which includes "EQUIVALENT" and "NOT USED") I like this. I think I proposed it last year. ;) (KYNN) GREGG: THEN IT MUST BE A GOOD IDEA
Received on Tuesday, 20 March 2001 01:29:12 UTC