What is the role of 'help and documentation' in UI usability, and when should it be provided?

• A. Accessible, task-specific help when users need it; not to overwhelm primary interface.
• B. Should always be on screen
• C. Should replace on-screen controls
• D. Should never be consulted

Answer: (A)

Help and documentation should be accessible on demand and tailored to the task at hand. In practice that means providing context-sensitive guidance—like tooltips, inline hints, short how-to tips, and a searchable help center—so users get help exactly where and when they need it without cluttering the main interface. This approach keeps the interface clean while still offering support to complete tasks, learn the UI, and recover from mistakes.

Think of it as a lightweight safety net that supports learning and performance. It should appear when users encounter unfamiliar controls or workflows and should be easy to dismiss or hide when not needed. For more detail, users can access deeper documentation, but the default should be concise, actionable guidance that aids progress.

If help were always on screen, the UI would feel crowded and distracting. If help were meant to replace on-screen controls, users would lose the directness and efficiency of interacting with the UI itself. If users never consulted help, they’d miss valuable guidance that could prevent errors and speed up learning.