RE: Example for SC 3.2.2

Hi Becky,

Thanks much for pulling this together

this is close -- but goes a bit beyond an example when it makes statements
about the success criterion and what conforms.  

Hmmmmm

How about a slight tweak so it is avoids statements like  "as long as". 


Example:  A form is provided for creating calendar entries in a web based
calendaring and scheduling application.  Along with the standard fields for
subject, time and location, there is a set of radio buttons to select the
type of calendar entry to create.  The calendar entry type can be meeting,
appointment or reminder.  If the user selects the radio for meeting,
additional fields are displayed on the page for entering the meeting
participants. Different fields appear if the reminder button is chosen.
Because only parts of the entry change and the overall structure remains the
same the basic context remains for the user.  


Does this work for you?  
 
Gregg

 -- ------------------------------ 
Gregg C Vanderheiden Ph.D. 
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 


-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf
Of Becky Gibson
Sent: Tuesday, January 03, 2006 1:30 PM
To: WCAG
Subject: Example for SC 3.2.2


At the December 22, 2005 teleconference I took an action item to create an
additional example for success criterion 3.2.2 [1]. 

Example:  A form is provided for creating calendar entries in a web based
calendaring and scheduling application.  Along with the standard fields for
subject, time and location, there is a set of radio buttons to select the
type of calendar entry to create.  The calendar entry type can be meeting,
appointment or reminder.  If the user selects the radio for meeting,
additional fields are displayed on the page for entering the meeting
participants.  If the user then selects, reminder, the fields for entering
participants are hidden since they are not needed to create a 
reminder entry.   Hiding and showing certain portions of the delivery unit 
is not a complete change on context since the intent of the form, to create
a calendar entry, does not change.  As long as the fields which get hidden
or displayed are fully accessible to all users, this type of behavior would
comply with success criterion 3.2.2. 

Issue #1661[2] can be closed is this example is accepted. 

[1] Becky to create example in How to Meet Document for 3.2.2 that explains
that hiding and showing content as the result of an input field change is
NOT a complete change of context (Calendaring and scheduling
example) [recorded in
http://www.w3.org/2005/12/22-wai-wcag-minutes.html#action07]
[2] http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1661

Becky Gibson
Web Accessibility Architect
                                                       
IBM Emerging Internet Technologies
5 Technology Park Drive
Westford, MA 01886
Voice: 978 399-6101; t/l 333-6101
Email: gibsonb@us.ibm.com

Received on Wednesday, 4 January 2006 05:28:00 UTC