For non-web software with a user interface within the ICT, the software has to satisfy the WCAG 2.2 criteria of this group: structure and relationships available programmatically (11.1.3.1); a reading order that keeps the meaning (11.1.3.2); instructions that do not rely only on shape, size, position or sound (11.1.3.3); no lock to one display orientation unless essential (11.1.3.4); programmatic purpose for fields collecting user data (11.1.3.5). 1.3.1, 1.3.2 and 1.3.5 apply to open functionality (1.3.5 only where the technology can mark input meaning); 1.3.4 only where the hardware is meant to be reoriented in typical use.
This control maps to 6 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 6 it maps to, and the evidence behind each claim, over MCP and REST.