Thread Subject: Re: Animation
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: Robinson, Norman B - Washington, DC
Date: Tue, Jul 17 2007 1:05 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Gregg Vanderheiden: "Re: Animation"
- Previous message in thread: Jared Smith: "Re: Animation"
- Messages sorted by: Author | Thread | Date
Well considering that most web access allows bookmarking and
direct access without coming from "the one entry page" then putting the
controls only in one place doesn't really work. I'd say that is a
specific implementation that is deemed bad or good, but not necessarily
a clear accessibility issue - just the potential for bad design. You
could also address this by keeping user preferences after login and in
other ways however.
Norman B. Robinson
Section 508 Coordinator
IT Governance, US Postal Service
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Faruk
Sent: Tuesday, July 17, 2007 11:06 AM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Animation
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(r): http://mezzoblue.com/about/
Nutshell: it's a fixed-vs-full layout width toggle for browsing
Mezzoblue, but the toggle is only available on that one page.