W3C

DRAFT DOCUMENT

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.

HTML Test Suite for WCAG 2.0
Test 37 - The header following an h1 is h1 or h2.

W3C Editor's Draft 2005-08-11

Editors:
Chris Ridpath, ATRC, University Of Toronto
Jenae Andershonis, Microsoft Inc.

Abstract

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.


Status Of This Test

As part of the conformance test process, this test has a status of 'pending'.


WCAG2 Guideline

Guideline: 1.3 - Ensure that information, functionality, and structure can be separated from presentation.
Success Criteria: 1. Navigational features can be programmatically identified .

Level 1

The WCAG2 has 3 priority levels for making Web content accessible. This test has a priority of 'Level 1'.


Techniques

The WCAG Working Group has created techniques that describe how Web content may be made accessible. The following techniques are related to this test:


Prerequisite Tests

There are no prerequisite tests for this test.


Test Process

Procedure

  1. For each h1 element, find the header element that follows it.

Expected Results

  1. The header following an h1 is h1 or h2.

Fail Instructions

  1. Rearrange the header order so h1 or h2 elements follow h1 elements.

Pass Instructions

Any accessibility check may be performed after this test.


Test Files

These test files contain examples of the accessibility problem detectable by this test. They may also contain more accessibility problems than the one described in this test. Please ignore any extraneous accessibility problems in these files.

Valid XHTML 1.0!