Which guideline describes when and how help and documentation should be provided?

• A. Aesthetic design
• B. Error prevention
• C. Visibility of system status
• D. Help and documentation

Answer: (D)

Help and documentation focuses on providing assistance that users can actually use when they’re tackling tasks or recovering from uncertainties. The idea is to make help available where it’s needed, with concise, task-oriented guidance, and options like context‑sensitive tips, inline tooltips, tutorials, and a searchable help center so users can find exactly what they need without breaking their workflow. This approach ensures users can complete tasks and understand features even if they’re not obvious at first glance. Other guidelines address different aspects of design—aesthetic design for look and feel, error prevention for avoiding mistakes, and visibility of system status for feedback on what the system is doing—but they don’t specifically govern how help content should be presented or accessed.