Merge pull request #267 from w3c/2.5.2

Add draft for 2.5.2

Author: JJdeGroot

comments/2.5.2.md

@@ -5,6 +5,44 @@
 [wcag:pointer-cancellation]
 [wcag2ict:applying-sc-2-5-2-pointer-cancellation-to-non-web-documents-and-software]
 
-Placeholder
+This applies directly as written, and as described in [Intent from Understanding Success Criterion 2.5.2](https://www.w3.org/WAI/WCAG22/Understanding/pointer-cancellation#intent).
 
-[issue:38]
+**2.5.2 Pointer Cancellation:** For functionality that can be operated using a single pointer, at least one of the following is true:
+
+<dl>
+<dt>No Down-Event</dt>
+<dd>
+The down-event of the pointer is not used to execute any part of the function;
+</dd>
+<dt>Abort or Undo</dt>
+<dd>
+Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
+</dd>
+<dt>Up Reversal</dt>
+<dd>
+The up-event reverses any outcome of the preceding down-event;
+</dd>
+<dt>Essential</dt>
+<dd>
+Completing the function on the down-event is essential.
+</dd>
+</dl>
+
+[note:This requirement applies to mobile applications that interpret pointer actions (i.e., this does not apply to actions that are required to operate the platform software, operating system, or assistive technology). Each layer is responsible for its own pointer actions only, not for those in an underlying layer.]
+
+[note:Functions that emulate a keyboard or numeric keypad key press are considered essential.]
+
+[note:The determination of "essential" should focus on whether the function itself requires down-event activation, rather than solely on technological constraints. However, limitations of the underlying technology platform may also constitute valid exceptions where developers cannot provide alternative implementations.]
+
+<div class="example wcag2mobile">
+<strong>Example:</strong>
+<br/>
+Examples of essential functionality in mobile applications include:
+<ul>
+  <li>Drawing and sketching functionality where continuous pressure-sensitive input begins on the down-event.</li>
+  <li>Keyboard emulation functionality where keys activate on down-event to match expected physical keyboard behavior.</li>
+  <li>Musical instrument functionality where the down-event timing is essential to produce the intended sound at the correct moment.</li>
+  <li>Gaming functionality requiring precise down-event timing such as rhythm games, sports simulations and action games.
+  </li>
+</ul>
+</div>

index.html

@@ -3122,16 +3122,53 @@ <h2>Success Criterion 2.5.2 Pointer Cancellation</h2>
         </footer>
       </details>
     </p>
-<p>Placeholder</p>
+<p>This applies directly as written, and as described in <a href="https://www.w3.org/WAI/WCAG22/Understanding/pointer-cancellation#intent">Intent from Understanding Success Criterion 2.5.2</a>.</p>
+<p><strong>2.5.2 Pointer Cancellation:</strong> For functionality that can be operated using a single pointer, at least one of the following is true:</p>
+<dl>
+<dt>No Down-Event</dt>
+<dd>
+The down-event of the pointer is not used to execute any part of the function;
+</dd>
+<dt>Abort or Undo</dt>
+<dd>
+Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
+</dd>
+<dt>Up Reversal</dt>
+<dd>
+The up-event reverses any outcome of the preceding down-event;
+</dd>
+<dt>Essential</dt>
+<dd>
+Completing the function on the down-event is essential.
+</dd>
+</dl>
 <p>
-      <div class="note" title="Work In Progress">
-        <p>
-          <a href="https://github.com/w3c/matf/issues/38" target="_blank">
-            Read issue #38 on GitHub
-          </a>
-        </p>
+      <div class="note">
+        <p>This requirement applies to mobile applications that interpret pointer actions (i.e., this does not apply to actions that are required to operate the platform software, operating system, or assistive technology). Each layer is responsible for its own pointer actions only, not for those in an underlying layer.</p>
+
+      </div>
+    </p>
+<p>
+      <div class="note">
+        <p>Functions that emulate a keyboard or numeric keypad key press are considered essential.</p>
+
       </div>
     </p>
+<p>
+      <div class="note">
+        <p>The determination of &quot;essential&quot; should focus on whether the function itself requires down-event activation, rather than solely on technological constraints. However, limitations of the underlying technology platform may also constitute valid exceptions where developers cannot provide alternative implementations.</p>
+
+      </div>
+    </p>
+<div class="example">
+<strong>Example:</strong>
+<br/>
+Examples of essential functionality for mobile applications include:
+<ul>
+  <li>Features required for meeting system requirements (such as waking a device from sleep, power management controls, and emergency functions)</li>
+  <li>Interactions that require pointer down to function, such as drawing or sketching tools</li>
+</ul>
+</div>
 
       </section>