Non-unique ID on its own not a failure of 1.3.1

Name: Jason Kiss
Email: jason@accesscult.org
Affiliation: New Zealand Government
Document: TD
Item Number: F17
Part of Item: Applicability
Comment Type: technical
Summary of Issue: Non-unique ID on its own not a failure of 1.3.1
Comment (Including rationale for any proposed change):
While it is true that non-unique ID value is a failure of SC 4.1.1, and may very well introduce a failure of SC 1.3.1 where that ID value is referenced by another element in order to establish a relationship, it's not clear why two elements that have identical ID values but that otherwise aren't referenced by additional elements or in any one-to-one relationship.

Proposed Change:
Under Failure Example 1, change "An id attribute value that is not unique" to something like "An id attribute value that is not unique and that is referenced by another element to establish a relationship."

Under Procedure, change "1. Check for id and accesskey values which are not unique within the document." into two steps: "1. Check for id attribue values that are not unique within the document and that are referenced by other elements. 2. Check for accesskey values that are not unique within the document."

Received on Wednesday, 27 August 2014 03:15:07 UTC