Skip to main content

2.5 Input Modalities

Make it easier for users to operate functionality through various inputs beyond keyboard.

WCAG 2.2, Guideline 2.5
Various input methods: Braille display, touchscreen, keyboard, and user with headset for voice commands.

What is it?

The input modalities standards ensure you don’t force users to use complex gestures or a single specific device to interact with your content.

Why does this matter?

This standard is especially important for users with motor impairments, those who use assistive technologies (like eye-gaze or head-pointers), and anyone using a touchscreen device.

How do I ensure my content complies with input modalities?

  • Simplify Gestures: Decide if you need to use a complex feature like “drag-and-drop” in your content. If you do, ensure there’s a simple, single-click/tap alternative.
  • Target Size: Ensure your designs have enough visual space (padding) around interactive elements like buttons, icons, and links to make them easy to accurately select on any device.
  • Clear Labels: Verify that all your interactive elements have clear, visible text labels that exactly match the name announced for assistive technology.
  • Work with Developers: You won’t control everything, but you can alert developers when controls rely on motion or complex pointer actions (e.g., swiping/pinching) or if accidental activation (pointer cancellation) is an issue.

Bottom line…

Avoid complex gestures and ensure all interactive targets are large enough and clearly labeled for every user.