Free iSQI CTFL-UT Practice Exam with Questions & Answers

In usability evaluations, a distinction is made between actual usability problems (where a user struggles to complete a task or is confused by the interface) and suggestions or ideas that users provide based on their preferences or perceived improvements. When a participant offers a new feature idea (such as a quick search box), this is classified as a “good idea” or “feature suggestion,” not necessarily a usability problem. It may inform future design enhancements but does not indicate a failure in usability for existing functionality.

The System Usability Scale (SUS) is a standardized, reliable tool used to measure perceived usability. It consists of 10 items with five response options (from strongly agree to strongly disagree). It is widely used due to its simplicity and effectiveness in providing a single score to reflect a user’s overall satisfaction with a system. Option A refers to ISO's definition of usability testing, B describes a task in usability testing, and D refers to a usability requirement, not SUS. Therefore, the correct description of SUS is option C.

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.

Usability reviews evaluate a system or interface against established usability principles or standards to identify potential issues before user testing. A recognized criterion for such reviews includes adherence to usability standards such as ISO 9241 or the Web Content Accessibility Guidelines (WCAG). These standards are derived from years of research and user-centered design principles. Options A and C do not directly relate to usability. Functional requirements (option B) refer to what the system should do, not how usable it is. Hence, option D is correct as usability standards provide a consistent, objective basis for evaluating usability.

The human-centered design process emphasizes iterative development—testing and refining designs through multiple cycles. In the scenario, the project manager interviewed users and evaluated a prototype but did not iterate based on feedback. Skipping iteration likely resulted in unmet user needs. Human-centered design, per ISO 9241-210, includes: understanding context of use, specifying requirements, producing design solutions, and evaluating—repeated iteratively. Hence, option D (“iterate”) is correct.

The scenario describes a situation where the interface misleads users into making serious financial mistakes due to poor design, such as confusing decimal separators. Even though the system functions correctly, it facilitates critical user errors. This constitutes a major usability risk with potential legal and financial consequences. Therefore, the correct risk to address is increased liability due to financial loss caused by a poorly designed or deceptive interface (option D). The other options focus on usability-related dissatisfaction, resistance, or lack of adoption, which are not the key concern in this scenario.

A usability requirement specifies how usable a product or component must be, often in terms of effectiveness, efficiency, and user satisfaction, as defined in ISO 9241-11. These requirements ensure that the product meets specific human-centered design goals, such as allowing users to complete tasks accurately and quickly. Options A and C describe procedural or test setup elements, not actual usability requirements. Option B refers to personnel qualifications, which are not the same as usability requirements related to system behavior or performance.

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.

When a customer emphasizes the importance of accessibility, it means they are concerned with ensuring that users with disabilities or limitations are not excluded from using their products or services. Accessibility is about inclusiveness—providing equal access and opportunity to all users regardless of physical or cognitive ability. Option C directly reflects this understanding. The other options (A, B, and D) are aspects of usability or development methodologies but do not relate to addressing the needs of users with disabilities, which is the core focus of accessibility.

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.