# Motor Impairments: Using the Web Without a Mouse

Source: https://allyway.ai/glossary/motor-impairments

Motor impairments, also called physical or motor disabilities, are conditions that limit movement, muscle control, sensation or dexterity. People with motor impairments often use the web without a standard mouse – with a keyboard, switches, speech recognition, eye tracking or a head pointer.

Motor impairments change how people control a computer or phone, not what they can understand. Someone with a tremor, arthritis or a spinal cord injury may never touch a mouse, press only one key at a time or steer the screen with their voice. A website that works only with precise mouse movements locks them out – even when every word on it is perfectly clear.

## What it means

W3C's page on [physical disabilities](https://www.w3.org/WAI/people-use-web/abilities-barriers/physical/) – also called motor disabilities – lists weakness and limited muscle control, limited sensation, joint disorders, pain that limits movement and missing limbs. Named conditions include amputation, arthritis, fibromyalgia, multiple sclerosis, muscular dystrophy, repetitive stress injury (RSI), tremor and spasms, quadriplegia and seizure disorders. Many motor impairments are temporary – a broken arm counts too.

People use many kinds of [assistive technology](https://allyway.ai/glossary/assistive-technology): ergonomic keyboards and mice, head pointers and mouth sticks, on-screen keyboards with trackballs or joysticks, [switches](https://allyway.ai/glossary/switch-control) operated by foot, shoulder or sip-and-puff, [voice control](https://allyway.ai/glossary/voice-control) and eye tracking. Almost all of them work through keyboard commands – which is why full keyboard support is the single most important requirement.

| Barrier (W3C) | WCAG criterion | Level |
|---|---|---|
| Functions that need a mouse – see [keyboard navigation](https://allyway.ai/glossary/keyboard-navigation) | 2.1.1 Keyboard | A |
| Time limits too short to fill in a form | 2.2.1 Timing Adjustable | A |
| Swipe, pinch or multi-finger gestures with no simple alternative | 2.5.1 Pointer Gestures | A |
| Drag and drop without a single-click alternative | 2.5.7 Dragging Movements | AA |
| Tiny, crowded buttons – see [target size](https://allyway.ai/glossary/target-size) | 2.5.8 Target Size (Minimum) | AA |
| Missing structure and navigation aids that would save keystrokes | 2.4.1 Bypass Blocks | A |

> **Tip:** > **Every keystroke counts**
> For a switch user, each Tab press can take seconds. A [skip link](https://allyway.ai/glossary/skip-link), a sensible [focus order](https://allyway.ai/glossary/focus-order) and short forms save real effort – not just a little convenience.

## Examples

```html title="Example"
<!-- Inaccessible: drag-only slider, tiny icon, no keyboard support -->
<div class="price-slider" onmousedown="startDrag(event)"></div>
<span class="close" onclick="closeDialog()">×</span>

<!-- Accessible: native range input and a real button with enough size -->
<label for="max-price">Maximum price</label>
<input type="range" id="max-price" min="0" max="500" step="10">
<button type="button" class="close" aria-label="Close dialog"
  style="min-width: 24px; min-height: 24px">×</button>
```

The native `input type="range"` works with arrow keys, a click and voice commands. The `button` element is reachable with Tab and activates with Enter or Space, and at 24 by 24 CSS pixels it meets the Level AA minimum.

**Do:** Do

Make everything work with the keyboard, show a clear focus indicator, give touch and click targets room, offer single-tap alternatives to drag and swipe, let users extend time limits and save form progress.

**Don't:** Don't

Build controls from `div` elements with mouse events, require drag and drop or long presses, place small links tightly together, log people out after a short idle time or hide functions behind hover-only menus.

## How to check your site for motor impairments



## Questions

Q: How do people with motor impairments use a computer?
A: With the tools that suit their body: a keyboard or on-screen keyboard, one or more switches, speech recognition, eye tracking, a head pointer or a mouth stick. Most of these send keyboard commands to the browser.

Q: What is the most important WCAG rule for motor impairments?
A: Keyboard access, criterion 2.1.1 at Level A. If every function works with the keyboard, switches, voice control and on-screen keyboards usually work as well.

Q: Why do small buttons cause problems?
A: People with tremor or limited dexterity often miss small targets and hit the neighboring link instead. WCAG 2.2 sets a minimum of 24 by 24 CSS pixels or enough spacing at Level AA.

Q: Do time limits affect people with motor impairments?
A: Yes. Typing with a switch or a mouth stick takes much longer. WCAG 2.2.1 requires that users can turn off, adjust or extend most time limits.
