W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2001

Re: Updating 2.4, re-revised

From: Charles McCathieNevile <charles@w3.org>
Date: Thu, 31 May 2001 13:21:16 -0400 (EDT)
To: Matt May <mcmay@bestkungfu.com>
cc: Adam Victor Reed <areed2@calstatela.edu>, <w3c-wai-gl@w3.org>
Message-ID: <Pine.LNX.4.30.0105311315240.29668-100000@tux.w3.org>
I have a slightly different approach I think, or maybe I just think about it
in different words.

To make the thing accessible to various groups of people you need to have the
option to stop the timeout. There are some cases where this is genuinely not
feasible, and those things are not going to be accessible to such people. In
a context such as the Disability Discrimination Act in Australia, any
complaint is likely to result in a finding that the site cannot be made
accessible for some external reason, and therefore is eligible for an
exemption (like undue burden provisions in other situations). That doesn't
mean they are accessible, it means that they are not, and cannot be, and it
is not their fault.

This, by the way, is the basis for having a more granular conformance profile
as well as the nice simple scale of A, double-A, triple-A. Such a site may
pose no problems to certain groups of people, and it would be useful to have
a mechanism for stating that explicitly. EARL provides just such a mechanism.
But for the most part, it is better to aim for accessibility to all, at some
level, and the current scheme provides a reasonably simple approach to
dealing with that.

cheers

Charles

On Thu, 31 May 2001, Matt May wrote:

  ----- Original Message -----
  From: "Adam Victor Reed" <areed2@calstatela.edu>

  > And it is not difficult to design bypass
  > technologies that will still meet legitimate security and economic
  > constraints.

  I disagree. Timeouts such as those present in Dell's site (along with those
  at my former companies) are based on hard business rules on the back end.
  Expedia needs you to lock in your reservation so it can relay that request
  to the computerized reservation system it gets its data from. (And it uses
  meta refreshes to keep the HTTP connection alive while it contacts the slow
  pathetic creature.) HomeGrocer and Webvan needed to accurately manage
  delivery trucks and merchandise in the best possible manner. Resource
  management is critical in e-commerce.
Received on Thursday, 31 May 2001 13:21:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:10 GMT