user interface
Let an agent handle user interfaces by type, design principles, accessibility, usability testing and safety.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify
Researched by: Claude
Purpose and description
Let an agent handle user interfaces by type, design principles, accessibility, usability testing and safety.
The means by which people interact with a machine, device or system, including software screens, voice and gesture interfaces, and physical controls such as buttons, handles and game controllers.
What it is for: Letting people operate systems effectively, safely and inclusively.
It can be design usable interfaces; check accessibility; test with users; avoid deceptive design.
Distinguishing features
Point of human-machine interaction
Digital or physical
Usability and accessibility matter
Design shapes behaviour
What it looks like
Screens, menus, buttons, knobs, touch surfaces and voice prompts.
How it is recognised
Graphical, voice and physical interfaces
Controls such as buttons and sliders
Handrails and barres in the registry are physical aids, loosely related
Related models
is a kind of - category
is designed by - practice
is evaluated by - method
must meet - requirements
In practice
Families and kinds
graphical user interfaces
command-line interfaces
voice and conversational interfaces
physical controls
game controllers
Standards and regulation
WCAG 2.2
ISO 9241 ergonomics of human-system interaction
EU Accessibility Act
Rules on dark patterns (e.g. EU Digital Services Act)
Failure modes and hazards
Inaccessible interfaces
Confusing controls causing errors
Deceptive dark patterns
Also called
+240
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 4 bundles · 8 layers · 8 findings · 16 questions.
Type Which interface.
Type shapes design.
Kind
Graphical, voice, physical.
Kind
Interface type.
- What kind of interface is it? definition
- Who are its users? definition
Controls
Elements.
Controls
Controls.
- Which controls does it use? definition
- Are they consistent with conventions? boundary
Usability Ease of use.
Usability must be tested.
Testing
With users.
Testing
Usability testing.
- Has the interface been tested with representative users? provenance
- What did testing find? provenance
Errors
Prevention.
Errors
Error prevention.
- How does the interface prevent and recover from errors? definition
- Are critical actions confirmed? boundary
Accessibility Inclusion.
Interfaces must be accessible.
Conformance
WCAG.
Conformance
Accessibility conformance.
- Does it meet WCAG or equivalent requirements? boundary
- Which level? measurement
Assistive tech
Compatibility.
Assistive
Assistive technology.
- Does it work with screen readers, switches and voice control? boundary
- Was it tested? provenance
Ethics Honest design.
Design should not deceive.
Dark patterns
Deception.
Dark patterns
Deceptive design.
- Does the interface use deceptive patterns? boundary
- Which rules prohibit them? provenance
Safety
Critical systems.
Safety
Safety-critical interfaces.
- Is the interface safety-critical, such as in medical or vehicle systems? boundary
- Which standards apply? provenance
What the second pass must settle
- Should interface types be separate entries?
- How should accessibility conformance be recorded?
- How should physical aids be split off?