Accessibility · Applied
Accessible Target Size
Interactive targets need sufficient size and spacing for reliable use.
5 minute field note
Helps create
Fewer input errors
Overview
Make the interface carry more of the effort.
Make controls comfortably operable for people with different motor abilities, devices and contexts.
Human impact
Why it matters
Interactive targets need sufficient size and spacing for reliable use. When the interface does not account for this, people spend effort interpreting the product instead of completing the task. Applied with context, the principle supports fewer input errors without removing meaningful choice or control.
Design hypothesis
If we apply Accessible Target Size to the decision point, people should reach fewer input errors with less avoidable friction.
Mechanism
How it works
Notice where the task currently asks people to wcag or touch without enough support.
Make controls comfortably operable for people with different motor abilities, devices and contexts.
Make the smallest change that should improve fewer input errors, then compare the task before and after.
Try the principle
Same action, different target size
Assign the selected item
Why it helps: larger targets and comfortable spacing make the action easier to acquire.
Decision guide
When to use it
Apply it
Practical checklist
Provide at least a 24 by 24 CSS pixel target or sufficient spacing.
Use larger targets for frequent and important actions.
Avoid overlapping hit areas.
Test targets at mobile widths and zoomed layouts.
Watch for
Common mistakes
Measuring the icon while ignoring the actual hit area.
Packing adjacent actions too tightly.
Using target size as a substitute for clear labeling.
Accessibility considerations
Consider tremor, limited dexterity and one-handed use.
Keep inline text links visually and programmatically distinct.
Evidence plan
How to test it
Combine an objective check with human use.
Check the relevant WCAG success criterion and technique, then complete the real task with keyboard, zoom and an appropriate assistive technology. Automated checks can support this work but cannot prove the whole experience is accessible.
Observe
Whether names, roles, states, focus and recovery remain understandable throughout the task.
Decide
Pass only when the requirement is met and a person can complete the intended task without avoidable loss of information or control.
Use with judgment
Limits and trade-offs
Accessible Target Size is a decision lens, not a universal prescription. Context, frequency, expertise and consequence can change the right implementation.
Optimising only for fewer input errors can create new costs elsewhere. Recheck access, comprehension, user control and business constraints together.
A polished prototype can still fail in real use. Validate consequential decisions with representative people and realistic content.
Design responsibly
Better outcomes must also be honest outcomes.
Use the principle to reduce avoidable effort, not to pressure people into a choice.
Keep price, risk, consent and irreversible consequences visible before commitment.
Record what evidence supports the decision and what remains an assumption.
Evidence
Sources and interpretation
Design principles are lenses, not automatic answers. Apply them in context and validate consequential decisions with users and accessibility testing.
Keep close
Key takeaways
Interactive targets need sufficient size and spacing for reliable use.
Provide at least a 24 by 24 CSS pixel target or sufficient spacing.
Pass only when the requirement is met and a person can complete the intended task without avoidable loss of information or control.