Techniques for WCAG 2.0

Skip to Content (Press Enter)


F17: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine one-to-one relationships (e.g., between labels with same id) in HTML

Important Information about Techniques

See Understanding Techniques for WCAG Success Criteria for important information about the usage of these informative techniques and how they relate to the normative WCAG 2.0 success criteria. The Applicability section explains the scope of the technique, and the presence of techniques for a specific technology does not imply that the technology can be used in all situations to create content that meets WCAG 2.0.


Applies to the Document Object Model (DOM) for HTML and XHTML

This failure relates to:


The objective of this technique is to ensure that Web pages can be interpreted consistently by user agents, including assistive technology. If it is ambiguous, different user agents including assistive technologies could present different information to their users. Users of assistive technology for example may have different information presented to them than users of other mainstream user agents. Some elements and attributes in markup languages are required to have unique values, and if this requirement is not honored, the result can be irregular or not uniquely resolvable content. For example, when id attribute values are not unique, they are particularly problematic when referenced by labels, headers in data tables, or used as fragment identifiers, as user agents do not have enough information to determine essential relationships (i.e., to determine which label goes with which item).


Failure Example 1

  • A label element whose for attribute value is an idref that points to a non-existent id

  • An id attribute value that is not unique.

  • An accesskey attribute value that is not unique


No resources available for this technique.

(none currently listed)



  1. Check for id and accesskey values which are not unique within the document.

  2. Check that attribute values that have an idref value have a corresponding id value.

  3. For tables that use the axis attribute, check that all values listed in the axis attribute have a corresponding id value in a table header cell in the same table.

  4. For client-side image maps, check that the value of the usemap attribute is a URI that references a valid name or id.

Expected Results