- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Thu, 17 Nov 2005 09:39:00 -0600
- To: "'Tim Boland'" <frederick.boland@nist.gov>
- Cc: <w3c-wai-gl@w3.org>
- Message-ID: <002201c5eb8d$085e96e0$ee8cfea9@NC6000BAK>
The baseline is defined in the guideline itself. The other document is just a longer form of it with examples - a tutorial if you like. It doesn't (shouldn't) define it further than in the guidelines so it shouldn't be a problem. Will check this out with format people though to be sure. If you see a key part of the definition that isn't defined in the guidelines doc please let me know so we can include it. Tried to only put the definitive stuff in the guideline and leave explanations and background to the baseline doc. Thanks Gregg -- ------------------------------ Gregg C Vanderheiden Ph.D. Professor - Ind. Engr. & BioMed Engr. Director - Trace R & D Center University of Wisconsin-Madison _____ From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Tim Boland Sent: Thursday, November 17, 2005 9:27 AM To: Gregg Vanderheiden Cc: frederick.boland@nist.gov; w3c-wai-gl@w3.org Subject: Re: baseline_overview_draft.htm Would the inclusion of "baseline" as a component of WCAG2.0 conformance as detailed in the referenced document be consistent with (not violate) the following W3C QA SpecGL requirements (in particular QA SpecGL Requirements 8,9,10): (1) QA SpecGL Requirement 5: Define the terms used in the normative parts of the specification [1], (2) QA SpecGL Requirement 6: Create conformance labels for each part of the conformance model [2], (3) QA SpecGL Requirement 7: Use a consistent style for conformance requirements and explain how to distinguish them [3], (4) QA SpecGL Requirement 8: Indicate which conformance requirements are mandatory, which are recommended, and which are optional [4], (5) QA SpecGL Requirement 9: If the technology is subdivided, then indicate which subdivisions are mandatory for conformance [5], and (6) QA SpecGL Requirement 10: If the technology is subdivided, then address subdivision constraints [6]? Thanks and best wishes Tim Boland NIST PS - Thanks to the editors for working on this document! [1]: http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-principle [2]: http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conf-label-principle [3]: http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#consistent-style-princi ple [4]: http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#req-opt-conf-principle [5]: http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-mandatory-pri nciple [6]: http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdiv-constraints-prin ciple At 07:53 PM 11/16/2005 -0600, you wrote: xmlns:ns0="urn:schemas-microsoft-com:office:smarttags"> We have been working on a description of the baseline concept. Attached is what the editors have been able to develop on this. We can review it tomorrow. It would be good to release it with the next draft. Gregg ------------------------ Gregg C Vanderheiden Ph.D. Professor - Depts of Ind. Engr. & BioMed Engr. Director - Trace R & D Center University of Wisconsin-Madison < <http://trace.wisc.edu/> http://trace.wisc.edu/> FAX 608/262-8848 For a list of our list discussions http://trace.wisc.edu/lists/ <http://trace.wisc.edu:8080/mailman/listinfo/>
Received on Thursday, 17 November 2005 15:39:18 UTC