| Title | Validity error: illegal tabindex attributes |
|---|---|
| Description | An 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.
|
| Creator | BenToWeb (Christophe.Strobbe@…) |
| Rights | Copyright BenToWeb 2005-2007 |
| Language | English |
| Date | 2005-10-05 |
| Status | accepted QA |
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)
Feature: table
(namespace: http://www.w3.org/1999/xhtml)
.
Technical specification: Strictly Conforming Documents .
This test case is intended to pass even though some attributes are illegal.
Three or more accessibility experts.
“Rules” refer to success criteria in WCAG 2.0, checkpoints in WCAG 1.0 and similar requirements.
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.
The page is not valid, but this does not necessarily cause accessibility problems.
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).
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.
The page is not valid, but this does not necessarily cause accessibility problems.
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).