Fundamentals of Ergonomics in Software Development

This article is a definition of terms for software ergonomics fundamentals – including exam questions, core components, and tags.

In a Nutshell

• Usability focuses on effectiveness, efficiency, and satisfaction in task completion.
• User Experience (UX) additionally encompasses expectations, emotions, and context before/during/after use.

Ergonomic UIs emerge through requirements analysis, visual order, accessibility, and iterative validation with mockups/prototypes.

Compact Technical Description

Software ergonomics is based on standards such as ISO 9241 and principles of human-centered design.

• Usability: “Does the user complete the task correctly and quickly?”
• UX: “How does the overall experience feel (including expectation/brand/context)?”

Early visualization:

• Wireframe / Mockup (low/high fidelity)
• Click prototype for flows, feedback, and error scenarios

Accessibility:

• WCAG (POUR: perceivable, operable, understandable, robust)
• EN 301 549 as European framework (e.g., public procurement)

Evaluation:

• Heuristic evaluation (Nielsen)
• Walkthroughs
• User tests

Exam-Relevant Key Points

• Distinguish usability vs UX clearly (IHK)
• Mockup types + benefits (coordination, risk reduction)
• Ergonomics rules: consistency, feedback, error prevention, error tolerance
• Accessibility: contrast, keyboard operability, visible focus
• Form design: grid, grouping, reading order
• Cognitive laws: Fitts, Hick-Hyman (basic idea)
• Document requirements + acceptance criteria testably
• Metrics: Task Success, Time on Task, Error Rate, SUS/UEQ

Core Components

1. Requirements gathering (interviews, observation, personas)
2. Information architecture (navigation, vocabulary)
3. Interaction design (flows, states, errors)
4. Visual design (grid, typography, contrast)
5. Prototyping (wireframe → click model)
6. Accessibility (WCAG, keyboard, semantics)
7. Component library (forms, dialogs, tables)
8. Usability evaluation (tests, SUS/UEQ)
9. QA (acceptance criteria, A11y checks)
10. Governance (style guide/design system)

Practical Example (Support Ticket Form)

Fields: Subject, Description, Category, Priority, Upload
Ergonomics: Grouping, required fields marked, inline validation
A11y: Label->Input, keyboard order logical, focus visible, contrast 4.5:1
Test: 5 users, metrics (success, time, errors, SUS)

Advantages and Disadvantages

Advantages

• Higher task success rate
• Lower support and training costs
• Better accessibility (inclusive products)

Disadvantages

• Initial effort (analysis, prototyping, tests)
• Need for test users
• Target conflicts (branding vs. contrast/A11y)

Typical Exam Questions (with Brief Answer)

1. Usability vs UX? Usability = completing the task; UX = entire user experience.
2. Why mockups early? Make requirements visible, iterate cost-effectively.
3. Important usability metrics? Task Success, Time on Task, Error Rate, SUS/UEQ.
4. Important WCAG aspects for forms? Labels, contrast, keyboard, focus, understandable error messages.

Most Important Sources

1. https://www.w3.org/WAI/standards-guidelines/wcag/
2. https://de.wikipedia.org/wiki/ISO_9241