Physical disabilities 101
Understand common access needs for people with physical disabilities.
What this helps you understand
Physical disabilities can affect movement, muscular control, energy, coordination, or pain.
Some physical disabilities are permanent. Others may be temporary. People with physical disabilities may use different tools to access websites and apps, including switch systems, one-handed keyboards, head mice, voice control, and dictation tools.
Why this matters
People rarely use one access tool for every task.
A person may use voice recognition for writing, a mouse for some interface controls, and a keyboard when voice control does not work well. Digital experiences need to support flexible ways of interacting.
When to use this guidance
Use this guidance when you are:
- Designing websites, apps, or digital workflows
- Writing user journeys for accessibility research
- Preparing for moderated sessions with people with physical disabilities
- Reviewing keyboard access, focus states, forms, and time limits
- Testing experiences that may require precise pointer control
Recommended approach
Design for flexibility.
Do not assume every user can rely on a mouse, keyboard, touch gesture, or voice command alone. Support multiple input methods and make each interaction clear, predictable, and forgiving.
Best practices
Make all controls keyboard accessible
What to do:
Ensure users can reach and activate all controls without a mouse.
Why it matters:
Many people with physical disabilities use alternative input methods. These methods often depend on keyboard access.
Example:
A user should be able to complete a form, open a menu, select options, and submit information with keyboard commands or keyboard-compatible tools.
Give users enough time
What to do:
Avoid short time limits. When timing is required, let users extend, restart, or continue without losing their work.
Why it matters:
Some users may take longer to complete tasks. Losing progress can make a task frustrating or impossible.
Example:
If a session expires, let the user return to the same point instead of starting over.
Use clear focus indicators
What to do:
Make the currently focused element visually clear.
Why it matters:
Focus indicators help users understand where they are and what control they are interacting with.
Example:
Use a visible focus outline around links, buttons, and form fields.
Use large, forgiving targets
What to do:
Make buttons, links, and controls easy to select.
Why it matters:
Small targets and hover-only areas can be difficult for users with limited coordination or fatigue.
Example:
Avoid tiny controls that require precise pointer movement.
Label controls clearly
What to do:
Use labels and alt text that match what users can see and what they may say with voice control.
Why it matters:
Voice control users need predictable labels to activate controls successfully.
Example:
If a visible button says “Submit,” the accessible name should also communicate “Submit.”
Common mistakes to avoid
Avoid: Designing mouse-only interactions.
Why: Some users cannot use a mouse.
Do this instead: Support keyboard access and alternative input methods.
Avoid: Creating long, complex research journeys.
Why: Tasks may take longer for users with physical disabilities.
Do this instead: Split journeys into shorter tasks.
Avoid: Assuming assistive tools will appear clearly during screen sharing.
Why: Some virtual keyboards or assistive software elements may not show up visually in Zoom.
Do this instead: Ask the participant what you should expect during the session.
Examples
During meetings or research sessions:
- Account for extra time.
- Expect some software to run slower during screen sharing.
- Be mindful of energy levels.
- Consider several shorter sessions instead of one long session.
- Confirm keyboard access and labels before testing.
What to do next
Before testing with people who use alternative input methods, review your journey for keyboard access, labelled controls, timing limits, and target size.