Principle 2

Operable

Users must be able to operate apps with the technologies they use. Ensure functionality is not only operable via touch. People who use a screen reader, voice control, switch control, external keyboard or other assistive technologies should also be able to operate apps.

Examples

• An app should be operable in multiples ways, including with a screen reader, voice control, keyboard access and switch control.

• People with disabilities sometimes need more time to navigate through a screen. It is important that the time limits can be extended.

• Some users have mobility impairments, preventing them being able to shake their phone. Make sure that this kind of functionality can also be activated in other ways.

Guidelines

• 

  Keyboard Accessible

  All functionality must be usable with assistive technologies.

  Guideline 2.1 - Keyboard Accessible
• 

  Enough Time

  Users should have enough time to complete tasks, especially when using assistive technologies.

  Guideline 2.2 - Enough Time
• 

  Seizures and Physical Reactions

  Apps should be safe for everyone to use. Some people can have a seizure because of flashing images.

  Guideline 2.3 - Seizures and Physical Reactions
• 

  Navigable

  Users must be able to navigate to the information they are looking for.

  Guideline 2.4 - Navigable
• 

  Input Modalities

  All forms of input should be possible for everyone, including those using assistive technologies.

  Guideline 2.5 - Input Modalities

Resources

• WCAG 2.2 - Principle 2 - Operable