RE: Use of term “Format” and relationship with WCAG (related to Bugs #1196, #1116, #1197-checkpoint 2.1)

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.]

Received on Thursday, 21 April 2005 15:29:52 UTC