W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > May 2012

Re: Procedure #2 & Note in Expected Results

From: Loretta Guarino Reid <lorettaguarino@google.com>
Date: Thu, 24 May 2012 14:52:02 -0700
Message-ID: <CAHu5OWa_FuqZzTkGKZPmzz9fDyhZckN2DTcTTDbix-ZNYQrU4Q@mail.gmail.com>
To: makoto.ueki@gmail.com
Cc: public-comments-wcag20@w3.org
On Tue, Apr 24, 2012 at 2:14 AM, <noreply@w3.org> wrote:

> Name: Makoto Ueki
> Email: makoto.ueki@gmail.com
> Affiliation: WAIC (Japan) / Infoaxia, Inc.
> Document: TD
> Item Number: F61
> Part of Item: Tests
> Comment Type: general comment
> Summary of Issue: Procedure #2 & Note in Expected Results
> Comment (Including rationale for any proposed change):
> It is difficult to interpret and translate the following parts:
> --
> Procedure #2.
> Leave the content open for a length of time 10 times what a user could
> reasonably be expected to keep the viewport open for. For instance, a
> site's web analytics may indicate that average user visits last 1 hour and
> most return users visit once per day. 24 hours could be considered an
> appropriate length of time for the procedure.
> --
> Note:
> Regardless of the time span used at step 2 of the procedure, if step 3
> tests true after any length of time, then step 4 must be confirmed and the
> expected results evaluated as at 1.
> --
> Could you explain what you meant?
> Proposed Change:
> Need to clarification for us to translate and share the procedures with
> JIS X 8341-3.
> ================================
Response from the Working Group
We have rewritten the test to make it easier to understand and follow:


1) Measure or estimate the amount of time that the average user spends on
the page.
2) Go to the page
3) Wait for 10 times the length of time the average user stays on the
page.  (From Step 1)
4) Check to see if there is a change in context during this time.
5) If there is no change of context STOP.
6) If there is a change in context, then check to see if there is any
mechanism on the page that would have prevented that change of context.
7)  If there IS a mechanism for preventing that change of context, use that
mechanism to prevent that change of context and run the test over.
8) If there is a change of context and there are no mechanism to prevent
that change in context then you have a failure

* One way to measure or estimate the amount of time in step 1 would be to
check a web site's analytics to see how long the average user looks at the
* An example of step 6 would be a mechanism for turning off auto updates.

Expected Results

If you reach step 8 then the content fails this success criteria.

Loretta Guarino Reid, WCAG WG Co-Chair
Gregg Vanderheiden, WCAG WG Co-Chair
Michael Cooper, WCAG WG Staff Contact

On behalf of the WCAG Working Group
Received on Thursday, 24 May 2012 21:52:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:14:56 UTC