Seventeen requirements: platform software must offer documented services that let user-interface software interoperate with assistive technology (11.5.2.1) and that let assistive technology interoperate with that software (11.5.2.2), supporting where the concept exists the items 11.5.2.5 through 11.5.2.17; user-interface software must use the documented platform accessibility services, or other documented services where those fall short (11.5.2.3), and assistive technology must use them (11.5.2.4). Through those services software must expose to assistive technology the name, role, description, states and boundary of each element (11.5.2.5); table rows, columns and their headers (11.5.2.6); current value and range limits (11.5.2.7); label relationships (11.5.2.8); parent and child relationships (11.5.2.9); text content, attributes and boundaries (11.5.2.10); the available actions (11.5.2.11) and, where security allows, their execution (11.5.2.12); focus, insertion point and selection tracking (11.5.2.13) and, where security allows and users can change them, their modification (11.5.2.14); notification of changes to those attributes (11.5.2.15); and, where security allows, modification of element states and properties (11.5.2.16) and of values and text through platform input methods (11.5.2.17).
This control maps to 1 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 1 it maps to, and the evidence behind each claim, over MCP and REST.