This is a W3C Working Draft produced by the Web Content Accessibility Guidelines Working Group (WCAG WG). It describes requirements for Checklists and Techniques described by the Web Content Accessibility Guidelines 2.0 (WCAG 2.0). These requirements are related to but different from Requirements for WCAG 2.0 in that "Requirements for WCAG 2.0 Checklists, Techniques, and Test Files" specifies requirements for the technology-specific documents produced by the WCAG WG while "Requirements for WCAG 2.0" specifies general requirements for the general usability of documents produced by the WCAG WG. The Working Group encourages feedback about these requirements as well as participation in the development of WCAG 2.0 by people who have experience creating Web content that conforms to Web Content Accessibility Guidelines 1.0.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.
Send comments about this document to the Web Content Accessibility Guidelines Working Group mailing list. The archives for this list are publicly available.
This document was produced under the 5 February 2004 W3C Patent Policy. The Working Group maintains a public list of patent disclosures relevant to this document; that page also includes instructions for disclosing [and excluding] a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) with respect to this specification should disclose the information in accordance with section 6 of the W3C Patent Policy.
This document has been produced as part of the W3C Web Accessibility Initiative (WAI). The goals of the WCAG WG are discussed in the Working Group charter. The WCAG WG is part of the WAI Technical Activity.
This document describes requirements for creating Checklists and Techniques for the Web Content Accessibility Guidelines 2.0. It is a draft document that does not fully represent the consensus of the group at this time. Consensus is expected to be achieved shortly and work on creating the Techniques documents to proceed.
This is a draft document and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR/.
The Web Content Accessibility Guidelines 2.0 creates a technology-independent set of Web accessibility guidelines by providing a set of high-level guidelines, and providing technology-specific information in auxiliary documents that are more frequently updated and may be non-normative. This document sets forth requirements for providing those documents, as summarized in Priorities and Techniques. Specifically, this set of requirements fulfills WCAG 2.0 Requirements to provide technology-specific Checklists and technology-specific Application Information.
While the WCAG Working Group intends to provide techniques for a variety of technologies, there is not a mandate to provide techniques for all technologies. W3C policy prohibits work on proprietary technologies, and it is not expected that the working group will have resources to provide techniques for every other technology in use on the Web. Additionally, while there will be an effort to provide comprehensive overviews of available techniques for which the WCAG Working Group does provide techniques, there is no guarantee that every possible means of satisfying the Success Criteria will be inventoried. Therefore, the techniques must be viewed only as example techniques which clarify the guidelines and describe common ways to conform to WCAG 2.0. It is possible to conform to the guidelines without following the techniques provided by the WCAG Working Group. Nevertheless, these techniques should represent the best available knowledge and serve as solid guidance for most implementors.
This document describes requirements both for the source files used to store techniques and for the documents that will be generated from the source files. The source files will likely only be viewed for editing purposes and will exist in the best format and organization that fulfills the requirements (i.e., they are not likely to be available in HTML for general use). From these sources files we intend to generate a variety of views (see Appendix 1 Output Formats ). Each view may have its own requirements. The three views currently under discussion are comprehensive Techniques ( 2. Techniques Requirements ), Checklists ( 3. Checklist Requirements ), and Test Files ( Test Cases ).
Other W3C groups have expressed interest in using the schema that is developed. Developers of non-W3C technologies may use the schema to publish their own techniques documents that show how to use their technologies to conform to WCAG 2.0. Therefore, while the Techniques documents are specifically created to meet WCAG 2.0 requirements, the structure is intended to be generalizable to other working groups and technologies.
[Definition: Machine Testable: There is a known algorithm (regardless of whether that algorithm is known to be implemented in tools) that will determine, with complete reliability, whether the technique has been implemented or not. Probabilistic algorithms are not sufficient.]
[Definition: Reliably Human Testable: The technique can be tested by human inspection and it is believed that at least 80% of knowledgeable human evaluators would agree on the conclusion. Tests done by people who understand the guidelines should get the same results testing the same content for the same success criteria. The use of probabilistic machine algorithms may facilitate the human testing process but this does not make it machine testable.]
[Definition: Not Reliably Testable: The technique is subject to human inspection but it is not believed that at least 80% of knowledgeable human evaluators would agree on the conclusion.]
[Definition: Testable Statement: An assertion of the proper application of a technique that can be evaluated as either passed or failed.]
[Definition: Test File: A discrete unit representing by specific example a pass or fail condition of a testable statement.]
[Definition: Positive Test: A test file that demonstrates the proper application of a technique. If a technique's requirement is to avoid a certain practice, a postive test case may represent the absence of a feature.]
[Definition: Negative Test: A test file that demonstrates improper application of a technique. If a technique's requirement is to avoid a certain practice, a negative test case may represent the presence of the feature to be avoided.]
[Definition: Sufficient: A technique or set of techniques that fulfill the requirements of a Success Criterion without additional requirements.]
[Definition: Optional: A technique that is not necessary to fulfill requirements of a Success Criterion, but may nevertheless have value to implement.]
[Definition: Not Recommended: A technique whose implementation has a negative impact on the requirements of a Success Criterion and should not be followed.]
Techniques must be usable by a variety of audiences. Audiences that have been identified include
User agent developers
Evaluation tool developers
Authoring tool developers
Assistive technology developers
Training material developers
Operating System developers
Source files must be structured in such a way that multiple views can be achieved. A list of specific views is provided in Appendix 1 Output Formats . Some views may be targeted to specific audiences and other views may be appropriate for multiple audiences.
Techniques must be highly structured and largely machine manipulable. It is expected that they will exist in XML files conforming to the DTD/Schema in Appendix 2 Techniques Schema .
Techniques documents must be versioned in such a way that updates to the documents do not break interdependencies that may exist among multiple documents (e.g., on Core techniques, HTML dependent on CSS, etc.). Versioning can be based on revision dates of specific documents.
Each technique must be assigned a unique identifier to enable machine-readable conformance statements.
Structure should be general enough that it can be used by groups outside the WAI domain.
It must be possible for Techniques documents to be localized.
It must be possible to provide techniques that are applicable to specific locales, but are not relevant in other locales.
Each technique must map to a specific WCAG 2.0 Success Criterion by URI and number for clarity and to enable auto generation of hybrid Guidelines/Techniques documents.
There may be multiple techniques for each Success Criterion, clearly stated that they are alternate techniques. Such techniques have an OR relationship with each other.
Each technique must state whether its implementation fully conforms to the Success Criterion, and if not, provide references to other techniques (in the same or other Techniques documents) needed to achieve full conformance. Such techniques have an AND relationship with each other.
A set of techniques whose implementation fulfills a Success Criterion is considered "Sufficient" for the Success Criterion.
Techniques may be "Optional". Implementation of an optional technique does not fulfill the requirements of a Success Criterion but has an identifiable benefit with respect to the intent of the Success Criterion.
Techniques must provide information about baselines for which they are intended.
For a given baseline, a technique may be sufficient (possibly when in combination with other techniques), optional, or not recommended. Optional and not recommended techniques are documented if they are considered sufficient in a different baseline.
Techniques should be grouped by particular technologies to which they apply (e.g., HTML, CSS, SVG, ECMAScript).
Each technique must clearly indicate what is required to conform to the Success Criterion to which it applies.
There should be a separate group of techniques that are not related to a specific technology, to describe accessibility practices at a level of detail not appropriate for the guidelines but common to multiple technologies. Requirements for these techniques are detailed below in General Techniques .
Where technologies work together (e.g., HTML and CSS), relevant joint techniques must be presented with the host technology (e.g., HTML). If techniques do not involve interactions between the two technologies, they must be presented with their respective technology only.
NOTE: There is not consensus about whether it should be permissable to create techniques for technologies that cannot meet the minimum Success Criteria of the guidelines even in combination with other technologies.
Techniques must state to which versions of the technology they apply, i.e., describe a practice to avoid or follow. They may specify all versions, all versions prior to or later than a particular version, or enumerate particular versions.
For a given technology, it is not necessary to provide techniques for every Success Criterion if the criterion is not applicable to the technology, either because the technology is designed to be used with another technology (e.g., CSS with HTML) or because it is not possible to achieve full guideline conformance with the technology. In place of a technique there must be an indication that states whether the technology is intended to interact with other technologies to provide full guideline conformance, or whether it is not possible in that technology to achieve guideline conformance for that Success Criterion. In the latter case, outputs must prominently state that full guideline conformance is not possible with the technology.
NOTE: There is serious debate about whether it should be possible to create views which contain Checklist items related specifically to technologies that do not themselves fully support the guidelines. For example, it may be possible to create a Checklist devoted solely to CSS, but it is never possible to achieve full guideline conformance with CSS. It may be desirable to require that views for such technologies always include other technologies, such as HTML, that can result in complete guideline conformance when following the guidance of that view. It is expected that the process of developing techniques and views will help clarify and close this issue.
Techniques may describe practices that are not yet supported by user agents, authoring tools, etc. in order to provide guidance for tool developers. When possible techniques should also describe practices that work in contemporary tools.
NOTE: This is related to baseline and needs to be adjusted when that is completed.
For techniques in which current user agent support is known to be variable or otherwise relevant to the technique, information about this issue should be provided. Additional user agent information may be provided in external resources.
Each technique must indicate the conditions under which it is applicable. Applicability conditions refer to the presence or absence of certain features relevant to the technique.
The General Techniques must offer concrete strategies that can be implemented in a wide variety of technologies to satisfy specific success criteria.
Each technique should provide at least one clear example. Examples, though sometimes of necessity implemented in a particular technology, do not specifically indicate proper use of that technology, but show a general concept.
The General Techniques must be clearly written and have a reading level at or below 9th grade level (Flesch Reading Ease score 55 or higher).
The General Techniques must serve the same diverse audiences as the Guidelines.
Each General Technique must provide links to relevant technology-specific techniques.
The General Techniques document(s) must stand in clear relation to other documents in the WCAG 2.0 collection.
The following points are mandatory requirements for Techniques.
Positive test cases must be provided for testable Techniques. Negative test cases should be provided when possible.
Techniques should include descriptions, commentary, implementation notes, links to resources or training materials, etc. to contain information not part of the structured data.
The following points are mandatory requirements for Checklists.
Technology-specific Checklists must include technology-specific checklist items that address every Success Criterion in the guidelines. Checklist items for success criteria that include an "or" statement should have all related provisions included in one technology-specific checklist item.
NOTE: Normally, a Checklist will include content drawn from techniques for multiple technologies described as in Scope of Documents . Each Success Criterion would be met by techniques drawn from one or more of the technologies but not necessarily all. For example, a Checklist describing HTML and CSS may indicate that some Success Criteria are met by HTML and others by CSS.
Each Success Criterion addressed in a Checklist must include a list of Checklist items that are both necessary and sufficient to meet that Success Criterion. If there are multiple interchangeable techniques which could be used to achieve a Success Criterion, they must be listed all together in a single Checklist item as an "OR" proposition.
Checklists must be constructed such that all items in the checklist for a given success criterion must be marked true in order for the content to be declared conformant at any conformance level.
If there are no techniques for a particular technology that address a specific success criterion, then a checklist item for that success criterion must be present and must include information stating that the content must also be provided in another form that meets all of Level 1 requirements.
NOTE: This item relates to baseline so should be clarified appropriately.
Checklist items are grouped according to the Success Criterion to which they apply and are ordered by their conformance level. Optional techniques should be presented in an "additional strategies" section and listed separately.
NOTE: We need to figure out what to do with Optional Techniques. This is a bit of a holdover and needs to be updated.
The following points are mandatory requirements for Test Cases.
At least one test case should be provided for every technology-specific technique. Multiple test cases may be provided for a technique.
Metadata must exist about each test case detailing the following:
A testable statement that describes the issue to examine and can be answered as true or false.
Prerequisite tests that must be executed before the current test.
NOTE: Need more explanation here.
Instructions for evaluator when test case passes.
Instructions for evaluator when test case fails.
Link to technique(s) the test case supports.
There must be at least two test files for every testable statement, one to test the pass condition and one to test the fail condition.
Test files should be granular, depending as little as possible on resources outside themselves.
Test files must be consistent with the examples in the techniques documents, i.e., test files should look like more complete examples of the brief examples already provided.
The Techniques are designed to meet a number of needs. As documents are designed to work together, each view may be drawn from multiple source files. The number of possible output formats is therefore large and many views may be generated from the source files at request time.
The following output formats have been identified and it must be possible to generate each of these documents.
NOTE: This list is not yet complete. While it does not have to be for us to proceed with the work, the more complete it is the more likely we will be to not miss anything. Also, it is not clear whether this should be an Appendix (in which case it may be ok to view it as a growing list) or part of the requirements, in which case it probably does need to be considered complete at the time the requirements are ratified.
List Techniques by Success Criterion to which they apply
Specify the Techniques as true/false statement
Implementation of the Techniques in the Checklist must be sufficient to provide complete implementation of the Success Criterion.
Unabridged Techniques documents
Small files that provide single positive or negative examples of each Technique.
Contribute to test suites for Evaluation and Repair tools, Authoring tools, and User Agents.
A manifest file that provides machine-readable metadata about the techniques covered by each test file and whether it is a positive or negative test case.
Techniques by conformance level
Techniques by technology version
Techniques by implementation status
The DTD for techniques is available at http://www.w3.org/WAI/GL/WCAG20/sources/xmlspec-tech.dtd.