For non-web software with a user interface within the ICT, the software has to satisfy the WCAG 2.2 criteria of this group: descriptive titles (11.2.4.2); a focus sequence that preserves meaning (11.2.4.3); each link's purpose clear from its text or surrounding context (11.2.4.4); headings and field labels describing topic or purpose (11.2.4.6); a visible keyboard focus indicator (11.2.4.7); a focused component not fully hidden by author content (11.2.4.11). Bypass blocks and multiple ways are void; 11.2.4.2 requires titles describing each window or screen where the platform supports titles; focus order is restated in Table 11.9; a link is any control behaving like a hypertext link.
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.