iSQI CTFL-UT ISTQB Certified Tester-Foundation Level - Usability Testing Exam Practice Test

Common mistakes in usability testing include:

Ignoring critical results (ii): A significant issue if findings are not acted upon.

Scheduling the test too late (iv): This can lead to usability problems being discovered too late to be addressed effectively.

Having the wrong focus (v): For instance, focusing on aesthetics instead of usability goals.

Option i ("user is too active") is not a problem—active participation is necessary. Option iii ("no observers involved") is not a typical mistake, since tests can still be valid even with recorded sessions and later review. Hence, the correct answer is A: ii, iv & v are true.

The usability test moderator plays a crucial role during the execution phase of a usability test. Their principal task is to facilitate the test sessions by guiding participants through predefined testing tasks, observing behaviors, and ensuring that the test environment is neutral and free from bias. Defining testing tasks, however, is primarily done during the test design phase by the usability test designer or analyst, but the moderator ensures these tasks are clearly communicated and administered to participants during the session. Logging usability problems (option B) is often done by observers or analysts reviewing session recordings or notes, not directly by the moderator during live testing. Creating a survey plan (option C) and writing the usability test plan (option D) are preparatory activities generally done before the test sessions and are not the moderator's main focus. Therefore, the principal role of the moderator centers on conducting the sessions and managing task delivery effectively to obtain authentic user interaction with the system under test.

The use of HTML tables for layout instead of proper semantic HTML and responsive design violates accessibility guidelines, particularly those defined in the Web Content Accessibility Guidelines (WCAG). Such a design makes it difficult or impossible for users relying on screen readers, keyboard navigation, or other assistive technologies to interact effectively with the site. Therefore, this creates a significant accessibility risk, which is distinct from general usability or user experience risks. Accessibility ensures inclusion of users with physical or cognitive impairments, making option B the correct choice.

A usability test script is a structured document used by the moderator to ensure consistency across test sessions. It typically includes pre-session briefing text, pre- and post-session interview questions, and the specific usability tasks to be performed. However, it does not include answers to the test questions, as usability tests focus on observing user behavior and performance—not testing users’ knowledge. Providing answers would bias results and invalidate findings. Thus, option D is incorrect and the best choice.

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.

A usability test participant is a person selected to represent the target user group and asked to perform specific tasks in a usability test. Their actions, reactions, and feedback help identify usability issues and evaluate the system’s effectiveness, efficiency, and user satisfaction. This role is strictly observational and does not involve organizing, observing, or setting up the test. Options A, B, and C describe other roles (e.g., technical support, observers, or moderators). Only option D accurately reflects the definition of a usability test participant.

The described issue violates the usability heuristic “User control and freedom,” as defined by Jakob Nielsen. This principle emphasizes that users should have the ability to undo and redo actions and navigate freely without being trapped in irreversible sequences. In the scenario, users are forced into the checkout process without a clear way to return or correct mistakes, except through the unreliable and disruptive back button. This design flaw undermines user autonomy and can result in lost progress or frustration.

The usability tester, often synonymous with the usability test moderator in practice, is primarily responsible for interacting directly with the test participants during the usability testing sessions. This role includes communicating with participants to guide them through test tasks, answering questions without leading responses, and ensuring the session runs smoothly. Effective communication is essential to facilitate participant comfort, elicit genuine user behaviors, and capture accurate usability data.

Performing the pre-session briefing (Option A) may be done by the usability tester but is often a shared responsibility or part of test facilitation protocols. Discussing findings (Option C) typically falls to analysts or usability experts after testing sessions are completed and data analyzed. Defining testing tasks (Option D) is usually done by test designers or analysts during test planning, not during the test execution.

Therefore, communicating with test participants during testing is a core, principal task of the usability tester role.

Positive usability findings play a key role in reinforcing what is working well in the user interface. They help:

A: Build developer confidence and soften criticism when pointing out issues.

C: Provide a complete picture of usability strengths and weaknesses.

D: Inform developers what should remain unchanged during redesign.

However, B is incorrect because justifying usability test costs should not rely solely on positive findings. Cost justification should come from the overall impact of usability on user satisfaction, performance, and business outcomes—not just good results.

Moderating the usability test is a core activity during the actual usability test session. The moderator guides participants through tasks, ensures the session stays on track, and avoids introducing bias. Option A (testing the setup) happens before the session, during preparation. Option C (extracting findings) occurs during analysis, after the test. Option D (talking during task execution) should be minimized unless necessary, to avoid influencing user behavior. Therefore, option B is the only correct answer aligned with best practices in usability testing.

Option B represents a realistic, goal-oriented scenario that reflects how an actual user would interact with the website. It incorporates context, user intent, constraints, and desired outcome—all characteristics of well-designed usability tasks. Option A is vague and lacks real-world motivation. Option C is too prescriptive and limits insight into user behavior, while D is a survey question, not a usability task. According to Nielsen Norman Group and ISO 25062, the best usability tasks are scenario-based, realistic, and outcome-driven—making B the correct answer.

The Web Content Accessibility Guidelines (WCAG) provide standards to ensure websites are accessible to people with disabilities. They specifically address:

i. Text resizability (SC 1.4.4),

iii. Text alternatives for non-text content (SC 1.1.1),

iv. Keyboard accessibility (SC 2.1.1),

v. Device independence, which includes not relying solely on mouse input.

Visually appealing design (ii) is not an accessibility requirement and is thus not a WCAG focus. The correct answer is D: i, iii, iv & v are true; ii is false.