A pilot usability test session is a critical step prior to conducting the actual usability test. Its purpose is to ensure that the test setup, task design, and moderator instructions are clear and function as expected. According to ISO 9241-210 and the Nielsen Norman Group's best practices, pilot testing helps detect unforeseen issues and fine-tune the process. Options A and B are incorrect because testing conditions must reflect realistic scenarios, and thorough preparation is essential to gather meaningful usability data. Option D is also incorrect; a usability test typically consists of multiple sessions with different users to gather sufficient data for analysis. The pilot session ensures everything works smoothly before involving real participants.
[References:, , ISO 9241-210:2019, Ergonomics of human-system interaction – Human-centred design, , Nielsen Norman Group: Usability Testing 101, , Usability.gov: Pilot Testing, , ‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾, ]
Question 2
What is good accessibility?
Options:
A.
Good usability regardless of disturbances like bright sunlight, noise or wind
B.
Good usability of a software product on all devices (smart phone, computer, etc.)
C.
Good usability of a software product by people with limited knowledge of the software
D.
Good usability of a software product by people with limited vision, hearing, dexterity, cognition or physical mobility
Answer:
D
Explanation:
Accessibility refers to designing products so that people with disabilities or limitations (permanent or temporary) can use them effectively. According to the Web Content Accessibility Guidelines (WCAG) and ISO standards, accessibility focuses on ensuring that users with vision, hearing, cognitive, or mobility impairments can access digital interfaces. Option D captures this intent accurately. The other options relate to general usability or responsiveness (e.g., device adaptability or user experience in noisy environments) but do not address the inclusive nature of accessibility as defined by official guidelines.
You’re asked to evaluate the direct interaction between ordinary users and the software product. Which kinds of evaluations would be suited for that?
Options:
A.
Accessibility evaluation
B.
Usability maturity assessment
C.
Risk assessment
D.
Usability evaluation
Answer:
D
Explanation:
A usability evaluation is specifically designed to assess how real users interact with a software product. It focuses on effectiveness, efficiency, and user satisfaction in completing tasks. This may involve usability testing, expert reviews, or heuristic evaluations. The goal is to identify any usability problems and understand user behavior during real use.
Option A (Accessibility evaluation) targets inclusivity for users with disabilities, not general user interaction. Option B (Usability maturity assessment) evaluates the organization’s usability practices, and Option C (Risk assessment) evaluates potential project or system risks. Only option D directly involves observing and measuring user interaction.
[References:, , ISO 9241-11:2018 – Usability Definitions and Concepts, , Usability.gov: Usability Evaluation Basics, , Nielsen Norman Group: Types of Usability Evaluations, , ‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾, ]