Skip to content
You are here: Home » Accessibility » Chapter 15 – Principle 2: Operable

Chapter 15 – Principle 2: Operable


Thanks for your interest in the Abra kick-off training about the accessibility of apps. My name is Paul van Workum and I am working in the field of app accessibility.

Principle 2: Operable

Everyone should be able to operate the user interface and navigation components.

Guideline 2.1: Keyboard Accessible

The app must be operable via keyboard or screen reader. Test with both as the screen reader goes to all elements and the keyboard only to elements you can activate. If both keyboard and screen reader work, switch control and voice control also work.

Not being able to use the keyboard interface accounts for 31% of the issues reported by users in our reporting app ‘Inaccessible’.

Guideline 2.2: Enough Time

Users must be able to complete tasks in the time they require. For example users dependent on switch control need this extra time. It should be possible to extend time limits and pause distracting content.

Guideline 2.3: Seizures and Physical Reactions

Never show more than three flashes per second anywhere in an app. This can cause an epileptic seizure.

Guideline 2.4: Navigable<

Ensure assistive technologies use a logical focus order, when navigating. The normal focus order is from left to right, from top to bottom. Except if this influences the meaning of the content. For example, if you have a two column article it is allowed to first share all information in column 1, before going to the next.

Guideline 2.5: Input Modalities

Not all people can zoom by pinching fingers. Provide an alternative for gesture actions , e.g. by providing a button. This is helpful when folks are using a keyboard or screen reader, or in case of motor limitations.