This is a draft document supplied by the WCAG Techniques Task Force. It in no way represents a WCAG Working Group consensus or agreement and is provided for informational and discussion purposes only. The accessibility test listed below should not be construed as required for conformance with the proposed WCAG2.
styleto convey list depth.
Copyright 2005, ATRC, University Of Toronto, All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.
This test case was created by the ATRC at the University Of Toronto. It should not be construed as required for conformance with the proposed WCAG2.
The complete list of tests may be found at http://www.w3.org/WAI/GL/WCAG20/tests/
Comments on this test may be made to the WCAG mailing list.
As part of the conformance test process, this test has a status of 'pending'.
Guideline: 2.4 - Provide mechanisms to help users find content, orient themselves within it, and navigate through it.
Success Criteria: 1. Structures within the content can be programmatically determined . How to ensure that structures and relationships in content can be programmatically determined . (Informative) The concepts of "reliable" and "standard" need to be incorporated into the definition of "programmatically determined."
The WCAG2 has 3 priority levels for making Web content accessible. This test has a priority of 'Level 2'.
The WCAG Working Group has created techniques that describe how Web content may be made accessible. The following techniques are related to this test:
There are no prerequisite tests for this test.
Any accessibility check may be performed after this test.