Issue 983: Example of ICS claim

* UAAG 1.0
UAAG has the notion of inclusion by reference or by direct inclusion. 
For example in the conformance section will be declared what has been 
supported.
 http://www.w3.org/TR/UAAG/conformance.html#include-reqs

Plus
[[[
A claim is well-formed if it meets the following two conditions.

Condition 1: The claim must include the following information:
 1.   The date of the claim.
 2.   A conformance profile.
 3.   Information about the user agent. The user agent may consist of 
more than one component. For each component, the claim must include the 
following:
 ◦   Name and version information for the component. Version 
information must be sufficient to identify the user agent (e.g., vendor 
name, version number, minor release number, required patches or 
updates, natural language of the user interface or documentation). The 
version information may refer to a range of user agents (e.g., "this 
claim refers to all user agents version 6.x").
 ◦  Name and version information for the operating environment (or 
environments) in which the component is running.
]]] - http://www.w3.org/TR/UAAG/conformance.html#well-formed-claim

The Conformance Profile is composed by many things including a list of 
things which does not comply.

[[[
ance profile includes the following assertions:
 1.   Required: The guidelines title/version: "User Agent Accessibility 
Guidelines 1.0"
 2.   Required: The URI of the guidelines: 
http://www.w3.org/TR/2002/REC-UAAG10-20021217
 3.   Required: The conformance level satisfied: "A", "Double-A", or 
"Triple-A"
 4.   Required: At least one content type label. The VisualText label 
must be present if the user agent renders text visually.
 5.   Required: The Selection label, if the user agent implements a 
selection mechanism.
 6.   Required: A list of requirements (checkpoints or portions of 
checkpoints) that do not apply. A conformance profile should also 
explain why those requirements do not apply.
 7.   Required: Information about one or more specifications (e.g., 
markup languages, style sheet languages, and APIs) implemented to 
satisfy the requirements of this document. A user agent must satisfy 
the requirements identified by the profile for at least these 
specifications. A user agent is not required to satisfy the identified 
requirements for other implemented specifications except when a content 
type label definition states otherwise. The profile must include enough 
information to identify the implemented specifications. The profile 
should indicate which specifications are used to satisfy which 
requirements (e.g., which image formats are used to satisfy the 
requirements associated with the Image content type label).
 8.   Optional: The Events label
 9.   Optional: Input modality labels: "Pointer" and/or "Voice"
]]] - http://www.w3.org/TR/UAAG/conformance.html#profile-structure


* ATAG 1.0
ATAG 1.0 requests to include the checkpoints which have not been met as 
leaving outside the ones which have been met. In a kind of declare what 
you don't do.
To know th

[[[
A well-formed claim must include the following information:
 1.   The guidelines title/version: "Authoring Tool Accessibility 
Guidelines 1.0";
 2.   The URI of the guidelines: 
http://www.w3.org/TR/2000/REC-ATAG10-20000203;
 3.   The conformance level satisfied: "A", "Double-A", or "Triple-A";
 4.   The version number and operating system of the software covered 
by the claim. Also indicate whether any upgrades or plug-ins are 
required;
 5.   The date of the claim;
 6.   The checkpoints of the chosen conformance level considered not 
applicable. Claimants should use the checklist [ATAG10-CHECKLIST] for 
this purpose.
]]] - http://www.w3.org/TR/ATAG10/#conformance



-- 
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager
*** Be Strict To Be Cool ***

Received on Monday, 21 March 2005 13:54:27 UTC