For non-web software with a user interface within the ICT, the software has to satisfy the WCAG 2.2 criteria of this group: detected input errors identified and described in text (11.3.3.1); labelling or guidance wherever input is expected (11.3.3.2); correction suggestions when they are known (11.3.3.3); submissions with legal, financial or data consequences reversible, checked or confirmed (11.3.3.4); earlier entered information offered again instead of retyped (11.3.3.7); no cognitive function test in authentication without an alternative or assistance (11.3.3.8). Error identification applies to open functionality; error prevention and accessible authentication are restated in Tables 11.15 and 11.16.
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.