For non-web software with a user interface within the ICT, the software has to satisfy the WCAG 2.2 criteria of this group: single-pointer alternatives to multipoint or path gestures (11.2.5.1); pointer actions that can be aborted or complete on release (11.2.5.2); accessible names that contain the visible label (11.2.5.3); motion-triggered functions also operable from the interface and able to be disabled (11.2.5.4); a single-pointer alternative to dragging (11.2.5.7); pointer targets no smaller than 24 CSS pixels square, or spaced enough (11.2.5.8). Label in name applies to open functionality; pointer gestures, cancellation, dragging and target size are restated in Tables 11.10 to 11.13.
This control maps to 7 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 7 it maps to, and the evidence behind each claim, over MCP and REST.