Operable

Operability of the User Interface

Building ICT content with sound structure ensures the content is navigable and interoperable by a diverse range of individuals and parsers (ex. web browsers), as well as various Human Interface Devices (ex. keyboards, touch displays, refreshable braille displays, joysticks, speech input, and switch inputs).

Guideline 2.1 Keyboard Accessible

Make all functionality available from a keyboard.

As the title of this guideline implies, it is important in ICT accessibility to make all functionality keyboard accessible. Interactive elements like links, buttons, and form elements should be operable by an individual who cannot rely on a mouse. This guideline benefits both the non-sighted user as well as the user with mobility differences.

Back to top


Guideline 2.2 Enough Time

Provide users enough time to read and use content.

This guideline asks developers of ICT to allow for time for individuals to consume content. One aspect is to allow a user to adjust the timing to complete their tasks, and another is to provide a mechanism to turn off distracting elements like videos and animations. 

Back to top


Guideline 2.3 Seizures

Avoid designing content in a way that is known to cause seizures.

This guideline has only one success criteria, but that belies its importance. Flashing content from animations and videos can cause seizures in people with photosensitive epilepsy. This success criteria is written to identify and eliminate seizure-inducing content from ICT.

Back to top


Guideline 2.4 Navigable

Provide ways to help users navigate, find content, and determine where they are.

This guideline contains essential success criteria for users to navigate the user interface of ICT and has a wide range of benefits for vision, mobility, and cognitive differences.

Back to top