Everything the content does can be done from a keyboard interface, with no specific keystroke timing needed; the only exception is a function whose input inherently depends on the route the pointer travels rather than its start and end points.
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.