This Wiki page is edited by participants of the WCAG Working Group. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

Comment Summary 2-5-2

From WCAG WG
Jump to: navigation, search

2.5.2 Accidental Activation

SC Nov 5th Draft: For single-pointer activation, at least one of the following is true:

  • Activation is on the up-event, either explicitly or implicitly as a platform's generic activation/click event;
  • A mechanism is available that allows the user to choose the up-event as an option;
  • Confirmation is provided, which can dismiss activation;
  • Activation is reversible;
  • Down-event activation event is essential and waiting for the up-event would invalidate the activity.

New:

For single pointer activation a mechanism is available to use activation on the up-event, either explicitly or implicitly as a platform's generic activation event, unless one of the following is true:

  • The activation is confirmed;
  • The result of the activation is reversible;
  • Down-event activation is essential;

Definition of Single Pointer Activation:

Completion of an operation resulting from one point of contact with the screen

This is in contrast to multi-touch. A pointer can be any point of contact on the screen made by a mouse cursor, pen, touch (including multi-touch), or other pointing input device. This model makes it easier to write sites and applications that work well no matter what hardware the user has. For scenarios when device-specific handling is desired, the Pointer Events [pointerevents] specification also defines properties for inspecting.

New (11/27):

For single pointer activation implemented by the author, activation occurs on the up-event, either explicitly or implicitly as a platform's generic activation event, unless one of the following is true:

  • The result of the activation is reversible;
  • Down-event activation is essential;

Definition of Single Pointer Activation:

Completion of an operation resulting from one point of contact with the screen

This is in contrast to multi-touch. A pointer can be any point of contact on the screen made by a mouse cursor, pen, touch (including multi-touch), or other pointing input device. This model makes it easier to write sites and applications that work well no matter what hardware the user has. For scenarios when device-specific handling is desired, the Pointer Events [pointerevents] specification also defines properties for inspecting.

New (11/28)

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;
  • Essential Completing the function on the down-event is essential.

Alternative to bullet #1 No Down-Event: The down-event of the pointer does not trigger effects that last past the up-event (to handle the cases where useful information appears on click and disappears on release.)

Also need to update definition for Single Pointer Activation to "Single Pointer" (in 3.2.6 also):

one point of contact with the screen

This is in contrast to multi-touch. A pointer can be any point of contact on the screen made by a mouse cursor, pen, touch (including multi-touch), or other pointing input device. This model makes it easier to write sites and applications that work well no matter what hardware the user has. For scenarios when device-specific handling is desired, the Pointer Events [pointerevents] specification also defines properties for inspecting.

Issues

Issue 561: Thank you for the comment. Due to the increase diversity of input events we feel that it is best to not limit reversibility to up-event initiated actions.

Issue 380: Response Drag and Drop handle in Understanding document, series of concurrent actions (drag and drop, double-click, etc), covered by SC 2.5.1. Drag and drop is not a single point activation.

Issue 364: Response..we made a revision that we think addresses your concern, please review.

Issue 330: Response..Add a reference to Pointer Event Spec and - event fired when the trigger stimulous id relaesed for more information see the Pointer Event Spec for pointer up event, (https://www.w3.org/TR/pointerevents/#the-pointerup-event). Add single pointer activation definition change. @activation resulting from@ one point of contact with the screen. Exclude drag and drop?


GitHub open issues link

http://github.com/w3c/wcag21/labels/~comment-accidental-activation