Re: Techniques for 2.2

I can attempt #4..

Thanks..
Tim Boland NIST



At 08:08 PM 1/9/2006 -0500, you wrote:
>In the Team C teleconference today we winnowed down the list of techniques 
>for Guideline 2.2. Given that we only need to produce a minimum of one 
>sufficient technique for each success criterion, there are six techniques 
>we need to produce. Below are listed the first sufficient technique in 
>each of the success criterion. I would like to ask each member of the team 
>to volunteer to take one of them. Please reply to the list so we don't get 
>duplicates. If I don't get volunteers soon, I'll make assignments. :)
>
>1. 
><http://trace.wisc.edu/wcag_wiki/index.php?title=Providing_a_script_on_page_that_warns_the_user_and_allows_the_user_to_extend_time_or_turn_off_the_timeout&action=edit>Providing 
>a script on page that warns the user and allows the user to extend time or 
>turn off the timeout. (see 
><http://trace.wisc.edu/wcag_wiki/index.php?title=How_to_Meet_Success_Criterion_2.2.1>http://trace.wisc.edu/wcag_wiki/index.php?title=How_to_Meet_Success_Criterion_2.2.1) 
>
>2. 
><http://trace.wisc.edu/wcag_wiki/index.php?title=Ensuring_content_blinks_for_less_than_three_seconds&action=edit>Ensuring 
>content blinks for less than three seconds (see 
><http://trace.wisc.edu/wcag_wiki/index.php?title=How_to_Meet_Success_Criterion_2.2.2>http://trace.wisc.edu/wcag_wiki/index.php?title=How_to_Meet_Success_Criterion_2.2.2)
>3. 
><http://trace.wisc.edu/wcag_wiki/index.php?title=Allowing_the_content_to_be_paused_and_restarted_from_where_it_was_stopped&action=edit>Allowing 
>the content to be paused and restarted from where it was stopped. (see 
><http://trace.wisc.edu/wcag_wiki/index.php?title=Guide_to_2.2_L2_SC2>http://trace.wisc.edu/wcag_wiki/index.php?title=Guide_to_2.2_L2_SC2)
>4. 
><http://trace.wisc.edu/wcag_wiki/index.php?title=Designing_an_activity_so_that_timing_is_not_an_essential_part_of_the_activity&action=edit>Designing 
>an activity so that timing is not an essential part of the activity. (see 
><http://trace.wisc.edu/wcag_wiki/index.php?title=Guide_to_2.2_L3_SC1>http://trace.wisc.edu/wcag_wiki/index.php?title=Guide_to_2.2_L3_SC1)
>5. 
><http://trace.wisc.edu/wcag_wiki/index.php?title=Providing_a_mechanism_to_postpone_any_updating_of_content&action=edit>Providing 
>a mechanism to postpone any updating of content (See 
><http://trace.wisc.edu/wcag_wiki/index.php?title=Guide_to_2.2_L3_SC2>http://trace.wisc.edu/wcag_wiki/index.php?title=Guide_to_2.2_L3_SC2)
>6. 
><http://trace.wisc.edu/wcag_wiki/index.php?title=If_users_submit_data_when_the_user_is_no_longer_authenticated%2C_the_data_is_saved_and_the_data_is_reused_after_the_user_re-authenticates&action=edit>If 
>users submit data when the user is no longer authenticated, the data is 
>saved and the data is reused after the user re-authenticates. (see 
><http://trace.wisc.edu/wcag_wiki/index.php?title=Guide_to_2.2_L3_SC3>http://trace.wisc.edu/wcag_wiki/index.php?title=Guide_to_2.2_L3_SC3)
>
>Sorry for the formatting - using a Webmail client that's a pain.
>
>Michael