| Title | Graphical components (object) don't have same text equivalents. |
|---|---|
| Description | Two documents, each containing a graphical link. |
| Creator | BenToWeb (johannes.koch@…) |
| Rights | Copyright BenToWeb 2005-2007 |
| Language | English |
| Date | 2005-08-25 |
| 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: img
(namespace: http://www.w3.org/1999/xhtml)
.
Technical specification: http://www.w3.org/TR/1999/REC-html401-19991224/struct/objects.html#edef-OBJECT.
The test is intended to fail because the object elements in both test files don't have the same text equivalent.
Check whether components that have the same functionality within the given set of Web Units are identified consistently.
Accessibility expert.
“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 7, column 153: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#consistent-behavior-consistent-functionality.
Graphical components don't have same text equivalent.
The object elements' text contents are not the same.
The test case fails the following success criterion at line 7, column 153: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#consistent-behavior-text-equivalents.
Graphical components don't have same text equivalent.
The object elements' text contents are not the same.