Pass the ISTQB Usability Testing CT-UT Questions and answers with ExamsMirror

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

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.

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

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.

Conducting user surveys involves a structured approach that ensures data collection is effective, reliable, and meaningful. The process typically starts with writing a survey plan, which defines the objectives, scope, target population, and methodology. Next, interviewing users and stakeholders is important to gather qualitative insights, refine survey questions, and align the survey with business goals and user needs.

Selecting or designing the questionnaire follows, which includes crafting clear, unbiased questions to capture the desired data. After that, deploying the questionnaire to the recruited participants is essential; this can be done via email, online tools, or in-person, depending on the context. Once the data is collected, it must be analyzed to extract meaningful patterns, trends, and insights. Finally, communicating the findings to stakeholders completes the process by informing decision-making.

Other options miss critical steps such as deploying the questionnaire (Option C), or combine steps incorrectly (Options A and D). Importantly, the step of interviewing users and stakeholders prior to deployment ensures the survey is well-informed and targeted, enhancing the quality and relevance of data collected.

At an early development stage where only a rudimentary prototype exists, a usability review (e.g., expert or heuristic review) is the most effective method. It allows usability specialists to identify potential usability issues without the need for a fully functioning product. Reviews can provide immediate, actionable feedback to guide design improvements before moving into more resource-intensive usability testing. An unmoderated usability test (B) or lab test (D) may be impractical at this stage due to limited interactivity. A usability maturity assessment (C) evaluates organizational processes and is not applicable to evaluating a specific prototype.

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.

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.