Test Case sc1.3.1_l1_057: h1 element used to identify a heading

Formal Metadata

Formal Metadata
Titleh1 element used to identify a heading
DescriptionDocument containing an h1 for structuring and not for formatting.
CreatorBenToWeb (evlach@…)
RightsCopyright BenToWeb 2005-2007
LanguageEnglish
Date2005-08-30
Statusaccepted QA

Technologies and Features

Technologies are markup languages or data formats. If the technology is a markup language, “features” refers to elements and attributes.

XHTML™ 1.0 The Extensible HyperText Markup Language (Second Edition)

XHTML™ 1.0 The Extensible HyperText Markup Language (Second Edition)

Feature: h1 (namespace: http://www.w3.org/1999/xhtml) .

Technical specification: The H1 element .

Feature: strong (namespace: http://www.w3.org/1999/xhtml) .

Technical specification: The strong element .

Test Data

Purpose

The test case is intended to pass as the h1 is used for structuring and not for formatting.

Expert Guidance

Check if every heading element is used for structuring and not for formatting.

Test Modes

Accessibility expert.

Test Files

Test file.

TCDL Data

sc1.3.1_l1_057 (XML).

Rules

“Rules” refer to success criteria in WCAG 2.0, checkpoints in WCAG 1.0 and similar requirements.

Primary Rules

The test case passes (line 9, column 1) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#content-structure-separation-programmatic.

The test case passes (line 10, column 12) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#content-structure-separation-programmatic.

Functional Outcome

Heading element identifies a heading.

Technical Comment

h1 element has correctly been used for structuring.

Secondary Rules

Secondary Rule (WCAG 2.0 - June 2005 Working Draft)

The test case passes (line 9, column 1) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#content-structure-separation-programmatic.

The test case passes (line 10, column 12) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#content-structure-separation-programmatic.

Functional Outcome

Heading element has correctly been used for structuring.

Technical Comment

h1 element has correctly been used for structuring.