WCAG 2.0 Comment Submission

Name: Loretta Guarino Reid
Email: lguarino@adobe.com
Affiliation: Adobe Systems
Document: W2
Item Number: text-equiv-all
Part of Item: 
Comment Type: technical
Comment (Including rationale for any proposed change):
One of the clauses of 1.1.1 addresses General non-text content:

General Non-text Content: If non-text content presents information or responds to user input, then text alternatives serve the same purpose and present the same information as the non-text content. If text alternatives cannot serve the same purpose, then text alternatives at least identify the purpose of the non-text content.



It is hard to imagine how a text alternative can ever serve the same purpose as content that responds to user input, which makes this very confusing. It seems that the only way to satisfy this for content that responds to user input is to  provide a text alternative that identifies the purpose of the content, that is, a label. However,  labels are already required for user interface components in SC 4.1.2.

Proposed Change:
1. Define non-text content so that it is clear that content that responds to user input is not covered by this SC.

2. With this change, clarify the statement of SC 1.1.1 and the How to Meet document.

Received on Monday, 23 October 2006 19:14:17 UTC