W3C home > Mailing lists > Public > public-wcag2ict-tf@w3.org > September 2012

two question per Action items 54 and 56

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Tue, 25 Sep 2012 23:27:37 -0500
To: "public-wcag2ict-tf@w3.org Force" <public-wcag2ict-tf@w3.org>
Message-id: <9B4739C0-2A51-4292-BCC1-4D2C65753C66@trace.wisc.edu>
Below is the text to be submitted to WCAG WG per the action items 54 and 56.  

These will be discussed/approved/modified on Friday's WCAG2ICT call and submitted to WCAG WG next week. 

Gregg



ACTION-54: Ask WCAG to add examples to WCAG INTENT for 2.2.1 Timing Adjustable, 2.2.2 Pause, Stop, Hide, and 2.2.3 No Timing per his comment on the survey


When looking at the definition of Real time event (which is used on 2.2.1 Timing Adjustable, 2.2.2 Pause, Stop, Hide, and 2.2.3 No Timing ) it is unclear what is included and not included as real time events.  Currently the definition includes examples of things that are.  But examples of things that are not would also be helpful.

 real-time event:

event that a) occurs at the same time as the viewing and b) is not completely generated by the content

Example 1: A Webcast of a live performance (occurs at the same time as the viewing and is not prerecorded).

Example 2: An on-line auction with people bidding (occurs at the same time as the viewing).

Example 3: Live humans interacting in a virtual world using avatars (is not completely generated by the content and occurs at the same time as the viewing).

It is requested that the following note be added to the INTENT section of  2.2.1 Timing Adjustable, 2.2.2 Pause, Stop, Hide, and 2.2.3 No Timing

"The following are examples of things that have time limits but are NOT real-time event -- and are therefore covered by this success criterion: 
        - a 1 person video game not linked to real world events
        - a virtual world with no other human controlled actors or ties to real world events



ACTION-56: Propose text to add to SC 3.3.4 WCAG INTENT to cover the concern about the verb "access" in the definition of "user-controllable"


When looking at the definition of user-controllable (which is used on 3.3.4 Error Prevention (Legal, Financial, Data )) it is unclear what the term "accessed" means.  Does this mean that this only applies to data that the user can delete? 

3.3.4 Error Prevention (Legal, Financial, Data): For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: (Level AA)
Reversible: Submissions are reversible.
Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

user-controllable
data that is intended to be accessed by users
Note: This does not refer to such things as Internet logs and search engine monitoring data.
Example: Name and address fields for a user's account.


Suggest that the following be added to the INTENT of SC 3.3.4

NOTE: The purpose of the phrase "user-controllable data" is to eliminate the need to notify the user each time invisible user-data such as tracking logs  are deleted.   The term "accessed" in the definition of  "user-controllable' is meant to refer to information that the user can access and see - but not necessarily information the user would be able to edit themselves.  For example, banking records showing the past months transactions would be an example of 'user-controllable' data that they can access and use.  If they did something to cause this to be deleted, then one of the three options should be true.  However if the bank is keeping track of which pages the person visits during a particular visit, and this information is never shown to the user, then that user information would not be information that the user "accessed" (it is invisible to the user) and it would therefore not be "user-controllable" data.   





Received on Wednesday, 26 September 2012 04:28:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 26 September 2012 04:28:09 GMT