W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2001

Re: Priorities of Checkpoints 3.6 and 3.7

From: David Poehlman <poehlman1@home.com>
Date: Thu, 25 Jan 2001 09:24:02 -0500
Message-ID: <00d301c086da$774cfaa0$2cf60141@mtgmry1.md.home.com>
To: "jon gunderson" <jongund@ux1.cso.uiuc.edu>, <w3c-wai-ua@w3.org>
my problem with tinkering with refreshes still holds.  there is
content that will be missed if we control the refresh and that which
will be missed if we do not.  I think this should be kicked around a
bit with the content people and perhaps pf or a group that sets rules
for causing the refreshes in the first places?  I think then if you
are going to require the user agent to interact in this way that you
must also require that it store the refreshed content and allow it to
be retrieved as needed.

----- Original Message -----
From: "jon gunderson" <jongund@ux1.cso.uiuc.edu>
To: <w3c-wai-ua@w3.org>
Sent: January 24, 2001 9:44 AM
Subject: Priorities of Checkpoints 3.6 and 3.7


I think the raltionale for them being P2 is that in the case of
redirects
the author had not intended the page with the redirect to be viewed
anyway, so that not having access was not considered to be a P1 issue.
So
I thin this one does not need to be changed.

For automatic client side refreshes this probably needs to be changed
to
a P1. One techniques is that the stop loading button stops the
refreshes
and the user can refresh manually.  We should see if this already
works
with current browsers.

Jon
Received on Thursday, 25 January 2001 09:24:05 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:29 UTC