Test Case sc4.1.1_l1_013: Validity error: illegal tabindex attributes

Formal Metadata

Formal Metadata
TitleValidity error: illegal tabindex attributes
DescriptionAn XHTML file that is well-formed but not valid: although the markup is structurally correct, some elements have a tabindex although they are not allowed to have that attribute. It cannot be predicted how assistive technology is supposed to respond to this. Possibly, the illegal tabindex values will become part of the tab sequence for all elements with tabindex.
CreatorBenToWeb (Christophe.Strobbe@…)
RightsCopyright BenToWeb 2005-2007
LanguageEnglish
Date2005-10-05
Statusvalidated

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: table (namespace: http://www.w3.org/1999/xhtml) .

Technical specification: Strictly Conforming Documents .

Test Data

Purpose

This test case is intended to pass even though some attributes are illegal.

Test Modes

Three or more accessibility experts.

Test Files

Test file.

TCDL Data

sc4.1.1_l1_013 (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 63, column 5) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#ensure-compat-parses.

The test case passes (line 114, column 19) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#ensure-compat-parses.

The test case passes (line 63, column 5) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#ensure-compat-parses.

The test case passes (line 114, column 19) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#ensure-compat-parses.

Functional Outcome

The page is not valid, but this does not necessarily cause accessibility problems.

Technical Comment

Depending on the browser, the user can tab to the welcome message (for example with Internet Explorer 6) or tab past it (for example with Mozilla 1.7.3).

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

Secondary Rules

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

The test case fails the following success criterion at line 63, column 5: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#ensure-compat-parses.

The test case fails the following success criterion at line 114, column 19: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#ensure-compat-parses.

The test case fails the following success criterion at line 63, column 5: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#ensure-compat-parses.

The test case fails the following success criterion at line 114, column 19: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#ensure-compat-parses.

Functional Outcome

The page is not valid, but this does not necessarily cause accessibility problems.

Technical Comment

Depending on the browser, the user can tab to the welcome message (for example with Internet Explorer 6) or tab past it (for example with Mozilla 1.7.3).

Online version: sc4.1.1_l1_013.

Secondary Rule (WCAG 2.0 - February 2005 Editor's Draft)

The test case fails the following success criterion at line 63, column 5: http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20050211/#4.1_use-spec-avoid-spec-no-exception.

The test case fails the following success criterion at line 114, column 19: http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20050211/#4.1_use-spec-avoid-spec-no-exception.

The test case fails the following success criterion at line 63, column 5: http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20050211/#4.1_use-spec-avoid-spec-no-exception.

The test case fails the following success criterion at line 114, column 19: http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20050211/#4.1_use-spec-avoid-spec-no-exception.

Functional Outcome

The page is not valid, but this does not necessarily cause accessibility problems.

Technical Comment

Depending on the browser, the user can tab to the welcome message (for example with Internet Explorer 6) or tab past it (for example with Mozilla 1.7.3).