Re: Accidental Activation wrap-up

WFM

JF

On Tue, Nov 28, 2017 at 2:05 PM, Repsher, Stephen J <
stephen.j.repsher@boeing.com> wrote:

> For SC Accidental Activation, I came up with an extra bullet  which I
> think addresses the concern at the end of today’s call.  Here’s the current
> proposal in full:
>
>
>
> For functionality which can be operated using a single pointer, at least
> one of the following is true:
>
> ·       *No Down-Event*: The down-event of the pointer is not used to
> execute any part of the function;
>
> ·       *Abort or Undo*: Completion of the function is on the up-event,
> and a mechanism is available to abort the function before completion or
> undo the function after completion;
>
> ·       *Up Reversal*: The up-event reverses any outcome of the preceding
> down-event;
>
> ·       *Essential*: Completing the function on the down-event is
> essential.
>
>
>
> With glossary links for functionality, mechanism, up/down-event, and
> single pointer all as is in the current draft, except that we simply delete
> the word “activation”.
>
>
>
> In very plain language:
>
> ·       No Down-Event – applicable to single click, double click, etc.
> where I can abort after any down-event  by moving pointer away
>
> ·       Abort or Undo – applicable to outcomes completed via up-event,
> but need to use down-event, such as drag and drop, gestures, or long press
>
> ·       Up Reversal = Covers situation on today’s call where up cancels
> the effect of down, so user can’t accidentally do anything.
>
> ·       Essential – Covers stuff like games as explained in understanding.
>
>
>
> Any issues?  Looks good?
>
>
>
> *Steve Repsher*
>
> Twitter <https://twitter.com/steverep> | LinkedIn
> <https://www.linkedin.com/in/steverepsherjr/> | GitHub
> <https://github.com/steverep>
>
>
>



-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion