Usability and Accessibility in Design

Introduction to Usability and Accessibility Principles

• The need for interfaces to be understandable and readable.
    - Navigation: Interfaces should facilitate easy navigation for users of different skills.
    - Robustness: Interfaces should be able to accommodate various technologies, including screen readers.
    - HTML Validity: Importance of valid HTML to prevent unpredictable issues during user interaction.

Spectrum of Accessibility

• Types of Accessibility Needs:
    - Permanent: Long-lasting disabilities (e.g., loss of a limb).
    - Temporary: Short-term disabilities (e.g., a broken limb).
    - Situational: Conditions affecting functionality in certain contexts (e.g., holding a cup, bright sunlight).

• Importance of considering user usability across all the different types of accessibility needs.

Inclusive Design Philosophy

• Definition: Inclusive design as a philosophy that focuses on accommodating multiple user needs in the design process.
• High marks criteria for assessments:
    - Integration of inclusive design concepts with specific scenarios.
    - Meaningful references to the WCAG (Web Content Accessibility Guidelines).
• Mid marks criteria:
    - Basic identification of needs with vague references to guidelines.
    - Lack of specific context in addressing unique user scenarios.
• Low marks criteria:
    - Generic lists that do not engage with the specific question.

Distinction Between Accessibility and Inclusive Design

• Definition of Accessibility:
    - Accessibility focuses on removing barriers specifically for people with disabilities.
    - Often reactive and compliance-oriented due to legal requirements (e.g., WCAG).

• Definition of Inclusive Design:
    - Inclusive Design is proactive and integrates various user profiles including age, literacy, and culture into the design from the beginning.
    - Involves designing with consideration for all users rather than retrofitting solutions for specific groups.

• Importance of understanding both concepts:
    - They intersect but serve different purposes in the design ecosystem.

Interaction Design and Mental Models

• Mental Model in HCI:
    - Definition: A mental model represents users' expectations and understanding of how a system should operate.
    - Example: A typical web navigation bar that organizes links based on user expectations.
• Issues arising from mismatched mental models:
    - Users can become confused and frustrated if a designer's conceptual model differs from their mental model, leading to errors and inefficiencies.
• Strategies for mitigating mismatch:
    - Designers should ensure consistency in design and incorporate user research to align system behavior with user expectations.

Interaction Design Process

• Overview of the Interaction Design Process:
    - Iterative Process: Design must be revisited and revised over time based on new findings and user feedback.
    - Four Key Activities:
      1. Establishing Requirements: Understanding who the users are and their needs.
      2. Generating Multiple Designs: Creating diverse design ideas without committing to one too early.
      3. Prototyping: Transitioning from low-fidelity sketches to high-fidelity clickable prototypes.
      4. Evaluating: Testing the interface with real users to gather feedback and refine the design.
    - Distinction between LDX (Interaction Design) and UI (User Interface) Design.
      - LDX focuses on the overall design process, similar to rehearsals in drama; UI is the final performance.

Ethical Responsibilities in HCI Design

• Overview of ethical responsibilities surrounding personal data collection:
    - Informed Consent: Ensuring users understand what data is collected and why.
    - Transparency: Being clear about data usage policies.
    - Dark Patterns: Designing interfaces that manipulate user behavior in unethical ways, such as pre-ticked boxes on consent forms or creating addictive content.
    - GDPR Compliance: Adhering to data protection regulations by ensuring explicit, granular, and revocable consent from users.
• Example Issues:
    - Data Minimization: Collecting only necessary data to avoid breaches of trust.
    - Algorithm Transparency: Ensuring algorithms are auditable and do not perpetuate bias in outcomes (e.g., biased loan or job recommendations).

Evaluation Methods in HCI

• Two Common Evaluation Methods:
    1. Heuristic Evaluation:
       - Description: Evaluation by experts against established principles (e.g., Nielsen's heuristics).
       - Appropriate Use: Best used early in the design process, allowing for modifications before user testing.
       - Limitation: May result in biased insights, since evaluations reflect expert opinions.
    2. Think Aloud Testing:
       - Description: Users verbalize their thoughts while interacting with the system.
       - Appropriate Use: Effective during prototyping to observe real-time user behavior and barriers encountered.
       - Limitation: May produce unrepresentative behavior as it’s not natural for users to verbalize their actions on the go.
• Other Mentioned Techniques:
    - Cognitive Walkthroughs, AB Testing (Split Testing), SUS (System Usability Scale) questionnaires, analytics-based evaluations.

Final Exam Strategies and Tips

• Time Management: Aim to be halfway through the exam by the midpoint; prioritize questions accordingly to maximize mark potential.
• Concrete Examples: Provide specific instances and details rather than generic statements.
• Structure and Clarity: Ensure clear logical flow in answers, defining terms clearly and drawing connections to real-life applications.
• Stay Updated: Continuous reading and engagement with the subject matter enhances your understanding and performance in assessments, making it crucial for success in higher education.