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.

Loretta