Context of use includes device, physical environment, and social environment—not just the interface

What it is

In the standard, "context of use" is not backdrop but a three-part structure: equipment and systems (hardware, network, interoperating systems), the physical environment (light, noise, mobility, one-handed use), and the social environment (others present, organizational rules, motivational pressure). A usability judgment has determinate meaning only when these three are stated.

Why it happens

Each part directly reshapes interaction constraints: equipment sets input-output capability (touch versus desktop keyboard are different tasks), the physical environment sets perception and action conditions (screen legibility in sunlight, voice input failing in noise), and the social environment sets permitted behavior (private operations in public, interruption norms in collaboration). Change any part and the distribution of performance and satisfaction moves—context is in the definition because these variables are determinants, not noise.

Studying it

Context analysis is the standard's companion method: inventory equipment, physical, and social factors item by item into a context description that serves as the evaluation's premise. Empirically, field studies and context-faithful labs compare the same interface across context cells to quantify each part's impact. Beware interactions between variables (mobile × bright × one-handed arrive together); testing factors independently underestimates combination effects.

Where it stops holding

Context elements cannot be enumerated exhaustively: the standard asks for "relevant" factors, and relevance judgment introduces subjectivity; labs can control and reproduce only part of the space, and extrapolation to uncovered combinations needs care. The social environment resists standardization most—organizational culture, motivation, and presence effects are hard to reproduce, and context descriptions often decay into narrative there. Context also drifts during use; it is not static.

Applying it

• Write a context specification before evaluation and acceptance: device models, environmental conditions, and social constraints itemized, with uncovered contexts declared out of scope.
• For mobile and cross-device products, plan testing on a context-combination matrix prioritizing high-frequency, high-risk cells.
• In field studies, log social variables—who is present, time pressure, interruption sources—since they are the usual reason lab results fail to transfer.

Related

• Same group: B5.08.1 The standard definition confines usability to specified users, specified goals, and a specified context of use · B5.08.3 The definition treats usability as a relational property of product and context, not an inherent property of the product · B5.08.4 Newer standards place usability inside a broader quality-in-use concept alongside accessibility, not containing it
• Nearby: K1 Platforms and Device Forms · Q2 Usability Testing
• Search terms: context of use · context analysis · field study