Fluid Engage - Ideal accessible interaction for code entry

[E.J. Zufelt]

On 2010-02-23, at 9:15 AM, Justin Obara wrote:

> Hello Everett,
>
> On 2010-02-22, at 11:57 AM, E.J. Zufelt wrote:
>
>> 2. Having not tested the keypad, I will when buttons are labeled, I  
>> wonder how similar the experience is to dialing a phone number on  
>> the iPhone for a VO / Zoom user.
>
> The number pad should be announcing the buttons properly now, as a  
> fix went in yesterday for this issue.
>
* The numberpad is announcing buttons now.

1. Go to the Code Entry page (Voiceover announces the buttons and they  
are configured in the standard telephone keypad orientation).

2. Entered the number 5.

3. Explored the entire screen with VO, no changes, there was no text  
field showing what I had already entered.

3. Entered the number 5 a second time.  Same result as above.

4. Without notice or confirmation the "Muff" artifact page loaded.

Comments:

1. Although the keypad was reasonably easy for me to use, the buttons  
are much smaller than the buttons on the iPhone keypad (at least as VO  
recognizes them), this * might * cause a problem for others.

2. Someone should verify that visually the numbering on the buttons is  
of a sufficient size to make them easy to read for low vision users,  
that the display works correctly with iPhone built-in magnifier, and  
that colours pass the WCAG 2.0 contrast criteria.  Should probably do  
this last step for all UIs

3. I am not sure if the automatic redirect to the artifact page is  
expected behavior after a code has been entered, but if it is then  
some steps need to be taken to conform with WCAG 2.0 priority A:

http://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits-required-behaviors.html
http://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-unpredictable-change.html

Hope that helps,
Everett