Test Case sc1.3.1_l1_108: s element (strike) used for presentational purpose

Formal Metadata

Formal Metadata
Titles element (strike) used for presentational purpose
DescriptionPresentational element strike where its presentation characteristic is purely decorative and convey no meaning at all.
CreatorBenToWeb (evlach@…)
RightsCopyright BenToWeb 2005-2007
LanguageEnglish
Date2005-08-28
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: strike (namespace: http://www.w3.org/1999/xhtml) .

Technical specification: Font style elements .

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

Technical specification: Font style elements .

Test Data

Purpose

The test case is intended to pass as strike and s elements presentation characteristics are purely decorative and convey no meaning at all.

Expert Guidance

Check whether presentation tags has been used in order to convey information.

Test Modes

Three or more accessibility experts.

Test Files

Test file.

TCDL Data

sc1.3.1_l1_108 (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 11, column 106) the following success criterion: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#content-structure-separation-programmatic.

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

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

Functional Outcome

Presentation tag has been used only for presentation.

Technical Comment

This test case does not map to a WCAG 2.0 technique or failure.