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

RE: Multiple versions of a page

From: Charles McCathieNevile <charles@w3.org>
Date: Wed, 20 Mar 2002 21:33:58 -0500 (EST)
To: <gian@stanleymilford.com.au>
cc: <phoenixl@sonic.net>, <Lee.Otto@aspect.com.au>, <w3c-wai-gl@w3.org>
Message-ID: <Pine.LNX.4.30.0203202132500.26652-100000@tux.w3.org>
Well,

I suspect that one reason why they are not widely documented is that what is
in fact obvious varies wildly according to the specific situation - the
technology being used, the skills and experiences of the person deciding what
groupings to support, etc.

Chaals

On Wed, 20 Mar 2002 gian@stanleymilford.com.au wrote:

  I am sure there are some "reasonably obvious" groupings.  Why aren't
  they documented anywhere?

  > -----Original Message-----
  > From: charles [mailto:charles@w3.org]
  > Sent: Tuesday, 19 March 2002 12:51 AM
  > To: phoenixl
  > Cc: Gian Sampson-Wild; Lee.Otto; w3c-wai-gl
  > Subject: RE: Multiple versions of a page
  >
  >
  > I am sure that there are a number of "reasonably obvious"
  > functionality
  > groupings. I assume that the first thing we will see is the
  > "reasonably
  > obvious" ones catered for, and later we will see more adaptive systems
  > designed to better provide for the needs of a wide range of people.
  >
  > There is old technology available to do this. The real
  > question in my mind is
  > how to make sure that people are getting a version they can
  > use, and then
  > how to make sure they can get the version that is best for
  > them to use.
  >
  > Cheers
  >
  > Charles McCN
  >
  > On Sat, 16 Mar 2002, phoenixl wrote:
  >
  >   Hi,
  >
  >   I'm not sure I would agree with this analysis.  I think
  > there are some
  >   inherent groupings of functionality.  For example, in general, the
  >   major group of people which is affected by tables for layout is
  >   pretty much the same group affected by javascript.
  >
  >   Scott
  >
  >   > Hi,
  >
  >   > I think Lee is right, and one major problem with having multiple
  >   > versions of a web page is that we can NEVER know the variety of
  >   > disabilities a person may have, and therefore splitting
  > an accessible
  >   > web site into several sites can end up making that site
  > essentially
  >   > inaccessible. What I mean, is that if someone needs
  > checkpoints A and B
  >   > to access a site will not be able to do so if checkpoint
  > A is solved by
  >   > Site Version 1, and checkpoint B by Site Version 3.
  >
  >   > Cheers,
  >   > Gian
  >
  >
  > --
  > Charles McCathieNevile    http://www.w3.org/People/Charles
  > phone: +61 409 134 136
  > W3C Web Accessibility Initiative     http://www.w3.org/WAI
  > fax: +33 4 92 38 78 22
  > Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
  > (or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia
  > Antipolis Cedex, France)
  >
  >
  >



-- 
Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI  fax: +33 4 92 38 78 22
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Wednesday, 20 March 2002 21:34:08 GMT

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