Usability Aspects: Interaction Capability, User Experience and Accessibility (ISTQB CTAL-TA)
Overview
In the ISTQB Advanced Level Test Analyst (CTAL-TA) syllabus, usability testing is one of the quality characteristics the Test Analyst is directly responsible for. The syllabus separates usability into three related but distinct aspects: interaction capability (often still called usability), user experience (UX) and accessibility. Exam questions often check whether you can tell these aspects apart, link them to the right standards, and choose suitable test approaches for each one.
Why It Is Important
- Users judge systems by how they feel to use, not only by whether they work. A functionally correct system can still fail in the market if it is confusing, slow to learn or frustrating.
- Business impact: poor usability raises support costs, training costs, error rates and abandonment (for example, shopping carts left unpaid). It also lowers conversion and customer loyalty.
- Legal and regulatory impact: accessibility is legally required in many contexts. Examples include the European Accessibility Act, EN 301 549, Section 508 in the USA, the ADA, and public-sector web accessibility directives. Not complying can lead to lawsuits and fines, or to exclusion from public tenders.
- Ethical and social impact: accessible design includes people with disabilities, older users and people in difficult situations, such as bright sunlight, one hand busy or noisy surroundings.
- Safety: in safety-critical domains such as medical devices, aviation and automotive, poor interaction design causes user errors that can harm people. This makes user error protection a key concern.
- Cost of late defects: usability problems found late are expensive to fix. This is why the syllabus stresses early evaluation, for example reviews of wireframes and prototypes.
What It Is: The Three Aspects
1. Interaction Capability (Usability)
ISO/IEC 25010:2023 renamed the characteristic formerly called usability to interaction capability. It means the degree to which a product or system can be interacted with by specified users, who exchange information through the user interface to complete specific tasks in a variety of contexts of use. The classic definition from ISO 9241-11 is still very useful: the extent to which a system, product or service can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use.
- Effectiveness: accuracy and completeness with which users achieve their goals. Example: the percentage of tasks completed successfully.
- Efficiency: resources spent to achieve the goals. Examples: time, number of clicks, mental effort.
- Satisfaction: how far the user's physical, cognitive and emotional responses meet their needs and expectations. Example: questionnaire scores.
- Context of use: users, goals, tasks, resources and environment (technical, physical, social, organizational).
Sub-characteristics of interaction capability in ISO/IEC 25010:2023:
- Appropriateness recognizability: users can recognize whether the product suits their needs.
- Learnability: users can learn to use it within a specified time.
- Operability: it is easy to operate and control.
- User error protection: it prevents users from making errors and helps them recover.
- User engagement: it presents functions and information in an inviting, motivating way. This replaces the former user interface aesthetics.
- Inclusivity: it can be used by people of various backgrounds, such as different ages, abilities, cultures and languages.
- User assistance: it can be used by people with the widest range of characteristics and capabilities. This is closely tied to accessibility.
- Self-descriptiveness: it presents appropriate information so that its capabilities and use are immediately obvious, without excessive reference to manuals.
Note: the older ISO/IEC 25010:2011 listed accessibility and user interface aesthetics directly as usability sub-characteristics. Be aware of both versions, but the current CTAL-TA syllabus (v4.0) follows the 2023 terminology.
2. User Experience (UX)
ISO 9241-210 defines UX as a user's perceptions and responses that result from the use and/or anticipated use of a system, product or service.
Key points:
- UX is broader than usability. It covers emotions, beliefs, preferences, perceptions, comfort, behaviors and accomplishments.
- UX covers the time before use (expectations, brand image), during use (interaction) and after use (reflection, loyalty, recommending the product to others).
- UX is influenced by brand image, presentation, functionality, system performance, interactive behavior, assistive capabilities, the user's prior experience, attitudes, skills and personality, and the context of use.
- Usability criteria such as effectiveness, efficiency and satisfaction can be used to assess parts of UX. However, UX is more subjective and holistic.
3. Accessibility
Accessibility is the degree to which a product or system can be used by people with the widest range of characteristics and capabilities to achieve a specified goal in a specified context of use. This includes people with visual, auditory, motor, cognitive, speech or age-related impairments, whether permanent, temporary or situational.
The main reference is the Web Content Accessibility Guidelines (WCAG) from the W3C. WCAG is organized around four principles, remembered as POUR:
- Perceivable: for example, text alternatives for images, captions for video, sufficient color contrast.
- Operable: for example, full keyboard access, enough time, no content that triggers seizures, navigability.
- Understandable: for example, readable text, predictable behavior, input assistance and error suggestions.
- Robust: compatible with current and future user agents, including assistive technologies such as screen readers.
WCAG defines conformance levels A (minimum), AA (the usual legal target) and AAA (highest).
Accessibility requirements frequently come from legislation and standards (EN 301 549, Section 508, national laws). This makes them mandatory rather than optional.
How It Works: Testing These Aspects
Planning and context
- Identify the target user groups (personas), their tasks and goals, and the contexts of use.
- Derive measurable usability requirements. Example: 90% of first-time users complete checkout in under 3 minutes without help.
- Identify applicable accessibility standards and the required conformance level.
Formative vs. summative evaluation
- Formative: done early and iteratively during design to find and fix problems. Examples are prototype reviews, heuristic evaluation and think-aloud sessions.
- Summative: done near the end to measure whether the usability requirements are met, typically with metrics and benchmarks.
Typical techniques for interaction capability
- Usability reviews and inspections, including heuristic evaluation against principles such as Nielsen's 10 heuristics or the ISO 9241-110 interaction principles.
- Cognitive walkthrough: stepping through tasks from a new user's perspective.
- Usability testing with representative users: the users perform realistic tasks while being observed. Observers measure task completion, time, errors and help requests, often using the think-aloud protocol. This can be done in a lab, remotely, moderated or unmoderated.
- A/B testing and analysis of logs and analytics in production.
- Test conditions are derived from the sub-characteristics. Examples: Are error messages helpful (user error protection)? Can a novice learn the core task quickly (learnability)?
Typical techniques for UX
- Surveys and questionnaires, such as SUS (System Usability Scale), SUMI, WAMMI, UEQ and NPS.
- Interviews, diaries, long-term studies and emotional response measurement.
- Evaluating expectations before use and impressions after use, not only the interaction itself.
Typical techniques for accessibility
- Static analysis and automated checkers, for example WAVE, axe or Lighthouse. These find issues such as missing alt text or low contrast. They cannot find all issues, so manual evaluation is still needed.
- Manual inspection and reviews against WCAG success criteria.
- Testing with assistive technologies: screen readers (JAWS, NVDA, VoiceOver), magnifiers, voice control, keyboard-only navigation.
- Testing with users who have disabilities.
- Checklists derived from the applicable legal standard.
Role of the Test Analyst
The Test Analyst identifies test conditions, designs usability and accessibility test cases and scenarios, selects or supports appropriate techniques, and helps recruit or define representative users. They record usability defects with clear evidence such as observations, metrics and screenshots, and collaborate with UX designers and specialists. Specialist activities such as advanced UX research may be handled by usability experts. The Test Analyst must understand these activities and contribute to them.
Distinguishing the Three Aspects (Quick Comparison)
- Interaction capability / usability: Can specified users achieve specified goals effectively, efficiently and with satisfaction? It is task-focused and largely measurable.
- UX: What does the user perceive and feel before, during and after use? It is holistic, subjective and covers the whole user journey.
- Accessibility: Can people with the widest range of abilities use it? It is inclusion-focused, often standards-based (WCAG) and legally mandated.
- The three aspects overlap. Good accessibility usually improves usability for everyone, and good usability contributes to good UX. A product can, however, be usable for most people yet inaccessible, or usable yet still deliver a poor UX.
Exam Tips: Answering Questions on Usability Aspects: Interaction Capability, User Experience and Accessibility
1. Know the definitions precisely.
- Usability = effectiveness, efficiency, satisfaction + specified users, goals and context of use. If an option mentions all three criteria in a context of use, it is describing usability.
- UX = perceptions and responses from use and anticipated use. Keywords such as emotions, expectations, before/during/after use, brand, perception point to UX.
- Accessibility = usable by people with the widest range of characteristics and capabilities. Keywords such as disabilities, screen reader, WCAG, color contrast, keyboard-only, legal compliance point to accessibility.
2. Map scenarios to sub-characteristics.
- New employees need hours of training to do a simple task → learnability.
- Users accidentally delete records with no confirmation or undo → user error protection.
- Visitors cannot tell whether the app does what they need → appropriateness recognizability.
- The interface looks dull and fails to motivate users → user engagement.
- Functions are hard to control or operate → operability.
- The meaning of controls is not obvious without a manual → self-descriptiveness.
3. Watch for the 2011 vs. 2023 terminology. If a question uses interaction capability, user engagement, inclusivity or self-descriptiveness, it is following ISO/IEC 25010:2023. Do not reject a correct option just because it uses the new name.
4. Choose techniques that match the goal.
- Early design, finding problems → formative evaluation (heuristic evaluation, prototype reviews, cognitive walkthrough).
- Proving requirements are met → summative evaluation with metrics.
- Measuring satisfaction or UX → questionnaires (SUS, SUMI, WAMMI, UEQ).
- Accessibility compliance → WCAG-based reviews, automated tools plus manual checks and assistive-technology testing.
5. Beware of absolute statements. Options claiming that automated tools can find all accessibility defects, that usability testing must only be done at the end, or that UX is the same as usability are almost always wrong.
6. Remember representative users. Valid usability testing requires users who represent the target groups and realistic tasks in a realistic context. An option using developers or testers as the only test participants for measuring real-user satisfaction is usually a distractor.
7. Recognize the legal angle. If a question mentions government websites, public sector, regulations or contracts, the best answer usually involves accessibility conformance to a standard, typically WCAG level AA or EN 301 549.
8. Read the stem for the timeframe. Words such as anticipated use, first impression, after using or recommend to friends signal UX rather than pure usability.
9. Use elimination. First remove options that describe other quality characteristics. Performance efficiency (response time under load), functional correctness and compatibility can look similar to usability or UX issues. Slow response can affect UX, but if the question asks about the system's measured response time, it is performance.
10. K-level awareness. This topic is typically examined at K2 (understand/distinguish), and test-design applications may be at K3 or K4. Expect scenario-based questions asking you to identify which aspect is being tested or select the most appropriate approach, rather than plain recall.
Summary
Interaction capability is about whether users can achieve their goals effectively, efficiently and with satisfaction. UX is about the whole emotional and perceptual journey before, during and after use. Accessibility is about whether everyone, including people with disabilities, can use the product. To answer exam questions, master the definitions, the ISO/IEC 25010:2023 sub-characteristics, WCAG's POUR principles and the formative/summative techniques. Then carefully match the scenario keywords to the right aspect.
