Fluid Engage - Ideal accessible interaction for code entry

[E.J. Zufelt]

On 2010-02-23, at 12:38 PM, Colin Clark wrote:

> Everett,
>
> On 2010-02-23, at 11:43 AM, E.J. Zufelt wrote:
>
>> Good morning,
>>
>>> Filed as: ENGAGE-440
>>
>> Just took a look at the issue, it does mention notification, but  
>> does not mention allowing user to adjust / pause timing of auto- 
>> redirect as is necessary in previously cited WCAG 2.0 A criteria.
>
> I'm so glad you brought this particular issue up. It's one I've been  
> keen to see us address for the final 0.3 release, since there are a  
> number of places throughout the application where we have animations  
> or transitions that a user needs to be able to control. These will  
> make for fascinating and exciting design solutions, I think.
>
> Colin
>
* There are three things that come to mind.  First is that I was  
unaware of the animations / transitions (so yes let's work on that for  
the final release).  For the Code Entry in particular one issue is the  
redirect without a "let's go now" interaction and the other is the  
timing between successful entry of an object code and the redirect.   
All three issues are dealt with in the following 3 WCAG 2.0  
checkpoints, all priority A I believe.

2.2.1 Timing Adjustable: For each time limit that is set by the  
content, at least one of the following is true: Turn off: The user is  
allowed to turn off the time limit before encountering it; or Adjust:  
The user is allowed to adjust the time limit before encountering it  
over a wide range that is at least ten times the length of the default  
setting;or Extend: The user is warned before time expires and given at  
least 20 seconds to extend the time limit with a simple action (for  
example, "press the space bar"), and the user is allowed to extend the  
time limit at least ten times...

2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling, or auto- 
updating information, all of the following are true: Moving, blinking,  
scrolling: For any moving, blinking or scrolling information that (1)  
starts automatically, (2) lasts more than five seconds, and (3)
is presented in parallel with other content, there is a mechanism for  
the user to pause, stop, or hide it unless the movement, blinking, or  
scrolling is part of an activity where it is essential; and Auto- 
updating: For any auto-updating information that (1) starts  
automatically and (2) is presented in parallel with other content,  
there is a mechanism for the user to pause, stop, or hide it or to  
control the frequency of the update unless the auto-updating is part  
of an activity where it is essential.

3.2.2 On Input: Changing the setting of any user interface component  
does not automatically cause a change of context