Thread Subject: Re: Animation

From: Jared Smith
Date: Tue, Jul 17 2007 10:15 AM

• Return to this mailing list's archives
• View all messages in this thread
• Next message in thread: Robinson, Norman B - Washington, DC: "Re: Animation"
• Previous message in thread: Faruk Ates: "Re: Animation"
• Messages sorted by: Author | Thread | Date

Regarding WCAG 2.0 harmonization and some of the comments from the
TEITAC meetings, here's a stab at wording:

A mechanism must be provided to either stop/restart or hide/reveal
informational content that animates, moves, blinks, or scrolls for
more than three seconds, unless the animation provides only an
indication of current status or it is part of an activity where timing
or movement is essential. Purely decorative content that is animated
for more than three seconds can be stopped or hidden by the user.

Notes on this wording:

- Animation is currently covered in two section - Animation (3.2-B)
and Pausing (6.1-M - Web and Web Apps only). I'm not sure of (nor can
I find) the justifications for the separation, but the wording above
re-combines them.
- This adds the 3-second threshold to the web requirement. It was
unclear if this applied to animated content before because it was
required of animation in 3.2, but not stated (thus excluded?) in
6.1-M.
- Removes the restriction that only 'software' can stop animation. I
can provide animation controls within a web page itself.
- In most web browsers, the user can press ESC to stop (and then
Refresh to restart) animated GIFs. Is this sufficient or must a web
page author provide a specific control?
- "auto-updating content" is removed. I'm not sure how to address this
because there are many auto-updating 'things' that have no impact on
accessibility. As Peter mentioned at the meeting, WAI-ARIA, etc. have
mechanisms for providing access to auto-updating content.

Jared Smith

• Next message in Thread: Robinson, Norman B - Washington, DC: "Re: Animation"
• Previous message in Thread: Faruk Ates: "Re: Animation"