Add a bullet or Note to 3.3 to make keyboard equivalents explicit

[DavidMacDonald]

I think 3.3 needs a bullet with explicit mention that every touch gesture should have a keyboard equivalent, although there is a bullet in 3.4 about this it's not clear that this is necessary for 3.3 issues in the mobile doc.

perhaps there is no mention of a keyboard equivelent requirement because of the exemption in 2.1.1
"except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A)"

This WCAG exemption was intended for drawing programs and when the user uses a mouse to draw something...I don't think the exemption should apply to gestures even though they depend on the "user's movement between endpoints".
Suggestion:

Note: In order to meet WCAG SC 2.1.1 any outcome accomplished by a gesture would need to have a keyboard alternative.

[KimPatch]

Jan addressed this with a similar note

JR: Note I proposed: Note: While improving the accessibility of touchscreen gestures is important, keyboard accessibility is still required by some users and to meet WCAG 2.0 (see “3.1 Keyboard Control for Touchscreen Devices”).

Group agreed to go with Jans note