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.
Thanks,
Everett Zufelt
http://zufelt.ca
Follow me on Twitter
http://twitter.com/ezufelt
View my LinkedIn Profile
http://www.linkedin.com/in/ezufelt
On 2010-02-23, at 11:31 AM, James William Yoon wrote:
On Tue, Feb 23, 2010 at 10:31 AM, E.J. Zufelt <[email protected]>
wrote:
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.
Our code entry keypad is the same size (pixel-for-pixel) as the
unlock keypad on the iPhone. I do see that the iPhone's dialing
keypad is slightly larger though. We'll take this feedback into
account when designing the next iteration of the keypad.
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
Duly noted. We'll look into this.
Also, preliminary testing shows that the application works great
with the built-in screen magnifier.
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
Filed as: ENGAGE-440
Thanks, Everett!
James
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
