The following paragraph from the dragging movement SC has come up a number of times in queries to me that I think it is worth bringing to the WG's attention.

This requirement is separate from keyboard accessibility because people using a touch screen device may not use a physical keyboard. Keyboard specific interactions such as tabbing or arrow keys may not be possible when encountering a drag and drop control. Note, however, that providing a text input can be an acceptable single-pointer alternative to dragging. For example, an input beside a slider could allow any user to enter a precise value for the slider. In such a situation, the on-screen keyboard that appears for touch users offers a single-pointer means of entering an alphanumeric value.

Specifically, the paragraph is being interpreted as a bit of double speak. Where it initially states that the SC is separate from keyboard accessibility - but then later states that someone could use the mobile on screen keyboard to enter a value into a text field.

This has raised the question as to why on screen keyboards, in general, cannot be used to pass this SC. This question has been particularly raised when reviewing native/web desktop applications where the primary action of someone using the application would largely revolve around needing to be able to use their keyboard (or if they cannot use a keyboard, voice control software which would allow someone to speak keyboard commands if needed. E.g., "press left X times" to move something).

I can imagine a few responses to these queries (but me assuming answers aren't official responses, so that's why i'd be great to get them documented), and this is again not an issue of where I'm looking how to fix something - but rather clarifications (ideally even citations) being added as to why these sorts of suggestions pass or not, and why, either way.