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

RE: Not described in words

From: Sean Hayes <Sean.Hayes@microsoft.com>
Date: Tue, 13 Mar 2007 15:39:57 +0000
To: Loretta Guarino Reid <lorettaguarino@google.com>, "Bailey, Bruce" <Bruce.Bailey@ed.gov>
CC: Gregg Vanderheiden <gv@trace.wisc.edu>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Message-ID: <7261AC2A5F73904CA41773C8F00813FF1C6D91E1@EA-EXMSG-C309.europe.corp.microsoft.com>
Loretta, Thats a good example; so we have time dependant non analog (threshold) events, and we have non-time dependant analog, e.g. pressure which is a force.

Neither of these would be included in "time-dependant analog".

Described, or discerned in text might be:

"draw pixel 1,1 at with pen black at pressure 100N/m2,
draw pixel 1,2 at with pen black at pressure 99N/m2,draw pixel 1,3 at with pen black at pressure 98N/m2,draw pixel 2,3 at with pen black at pressure 98N/m2,draw pixel 2,4 at with pen black at pressure 99N/m2,draw pixel 3,4 at with pen black at pressure 97N/m2,draw pixel 4,4 at with pen black at pressure 96N/m2,..."

Which is not effective for the task.

My proposal was:

Operation of <content> is achievable through a keyboard interface without time constraint, unless performing the underlying task requires a form of analog input or time constraint that makes this impossible.

Sean Hayes
Standards and Policy Team
Accessible Technology Group
  mob +44 7977 455002
  office +44 117 9719730

From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Loretta Guarino Reid
Sent: 13 March 2007 14:52
To: Bailey, Bruce
Cc: Gregg Vanderheiden; w3c-wai-gl@w3.org
Subject: Re: Not described in words

To me, discern textually means something quite different than describing in words.  It is about something being recognizable *as* text.  It is about characters truly representing a function.  A slider might have a value between zero and 100 percent, so numbers can work too.

Thanks for trying to paraphrase what "discern textually" means to you, since I have been having so much trouble with that phrase. Perhaps we means something like "can be represented functionally in text"? Although it is the granularity of the functionality that is often the problem. "Turn arbitrary pixel black" seems functional, but isn't effectively functional.

Loretta wrote earlier:
<q>Bruce, we would need to think this through more carefully, since
removing the reference to timing means that keyboard operations that
depend upon the amount of time that a key is held down would be
permitted, and we know that this introduces accessibility problems for
some people.</q>

@@without requiring specific timings for individual keystrokes@@

This is the third time I am asking:  Can someone please provide some examples of why this is necessary to stipulate?  The ones that come to my mind are all gaming related.  Or maybe an application that ignores/defeats Sticky-Keys.  Is this SC really trying to address that potential problem?

Here is an example: double-clicking with the mouse often has different behavior from a series of two single clicks.  The  difference between these two gestures is based on the amount of time that elapses between the click actions. If you can't click quickly enough, you may not be able to invoke the double-click action.

Received on Tuesday, 13 March 2007 15:40:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:02 UTC