Test Case sc1.3.1_l1_136: Presentational elements in order to convey information and/or relationships.

Formal Metadata

Formal Metadata
TitlePresentational elements in order to convey information and/or relationships.
Description Document using semantic markup used incorrectly. Abbreviation description should appear in title attribute.
CreatorBenToWeb (evlach@…)
RightsCopyright BenToWeb 2004-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: span (namespace: http://www.w3.org/1999/xhtml) .

Technical specification: Grouping elements: the DIV and SPAN elements .

Test Data

Purpose

The test case is intended to fail as the semantic markup is used incorrectly.

Expert Guidance

Check whether semantic markup has been used correctly.

Test Modes

Three or more accessibility experts.

Test Files

Test file.

TCDL Data

sc1.3.1_l1_136 (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 11, column 4: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#content-structure-separation-programmatic.

Functional Outcome

Semantic markup has been used incorrectly.

Technical Comment

Abbreviation description should appear in title attribute.

Secondary Rules

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

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

Functional Outcome

Semantic markup has been used incorrectly.

Technical Comment

Abbreviation description should appear in title attribute.

Online version: sc1.3.1_l1_136.

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