Haptics as an accessibility channel

Make the information survive without touch

A haptic can reinforce a result when sound is off or someone’s attention is away from the screen. It can also go unnoticed: the device may be on a table, the hardware may not support the effect, or the person may not perceive or want it.

Begin with the information, then provide appropriate ways to receive it. A vibration indicating a failed save is incomplete unless the app also explains that the document remains unsaved and offers a recovery path. Apple’s feedback guidance calls for communicating through multiple forms of feedback. Feedback guidance

Design one event across channels

For each important event, write down its meaning, its visual state, its accessible representation and any sound or haptic. The forms do not need to be literal copies. They need to communicate the same result.

Do not rely on colour alone for the visual version. Do not assume a sound is always audible. Do not assume an automatic announcement is appropriate for every small change; test the reading experience and avoid flooding it with repetitive updates.

Apple’s accessibility guidance includes pairing audio cues with matching haptics. That is a useful complement, not evidence that any chosen vibration will be understood by everyone. Accessibility guidance

Keep the vocabulary learnable

Start with a few meaningful cues and show their context clearly. A person should not have to memorise a private tactile alphabet before they can use the app.

When comparing candidate cues, vary one feature at a time. For example, compare two rhythms at a comfortable strength before also changing their sharpness. Ask participants what they noticed and what they thought it meant. Do not tell them the intended answer first and then treat recognition as established.

A cue that is distinguishable in a quiet test may be difficult to identify during a busy task. Revisit it in context, including repeated use. A haptic design system provides a place to record those findings alongside the implementation.

Offer control without removing information

Give haptics a clear setting and make the off state work throughout the app. If you offer reduced strength, label it as a preference rather than a guarantee of comfort. The same setting can feel different across devices and people.

Test the app’s preference and relevant system settings on the OS versions you support. Do not infer every third-party Core Haptics behaviour from a setting’s name. Keep the operation and its visible result independent of whether the haptic plays. Apple’s haptic guidance explicitly calls for making feedback optional. Optional haptics

Make the design surface accessible too

A waveform picture does not explain itself to someone who cannot see it. Expose the information it represents: timing, event names, values and selection. Provide editable controls rather than making a tiny point on a canvas the only route to a value.

Haptrix’s feel view supplies an accessible chart representation of intensity over time. VoiceOver’s audio graph is another representation of that chart; it is not a recording of the physical haptic. Apple’s Audio Graphs API lets apps describe chart data so VoiceOver can turn its structure into sound. Audio graphs

For article illustrations, a useful caption or alternative description should name the important change: “three pairs of taps, each second tap softer,” rather than just “waveform.” Downloadable examples should also have a written description.

Test with people and with channels removed

Include people with different hearing, vision and tactile experiences in the design process. Agree on comfortable testing conditions, explain how to stop, and compensate participants for their time. The checklist below is a starting point for a usability session, not a substitute for specialist review.

1. Ask the person to complete a real task without explaining the cue’s intended meaning.
2. Ask what told them the task succeeded or failed.
3. Repeat with haptics disabled. Check that the information and recovery path remain available.
4. Where comfortable and appropriate, repeat with sound disabled and with assistive technology they normally use.
5. Ask which feedback they would keep, reduce or remove.

Also test with no supported haptic device. An iPad can use a connected haptic-capable controller even though built-in Core Haptics output is unavailable; query the output you actually intend to use. Preparing device output, controller output

The result to look for is successful understanding and control across those conditions. More vibration is not, by itself, a measure of accessibility.