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

RE: 2.1 thoughts

From: Charles McCathieNevile <charles@w3.org>
Date: Mon, 6 May 2002 19:54:12 -0400 (EDT)
To: Gregg Vanderheiden <GV@TRACE.WISC.EDU>
cc: <w3c-wai-gl@w3.org>
Message-ID: <Pine.LNX.4.30.0205061952540.5045-100000@tux.w3.org>
Yes I am. But that isn't a problem - most web pages already are. It is just a
question of how we phrase the requirement, so we can ensure that we aren't
accidentally excluding something, or requiring an implementation detail too
specific for the use cases we have.



On Mon, 6 May 2002, Gregg Vanderheiden wrote:

  Hi Charles.

  I am very confused.

  Are you saying that all web pages have to be navigable and operable from
  a phone keypad that doesn't even support tab?


  Gregg Vanderheiden Ph.D.
  Ind Engr - Biomed - Trace,  Univ of Wis

  > -----Original Message-----
  > From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On
  > Of Charles McCathieNevile
  > Sent: Monday, May 06, 2002 2:27 PM
  > To: Gregg Vanderheiden
  > Cc: w3c-wai-gl@w3.org
  > Subject: RE: 2.1 thoughts
  > On Mon, 6 May 2002, Gregg Vanderheiden wrote:
  >   Chaals wrote
  >   this starts to make sense, but I don't like it - it should be
  possible in
  >   most cases to just use a mouse to drive everything, yet that doesn't
  >   to be supported here.
  >   Question,
  >   How would you enter text with a mouse?
  >   (Using an on screen keyboard doesn't count since that is a keyboard
  >   far as the application is concerned).
  > response:
  > Yes, I mean that it should be possible to use an onscreen keyboard (as
  > done in kiosk type environments in some cases). The point is that most
  > now prefer to use a mouse, and in some situations (such as the EIAD
  > designed for people with brain injuries) rely on a touch screen.
  > Using the keyboard to move around requires an abstraction of
  > Point and click doesn't, for folks who can use it. We need to support
  > cases, I think.
  >   ALSO in response to
  >   5. All functionality operable via text input plus tab, up, down,
  >   right, and enter.
  >   (these are the text and command keys that can be ensured would be on
  >   "keyboards"  (real or virtual).)
  >   Chaals wrote
  >   No they are not. One of my two keyboards doesn't have this. And
  >   speech-based systems don't have up, down, left, right as ways of
  >   things. This is too specific to visual environments.
  >   3 Questions
  >   1- Which keys were missing.  The arrowkeys?
  > Yep, my phone doesn't have them, nor a tab key. And text entry isn't
  > efficient either.
  >   2 - What speech input system doesn't provide a way to operate
  >   keys?  (One on a system without a keyboard?)
  > One which isn't simply a speech input interface to a desktop computer
  model -
  > for example a VoiceXML application, or similar system. Again, my phone
  > voice control of many functions, but not voice simulation of keyboard
  >   3 - How about
  >   --- Text input plus  "step to next" (TAB) and "Activate". (ENTER).
  >   The arrowkeys can be optional but all function needs to be operable
  >   text and the two functions.
  > Well, I prefer to start from "device independent mechanisms, including
  > activation where available (e.g. Voice, point and click) and
  navigation among
  > options (e.g. "next", "previous", "activate" using voice commands, or
  > keyboard input)
  > By the way, this is the kind of problem that User Agent group has
  dealt with
  > fairly extensively - it would be worth asking their thoughts in my
  > opinion.
  > cheers
  > Chaals

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 Monday, 6 May 2002 19:54:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:41 UTC