Usability Testing Free Sample Questions

Efficiency, in the context of ISO 9241-11, relates to the resources expended (e.g., time, effort) to achieve a goal. A six-step process that could be three steps is less efficient. Effectiveness is the ability to complete the goal at all, which users could do. Satisfaction relates to the user's feelings about the interaction, which is also impacted but is a consequence of the poor efficiency. Accessibility relates to use by people with disabilities and is not the primary issue described.

Formative evaluation is conducted during the development process to 'form' or guide the design. Its goal is qualitative: to find and fix problems. Summative evaluation is conducted on a mature product to measure or 'sum up' its usability, often against benchmarks, and is quantitative. Accessibility is a type of evaluation, not a stage. Heuristic evaluation is a specific formative method, but 'Formative' is the broader, correct term for this stage and goal.

The scenario describes a technical project risk where the usability evaluation environment (small database, high-end hardware) did not realistically simulate the production environment, leading to missed performance-related usability issues. This is a classic example of an unrealistic test environment. The other options are organizational or supplier risks that are not directly indicated by the scenario's details.

Controllability is the principle that users should be able to initiate and control the direction and pace of the interaction until the point at which they have fulfilled their goal. By reloading the page and losing the user's scroll position, the system is taking control away from the user unexpectedly. While it also violates user expectations, the core issue is the loss of user control over their view state.

According to WCAG 2.1, providing audio description for prerecorded video content is a Level AA success criterion (1.2.5 Audio Description (Prerecorded)). Captions (1.2.2) are required for Level A. Therefore, by having captions but no audio description, the site meets Level A for this aspect but fails to meet the Level AA requirement. The correct statement is that it meets Level A, but the reason given in this option is that audio description is only required for Level AAA, which is incorrect. A better wording is needed. Let's re-evaluate the options. Option A is wrong, audio description is not Level A. Option B is tricky. Let's check WCAG 1.2.5 is AA, and 1.2.8 (Media Alternative) and 1.2.9 (Audio Only) are AAA. So, audio description IS a Level AA requirement. Therefore, the site FAILS Level AA. Option C states it fails Level AA, which is correct. Let's re-read the options carefully. Option B says it MEETS Level AA because audio description is only required for AAA. This is factually incorrect. Option C says it FAILS Level AA. This is correct. Let me fix the correct answer. The question is tricky. Let me re-read the WCAG. Ah, 1.2.3 Audio Description or Media Alternative is Level A, but 1.2.5 Audio Description (Prerecorded) is Level AA. This is a common point of confusion. For Level A, you need either an audio description OR a text transcript. For Level AA, you need the audio description itself. The question states there are captions, but not a full transcript or audio description. This means it fails Level A (1.2.3) and therefore also fails Level AA (1.2.5). Let me re-craft the answer set to be clearer. Okay, let's assume the question implies a full text transcript isn't present either. Then it fails Level A. Let's re-read the standard to be precise. SC 1.2.3 (Level A) requires audio description OR a media alternative. SC 1.2.5 (Level AA) requires audio description. So if a site has no audio description, it fails Level AA. It might pass Level A if it has a full media alternative (like a transcript). The question does not mention a transcript. So it definitely fails AA. Option C is the most accurate. Let me re-evaluate my previous thought. I will re-write my own question to be less ambiguous. New Question: A website aiming for WCAG 2.1 Level AA has a video with synchronized captions but no audio description or full text transcript. What is the status? It fails Level A (SC 1.2.3) and thus fails Level AA. So option C is correct. Let me re-read my original options. Option B is 'meets AA because audio description is AAA'. This is wrong. Option C is 'fails AA because audio description is required for AA'. This is correct. Option D is 'meets A but fails AA'. This would be true if a transcript existed. Since it's not mentioned, we assume it doesn't, so it fails A as well. The most direct failure is the AA one. Option C is the best answer.

The 'Consistency and standards' heuristic states that users should not have to wonder whether different words, situations, or actions mean the same thing. This includes following platform and industry conventions. A non-standard icon for 'next month' and a 'search' action styled as a link instead of a button both violate established web conventions.

The purpose of a pilot session is to check the usability test script and setup. Discovering a show-stopping bug is a valid and important outcome. The correct procedure is to report the bug, get it fixed, and then run another pilot to ensure the script and tasks can be completed before commencing the full test sessions with recruited participants.

For a point-of-sale system in a busy coffee shop, the environmental context is crucial. Realistic background noise and interruptions are key components of that context. Simulating the physical counter setup is also important for ergonomic and workflow evaluation.

A key principle of effective usability reporting is that the report itself must be usable. Reporting too many findings (e.g., all 50 observations) overwhelms stakeholders and reduces the likelihood of action. The moderator's critical task is to prioritize and report only the most important problems, typically limiting the list to around 20-25 findings.

This statement is false. User surveys are used to report subjective evaluations, such as user satisfaction, based on their experience. Observing user behavior and measuring task completion rates are the primary purposes of usability testing, not user surveys.