Test Case sc1.3.1_l1_064: h5 element used for formatting

Formal Metadata

Formal Metadata
Titleh5 element used for formatting
DescriptionDocument containing a heading element h5 for formatting and not for structuring.
CreatorBenToWeb (evlach@…)
RightsCopyright BenToWeb 2004-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: h5 (namespace: http://www.w3.org/1999/xhtml) .

Technical specification: The H5 element .

Test Data

Purpose

The test case is intended to fail because the heading element h5 is used for formatting and not for structuring.

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_064 (XML).

Rules

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

Primary Rules

The test case fails the following success criterion at line 9, column 16: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#content-structure-separation-programmatic.

Functional Outcome

The abuse of the heading for formatting disorients users who depend on headings for navigation and orientation.

Technical Comment

The test case maps to failure F43: Failure of SC 1.3.1 due to using structural markup in a way that does not represent relationships in the content.

Secondary Rules

Secondary Rule (WCAG 2.0 - April 2006 Working Draft (Last Call))

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

Functional Outcome

The abuse of the heading for formatting disorients users who depend on headings for navigation and orientation.

Technical Comment

Online version: sc1.3.1_l1_064.

Secondary Rule (WCAG 2.0 - June 2005 Working Draft)

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

Functional Outcome

The abuse of the heading for formatting disorients users who depend on headings for navigation and orientation.