For non-web software with a user interface within the ICT, the software has to satisfy the WCAG 2.2 criteria of this group: every function operable from a keyboard interface (11.2.1.1); focus can always be moved off a component by keyboard (11.2.1.2); single-character shortcuts that can be switched off, remapped or limited to focus (11.2.1.4). Keyboard applies where the platform offers a device-independent keyboard interface service, an on-screen keyboard alone not sufficing; no keyboard trap is restated in Table 11.5.
This control maps to 4 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 4 it maps to, and the evidence behind each claim, over MCP and REST.