Free and Premium iSQI CTFL-UT Dumps Questions Answers

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.

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.

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.

Formative usability evaluation is conducted during the development process to identify usability problems and improve the product iteratively. It is diagnostic and improvement-focused. Summative evaluation, on the other hand, is done after development to assess the final product’s usability, measuring how well it meets defined usability goals. Therefore, the correct distinction is that formative evaluation focuses on improvement, and summative evaluation assesses the outcome. This distinction aligns with widely accepted models such as those defined by ISO 9241-210 and usability.gov.

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.

An informal usability review can be conducted by anyone, including stakeholders or developers, and does not require formal usability training or qualifications. It is typically subjective and based on general impressions. In contrast, an expert usability review (also called heuristic evaluation) is conducted by a trained usability expert who applies recognized usability principles. This is what differentiates the two approaches most clearly. Options A and C are misleading; expert reviews can be informal in format, and informal reviews aren't necessarily based solely on opinion. Option D is incorrect since both informal and expert reviews can be conducted individually or in groups.

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.

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.

SUS (System Usability Scale), SUMI (Software Usability Measurement Inventory), and WAMMI (Website Analysis and Measurement Inventory) are all validated, standardized usability questionnaires that support benchmarking. They allow comparison against known usability scores from a wide variety of systems. These instruments provide numeric scores that can be interpreted using benchmark datasets or industry standards. Therefore, all three—i, ii, and iii—are true, making D the correct answer.

A usability test plan is a foundational document created before conducting usability testing. It outlines the objectives, scope, methodology, participants, tasks, and schedule for the testing activities. One of its essential components is the schedule, which details when and how test sessions will occur to ensure proper resource allocation and time management. Including a schedule helps coordinate between test moderators, participants, observers, and stakeholders, making the testing process organized and efficient.

While briefing instructions (Option B) may be related to the usability test, they are typically documented separately or included in participant materials rather than the formal test plan itself. The test plan should be concise and focused; it need not be overly elaborate or lengthy (Option C), as clarity and usability of the plan are more important than length. The results of the test sessions (Option D) are not included in the test plan but rather compiled afterward in a test report or analysis document.

Therefore, the correct statement is that the usability test plan contains a schedule, ensuring a structured timeline for the usability testing activities.

A usability test task is a clearly defined activity that a participant is asked to perform during a usability test session. These tasks are typically created by the test designer or moderator and are designed to reflect realistic user goals (e.g., “Find and buy a product”). The purpose is to observe the participant’s interaction with the system and identify usability issues. Option A describes a usability test script, not a task. Option C defines usability evaluation in general, and D refers to a session, not a specific task. Therefore, B is correct.

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.