ambiguous word "whether" in 4.6 regarding keyboard alternatives

[DavidMacDonald]

4.6
"Therefore, instructions (e.g. overlays, tooltips, tutorials, etc.) should be provided to explain what gestures can be used to control a given interface and whether there are alternatives. "

I think the word whether leaves it ambiguous whether there need to be keyboard alternatives. I think WCAG requires keyboard alternatives for all gestures.

[DavidMacDonald]

For reference, here are all the mentions of Keyboard in the document that could refer to 2.1.1

Intro

"Have we sufficiently explained why keyboard interface and modality independent controls are needed in the mobile environment?"

Section 1.1
"many mobile devices can be connected to an external keyboard and mouse, "

Section 3.1

Mobile device design has evolved away from built-in physical keyboards (e.g. fixed, slide-out) towards devices that maximize touchscreen area and display an on-screen keyboard only when the user has selected a user interface control that accepts text input (e.g. a textbox).

However, keyboard accessibility remains as important as ever and most major mobile operating systems do include keyboard interfaces, allowing mobile devices to be operated by external physical keyboards (e.g. keyboards connected via Bluetooth, USB On-The-Go) or alternative on-screen keyboards (e.g. scanning on-screen keyboards).

Supporting these keyboard interfaces benefits several groups with disabilities:..

Section 3.4

"Therefore, even when device manipulation gestures are provided, developers should still provide touch and keyboard operable alternative control options. "

4.4 Grouping

... It also reduces the number of redundant focus targets, which benefits people using screen readers and keyboard/switch control.

5.2 Provide easy methods for data entry. Users can enter information on mobile devices in multiple ways such as on-screen keyboard, Bluetooth keyboard, touch, and speech. ...

[ataulm]

@DavidMacDonald would it work for you if the last clause was omitted?

Therefore, instructions (e.g. overlays, tooltips, tutorials, etc.) should be provided to explain what gestures can be used to control a given interface.