2.5.2 Pointer Cancellation adjust notes for consistency with 2.5.1 Pointer Gestures

[maryjom]

Modify comments for 2.5.2 Pointer Cancellation to align with those for 2.5.1 Pointer Gestures.

Copying in just the 2.5.1 approved content and notes as well as the 2.5.2 notes (as they are in the current editor's draft) that would have to be adjusted to match.

2.5.1 Pointer Gestures guidance is as follows:

This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.1 (also provided below), making changes to the notes for non-web documents by replacing “web content” with "content" and for non-web software by replacing "web content" with "non-web software" and "user agent" with "underlying platform software".

(non-web documents)

NOTE
Multipoint and path-based gestures are less common in documents. An example where a document author could add such gestures is an interactive prototype document created in a software design tool.

(non-web software)

NOTE
This requirement applies to [non-web software] that interprets pointer actions (i.e. this does not apply to actions that are required to operate the [underlying platform software] or assistive technology).

---

2.5.2 Pointer Cancellation guidance would need updates to the following content:

This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.2 (also provided below), making changes to the notes by replacing “web content” with "content" or “non-web software” and removing "user agent" as an excepted case for non-web software.

(for non-web documents)

NOTE
Applicability of this Success Criterion would be limited to document types where a document author can add content that interprets pointer actions and control which events are used for executing functionality. For example, prototyping tools used to design software.

(for non-web software)

NOTE
This requirement applies to [non-web software] that interprets pointer actions (i.e. this does not apply to actions that are required to operate assistive technology).

NOTE
Non-web software applications are not responsible for pointer actions required to operate the underlying user agent or platform software.

[maryjom]

The proposed changes to make 2.5.2 Pointer Cancellation more consistent with 2.5.1 Pointer Gestures are:

This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.2 (also provided below), making changes to the notes for non-web documents by replacing “web content” with "content" and for non-web software by replacing "web content" with "non-web software" and "user agent" with "underlying platform software".

(for non-web documents)

NOTE
Content that interprets pointer actions and controls which events are used for executing functionality is less common in documents. An example where a document author could add such functionality is an interactive prototype document created in a software design tool.

(for non-web software)

NOTE
This requirement applies to [non-web software] that interprets pointer actions (i.e. this does not apply to actions that are required to operate the [underlying platform software] or assistive technology).

[maryjom]

Per the 4 May meeting, adjusted the non-web document note to add commas, which now reads:

NOTE
Content that interprets pointer actions, and controls which events are used for executing functionality, is less common in documents. An example where a document author could add such functionality is an interactive prototype document created in a software design tool.