Fluid Engage - Ideal accessible interaction for code entry

[James William Yoon]

It's certainly something the designers are thinking around. We'll make sure
these issues are addressed and resolved in the next design iteration.

On Tue, Feb 23, 2010 at 12:38 PM, Colin Clark <colinbdclark at gmail.com>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
>
> ---
> Colin Clark
> Technical Lead, Fluid Project
> http://fluidproject.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20100223/03d635c0/attachment.html>