CTFL-UT Sample Questions Answers

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.

A best practice in usability reporting (based on ISO/IEC 25062:2006 – Common Industry Format for usability test reports) is to include a clear description of the evaluation method used. This includes how the test was designed, how participants were selected, what tasks were performed, and under what conditions the test was conducted. This ensures the results are credible and reproducible. The provided structure omits this essential information. While the report length is not excessive and positive findings may or may not be present, the key missing component is the method description.

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.

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.

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.

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.

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.

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.

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.