If an interface is easy and useful for someone with a disability, it's usually easy and useful for everyone. That's the whole case for accessibility.
Accessible interfaces and assistive technology are core to UX, especially for Universal Design. Start with UX research and involve users with disabilities early, so problems surface before they’re costly to fix. Follow WAI-ARIA (often enough on its own), and don’t single people out with ‘special treatment’. Practically: assume limitations (one hand, no shortcuts), avoid double-clicks and timed actions, make targets large and easy to hit, and account for vision and color impairments. The guiding idea is ‘one-size-fits-one’ flexible design over rigid ‘one-size-fits-all’, framed by the social model of disability: accessibility means removing the mismatch between a user’s needs and the design.
Key takeaways
- Involve real users with disabilities early; their input prevents costly redesigns.
- WAI-ARIA guidelines are usually sufficient; don't single users out with special treatment.
- Assume limitations: one-handed use, no keyboard shortcuts, motor or vision impairments.
- Avoid double-clicking and timing-based actions; use large, easy-to-target elements.
- Design 'one-size-fits-one' (flexible), not 'one-size-fits-all', and never exclusionary.
- Accessible for one usually means better for everyone.
Practical interface rules
| Rule | What to do | Helps with |
|---|---|---|
| Assume limitations | Design as if users may not have two hands or keyboard shortcuts (e.g. a trackball in the non-dominant hand). | Motor |
| No double-click or timed actions | Avoid interactions that require double-clicking or fast timing; keep them simple and forgiving. | Motor / cognitive |
| Large, easy targets | Make inputs and controls big and easy to hit, critical for motor and vision impairments. | Motor / vision |
| Account for vision and color | Design for low-vision and colorblind users; don’t rely on color alone. | Vision |
| Test with real tools and users | Combine multiple accessibility testing tools across devices, and validate with disabled users. | All |
Principles of inclusive, accessible design
Beyond the interface mechanics, inclusive design rests on a few durable principles: prefer ‘one-size-fits-one’ flexible solutions that adapt to context, but avoid segregated or exclusionary designs and adaptive systems that decide for the user. Respect the user’s dignity, autonomy and self-determination. Design from ‘extreme users’ (people with disabilities and special needs) outward, work in diverse, inclusive teams with accessible tools, and stay socially conscious of the wider impact. Crucially, adopt the social model of disability: disability is a mismatch between a person’s needs and the design of a product or service, so accessibility means eliminating that mismatch. Plan early, test carefully, and engage stakeholders and co-designers with lived experience of the relevant disabilities.
If an app is easy and useful for someone regardless of their impairments, it will likely be easy and useful for everyone.
On why accessibility helps all users
For neurological conditions specifically, see the companion guide, better UIs for Alzheimer’s, dementia and Parkinson’s. Note that conditions like Parkinson’s are often better served by specialized peripherals than by bespoke UI changes, with WAI-ARIA covering the rest.
Start with UX research and real users with disabilities, follow WAI-ARIA, avoid double-clicks and timed actions, use large easy targets, and account for vision and color impairments.
The W3C’s Accessible Rich Internet Applications guidelines. Following them is usually sufficient to make an interface accessible for most needs.
Flexible interfaces that adapt to individual users and contexts, as opposed to rigid ‘one-size-fits-all’ or segregated, exclusionary solutions.
The view that disability is a mismatch between a person’s needs and the design of a product or service. Accessibility means removing that mismatch.
Their feedback surfaces real problems before launch, preventing costly redesigns, and ensures the design meets their actual goals rather than assumptions.
Need genuinely accessible interfaces? Talk to Dorve.
Start a project