An interface reaches people with different devices, abilities, and conditions. Keyboard navigation, readable content, clear structure, and useful alternatives make a service more adaptable.
A new interaction should be considered alongside the ways someone might not be able to use it. Touch, motion, sound, and visual presentation each have limits in some contexts.
Accessibility belongs in the design of the experience, not only its final inspection. Start with the task and test whether it remains understandable through more than one path.
- Try the task with a keyboard.
- Check content without motion or sound.
- Keep a clear alternative to a new interaction.
An example to consider.
A future reading interface might add motion while respecting a reader’s preference to reduce it. Progress includes the conditions that make the experience usable.
Put it in perspective.
The person who maintains an idea may be different from the person who introduces it. Give both perspectives a place in the original decision.
Follow a related question
Write the assumptions beside the calculation.
An estimate with visible assumptionsDistinguish local preferences from account data.
Where a cloud application livesKeep learning
Related background to continue exploring this subject.
W3C: web accessibility W3C: accessibility, usability, and inclusion