For input fields collecting information about the user, the purpose can be programmatically determined where the field matches one of the listed input purposes and the technology supports identifying it (for example HTML autocomplete tokens).
This control maps to 3 controls across 1 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 3 it maps to, and the evidence behind each claim, over MCP and REST.