Thread Subject: Re: 3-I Pausing

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: Gregg Vanderheiden
Date: Wed, Sep 26 2007 11:05 AM


Nice Catch Jared.

There are two issues and we need to be sure to cover both.

Jared points out an important issue. In WCAG 1.3.1 covers his concern
since information must be accessible regardless of presentation. And TIMING
provision covers any information that cannot be read because it isn't around
long enough.

So this provision was just about distraction.

But his point is good. Perhaps the HIDING option should only be available
to "busy" or decorative moving items.

Jared's option 1 does this very nicely.

Option #2 also does it and reads better when using MUST format. However the
words "changes" needs to be changed to "it" or the list since not all are
really changes. Also the Moving in the last paragraph needs to be
expanded.

Hmmm hard to do.... maybe changes needs to stay and only blinking needs
to be added to end

> A mechanism must be provided to pause moving, blinking, scrolling, or
> auto-updating information that lasts more than 3 seconds unless the
> changes are an essential part of the activity. A mechanism must be
> provided to stop or hide moving or blinking content that is pure
decoration.


Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.

> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED = [mailto:teitac-
> = EMAIL ADDRESS REMOVED = ] On Behalf Of Jared Smith
> Sent: Wednesday, September 26, 2007 9:38 AM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] 3-I Pausing
>
> On 9/26/07, Andi Snow-Weaver < = EMAIL ADDRESS REMOVED = > wrote:
> > Shall we adopt this updated WCAG provision for 3-I Pausing?
>
> The think new WCAG wording is pretty bad. Without the definition, it
> reads as, "Moving information can be paused, unless the *INFORMATION*
> is important" and that's exactly the opposite of what we want. The
> definition slightly clarifies that the moving can be stopped unless
> the moving itself is essential, but it's still very confusing and an
> important clarification that belongs in the provision itself.
>
> Also, if it's 'information', doesn't that naturally mean it's
> important and shouldn't be hidden? I thought the hiding option would
> only be for decorative information.
>
> Suggested wordings:
> Moving, blinking, scrolling, or auto-updating information on a Web
> page that lasts for more than 3 seconds can be paused by the user
> unless the moving, blinking, scrolling, or auto-updating is essential
> to the activity. Moving or blinking content that is pure decoration
> can be stopped [OR HIDDEN] by the user.
>
> OR
>
> A mechanism must be provided to pause moving, blinking, scrolling, or
> auto-updating information that lasts more than 3 seconds unless the
> changes are an essential part of the activity. A mechanism must be
> provided to stop or hide moving content that is pure decoration.
>
> Jared Smith
>


WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University