Thread Subject: Re: Animation
Note
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Faruk Ates
Date: Tue, Jul 17 2007 9:10 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Jared Smith: "Re: Animation"
- Previous message in thread: Sean Hayes: "Re: Animation"
- Messages sorted by: Author | Thread | Date
On 16 Jul 2007, at 19:40, Sean Hayes wrote:
> Should we be harmonizing with WCAG here?
>
> Pausing: Moving, blinking, scrolling, or auto-updating information
> can be paused by the user unless it is part of an activity where
> timing or movement is essential. Moving content that is pure
> decoration can be stopped by the user. (Level AA) How to Meet 2.2.3
>
> Also if such content is informational, this provision must allow
> hast information is lost during the paused interval.
I have a question about this: suppose you offer animation controls on
the site, to enable/disable decoration-animations for instance (not
so much pause them mid-play, but simply enable/disable them site-wide)
… should those controls be offered on all pages, all pages where
animations are present, or is it acceptable within the realm of
accessibility to only offer those controls on a "Settings" or
configuration type page?
I'm reminded of the Jeremy Keith Button®: http://mezzoblue.com/about/
mezzoblue/
Nutshell: it's a fixed-vs-full layout width toggle for browsing
Mezzoblue, but the toggle is only available on that one page.
--
Faruk Ates
- Next message in Thread: Jared Smith: "Re: Animation"
- Previous message in Thread: Sean Hayes: "Re: Animation"
WebAIM is an initiative of:
