- From: Jan Richards <jan.richards@utoronto.ca>
- Date: Thu, 21 Apr 2005 12:07:27 -0400
- To: w3c-wai-au@w3.org, Wendy Chisholm <wendy@w3.org>
Tim: I should have mentioned in the message that I did discuss the "technology-specific WCAG benchmark" term with Wendy Chisholm from the WCAG-WG. Wendy didn't have a concern with the term, so that may be a good sign. Of course we should still take it to the full WCAG-WG for a broader opinion. Roberto: Can you be more specific about your concerns with the other 3 actions. I'm confused about Action 3 since it is closely related to Action 1 (that you agree with). All I did was do the replacement of the term "format" with "technology". Cheers, Jan Tim Boland wrote: > > Might want to coordinate with how WCAG is defining these terms (for > consistency's sake).. > WCAG is currently working on some definitions of terms.. > > Thanks and best wishes.. > Tim Boland NIST > > At 05:28 PM 4/21/2005 +0200, you wrote: > >> I suggest first solution, that is good. >> >> ----- Messaggio originale ----- >> Da: "Jan Richards"<jan.richards@utoronto.ca> >> Inviato: 21/04/05 17.11.15 >> A: "List (WAI-AUWG)"<w3c-wai-au@w3.org> >> Oggetto: Use of term "Format" and relationship with WCAG (related >> to Bugs #1196, #1116, #1197-checkpoint 2.1) >> >> On the April 18th call I took an action to address the following >> bug and >> just kept going from there: >> >> Bug1197: ...Guideline 2.1, "Support formats that enable the >> creation of >> Web content that conforms to WCAG": Even after considerable >> discussion, >> and following the link to the definition, we were not entirely clear >> what is meant by "format" here. For instance, we were wondering >> whether >> it was related to markup languages, or to doc type schemas, or >> something >> else. Please clarify here and then reinforce that in the glossary.... >> >> Proposed actions: >> >> [Action: 1] Replace "format" with the WCAG 2.0 term "technology" >> which >> is defined as: >> >> technology >> A technology is a: >> - markup or programming language >> - application Programming Interface (API) >> - or communication protocol >> >> --- >> >> [Action 2:] Introduce a new term, "technology-specific WCAG >> benchmark", >> to refer to the document that ATAG 2.0 requires evaluators to >> specify in >> the conformance profile. (Note: We used to call this a WCAG >> Techniques >> document, but techniques documents are non-normative. The nature >> of the >> document is actually closer to that of a WCAG conformance claim, >> except >> that the "benchmark" document covers a range of potential outputs >> from >> an authoring tool rather than some particular Web content as a WCAG >> conformance claim does. >> >> The term would then be defined in its own sub-section of the >> conformance >> section. The definition would hit these key points: >> >> 1) a benchmark document must specify the version of WCAG used. >> >> 2) a benchmark document can specify one or more technologies used >> together (e.g. plain HTML or HTML + CSS or SVG + PNG images, etc.) >> >> 3) the benchmark document becomes *normative* for a particular >> evaluation by the act of the evaluator including a reference to the >> benchmark URI in the ATAG 2.0 conformance profile. >> >> 4) the benchmark document can be created by any person or >> organization >> (although the AUWG does suggest checking to see if a benchmark >> document >> has already been published by W3C or another technology developer, >> before creating a new one). >> >> 5) the benchmark document specifies a target WCAG conformance level >> >> >> [Messaggio troncato. Toccare Modifica->Segna per il download per >> recuperare la restante parte.] > > > -- Jan Richards, M.Sc. User Interface Design Specialist Adaptive Technology Resource Centre (ATRC), University of Toronto Email: jan.richards@utoronto.ca Web: http://jan.atrc.utoronto.ca Phone: 416-946-7060 Fax: 416-971-2896
Received on Thursday, 21 April 2005 16:08:03 UTC