- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Thu, 7 Oct 2004 21:58:43 -0500
- To: "'Matt May'" <mcmay@w3.org>, <w3c-wai-au@w3.org>
I think you are absolutely correct. I also think that it will make WAI look like it has its act together. Also, if you get done early - we can use your help on evaluating and polishing WCAG. Gregg -- ------------------------------ Gregg C Vanderheiden Ph.D. Professor - Ind. Engr. & BioMed Engr. Director - Trace R & D Center University of Wisconsin-Madison -----Original Message----- From: w3c-wai-au-request@w3.org [mailto:w3c-wai-au-request@w3.org] On Behalf Of Matt May Sent: Thursday, October 07, 2004 6:26 PM To: w3c-wai-au@w3.org Subject: Proposal: reincorporate multiplexer into main doc Hi all, Jan and I have been discussing how to deal with the WCAG 1/2 ambiguity. At the last f2f, we had the idea of a multiplexer document that would be a second Recommendation, and would point to WCAG 1 for conformance until WCAG 2 came out, at which point it would be updated. We agreed that this is probably not really the best way to go about things, due to the complexity it would cause us and the readers of the spec. So I'd like to propose the following: 1) Bring the contents of this multiplexer document back into ATAG 2 proper; 2) Hold ATAG 2 at Proposed Recommendation status until WCAG 2 is at the same level; 3) Work on the WCAG 2 conformance requirements when it is complete; and 4) Release WCAG 2 and ATAG 2 simultaneously. The benefits of this approach are that we will only offer one target document, and no complicating directions coming from elsewhere; and that maintenance work on the document itself will be zero once it goes to Recommendation. Additionally, should WCAG 2 zig when we expected it to zag, we will be prepared to update our document to adequately reflect that. (However, should WCAG in fact XAG, then we have a whole different problem. Ha ha ha. Sorry, just a little WAI humor.) The drawback would be that we will then be tied to WCAG 2's development schedule. However, this is minor. Proposed Rec is usually a stable enough status that developers of authoring tools will be prepared to work toward it. Additionally, I believe that ATAG 2 would receive much more attention, and be better connected to WCAG 2 long term, if they are released and promoted together at Recommendation. This has been done with other specs, most recently RDF and OWL, with success. Thoughts? Concerns? - m
Received on Friday, 8 October 2004 02:58:44 UTC