ISTQB CT-UT Dumps

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.

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.

Usability labs provide a controlled environment that offers several advantages for observing and recording usability test sessions. Specifically, they allow for easy observation of participants (ii), standardized conditions for each session (iv), and facilitate audio and video recording for detailed analysis (v). However, the context is not natural (i), because the lab is an artificial setting rather than the user’s actual environment. Also, setting up a professional usability lab is not inexpensive (iii); it typically involves significant costs for equipment, space, and staffing. Therefore, options ii, iv, and v are true, while i and iii are false.

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.

Human-centered design, as defined by ISO 9241-210, emphasizes early user involvement, iterative design, and continuous usability evaluation. Option D aligns with this model as it begins with understanding user needs (interview users), proceeds through iterative prototyping (which allows for continuous improvement), and involves user evaluation. This ensures that the final product is shaped by real user input and feedback. Options A and B lack iteration and continuous evaluation, while option C, although partially aligned, lacks explicit user involvement in the evaluation process, focusing only on expert reviews.

To prevent usability testing from exceeding budget, active monitoring and control of project resources are critical. The best practice is to regularly check consumed time, costs, and effort against the original estimates, allowing timely adjustments to scope or resources. This is a classic quality control practice aligned with ISO 9001 principles and standard project management methodologies. Option A relates to test preparation, option C concerns reporting and communication, and option D applies after test execution. Only option B deals directly with budget control during the test.

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.

The Equality Act 2010 (UK) is legislation designed to protect individuals from discrimination in various areas, including employment and access to goods and services—this includes digital products like websites. While it does not directly mandate WCAG compliance levels (A or AA), it implies that digital services must be accessible to users with disabilities. Organizations are required to make "reasonable adjustments" to avoid discrimination. Therefore, the most accurate and comprehensive answer is B.

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.

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 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 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.