W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > May 2006

WCAG 2.0 Comment Submission

From: WCAG 2.0 Comment Form <nobody@w3.org>
Date: Fri, 5 May 2006 15:10:43 +0000 (GMT)
To: public-comments-wcag20@w3.org
Message-Id: <20060505151043.069FA47BA1@mojo.w3.org>

Name: Alex Li
Email: alex.li@sap.com
Affiliation: SAP
Document: W2
Item Number: Conformance claims
Part of Item: 
Comment Type: GE
Comment (Including rationale for any proposed change):
This is related to user-entered or contributed content.  It was brought to discussion on May 4th WCAG con call already with no conclusion.

Due to the fact that you can violate WCAG with an ASCII smily face (1.1.1) or change of language without proper tag, or use of jargon, any user input can potentially violate WCAG.  If the user input resurface, even as input confirmation, the web unit would automatically fail WCAG.

All seach engines would fail because it cannot stop users from typing in an ASCII smily in the search box.  The subsequent search result screen of finding x number, even if it is 0, of hits with the smily would fail.  This is the same with foreign languages and jargon.

All websites containing logon screen would fail because user can type in a smily face into the user id box, whether such user id exist or not.  The system returns to confirm the id.  The web unit of the confirmation just failed WCAG.

All webmails would fail because incoming mails could come from a plain text mail client or contain inaccessible mail content of all sorts.  Webmail cannot alter the content of incoming email without violation of privacy, at the minimum.  No webmail can claim conformity.

All photosites would fail because user can always put in empty or inproper alt tag of photos that they submit.

All blogs would fail because user input is essential.

Product user reviews, such as those in Amazon or Cnet, would fail.

The list can go on and extend to all web applications.  As soon as a user agent accepts user input that are not restricted (anything other than dropdown list or radio button), they cannot conform.  In fact, comment area of WCAG 2.0 last call fails because you cannot stop me from typing in jargon, foreign language, or ascii art.  I\'m making this violation at the botton of the mail just to make a point.

Scoping out user-entered content is extremely difficult for many sites, especially when user-entered content is pervasive.  How would a blog, web mail, evite, business application scope out user-entered content?  Such information is essentially on every web unit.


wie Sie den Test führen können


Proposed Change:
Add a paragraph in the comformance area that user-contributed content is automatically scoped out.
Received on Friday, 5 May 2006 15:10:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:14:40 UTC