Understanding Device Sensor


The intent of this success criterion is to ensure that functions that are triggered by device or user motion can also be operated by user interface components, unless the motion is essential for the function and not using it would invalidate the activity.

Note: This criterion concerns input through sensors which respond directly to motions such as tilting, shaking, or panning. It is not intended to cover indirect motion associated with operating a keyboard, pointer, or assistive technology.

Devices may have sensors that act as inputs, e.g., tilt/orientation or motion sensors on a phone or tablet device, allowing the user to control something by simply changing the orientation or motion of the device in space. Some users with disabilities may not be able to operate these sensors (either not at all or not precisely enough) because the device is affixed to a wheelchair or due to motor impairments. Functionality must therefore be implemented in a way that other means are available to activate the function that do not rely on sensor input.

Some applications are specifically created to use device sensor data. Examples of content that are exempt from this requirement include a pedometer that relies on device motion to count steps.







  • Functionality/content must not solely rely on device inputs (e.g. an alternative which does not require the user to manipulate their device/use these device inputs must be available)



  • Functionality/content solely relies on device inputs (e.g. tilt)