Intended users affect the safety context
The specific needs of the group for whose use a product is intended are expressly relevant to defectiveness under Article 7(2)(h) of Directive (EU) 2024/2853. A product aimed at people with particular limitations or dependencies cannot be assessed only against the capabilities of an imagined ideal operator. Identify the intended users and the safety functions they reasonably rely upon, together with the product's presentation and foreseeable use.
This remains the objective expected-safety assessment, rather than a rule that one individual's private expectation decides defectiveness. Recital 30 describes the expectations of the public at large while recognising the specific requirements of intended users. The inquiry should explain why a characteristic of the user group matters to the actual task and hazard. Vulnerability is context, not a substitute for analysing the product.
Avoid broad assumptions about capability
Children, older people and people with disabilities do not form uniform groups with identical abilities. A useful assessment identifies relevant characteristics such as reach, grip, comprehension, perception of warnings or dependence on a protective function. A general age label does not explain whether a particular control or instruction provides expected safety. Nor does a diagnosis alone establish the nature of the risk.
The product's purpose matters. Equipment intended to support a person with limited mobility may create expectations about stability and access different from those associated with a general-purpose item. A device used by a trained professional can nevertheless protect a vulnerable patient. Distinguish the operator from the person exposed to harm, because they may have different needs and different opportunities to recognise or avoid danger.
Presentation helps identify the intended group
Packaging, product descriptions, instructions and design features can indicate intended users. Preserve the actual version supplied. A product advertised for a particular group should be assessed with that representation in view, rather than solely through a generic technical label. Equally, a product's incidental appeal does not automatically establish every claimed intended use. The evidence should support the classification.
The analysis of product presentation explains how prominent messages and qualifications interact. An interface implying easy independent operation may be relevant where safety instructions assume continuous specialist assistance. That inconsistency needs examination rather than an automatic conclusion. Identify the task, the necessary protection and how the user is expected to access it under realistic conditions.
Protective functions can carry particular importance
Article 7(2)(i) separately recognises failure of a product whose very purpose is to prevent damage to fulfil that purpose. A protective alarm or life-supporting function therefore raises questions different from a missed convenience feature. Consider what the user depends on, how failure would be detected and what realistic alternatives exist. Avoid assuming that an operator can compensate for a silent failure merely because a manual describes a theoretical check.
Recital 30 identifies life-sustaining medical devices as capable of generating particularly high safety expectations because of their risk. The Court of Justice's Boston Scientific judgment, joined cases C-503/13 and C-504/13, provides earlier context under Directive 85/374/EEC. In that particular medical-device setting, products in a group or production series with a potential defect could be classified as defective without proving the individual item's actual defect. That judgment should not be presented as a universal rule about every product or every user group.
Information and design work together
A warning may be technically accurate while poorly suited to the intended audience. Assess language, format, placement and the action required. A warning that depends on fine visual discrimination may have a different practical effect for a product aimed at users with impaired vision. The relevant question concerns the safety communication in context, including other available safeguards, rather than typography in isolation.
Design can affect whether a predictable mistake becomes dangerous. Consider controls, access to hazardous parts, physical stability and feedback showing whether a protective function is active. These are examples of matters to investigate, not automatic legal requirements imposed on every product. The assessment must identify the relevant safety expectation or binding rule and the evidence that the product fell short.
Keep injury and defect evidence separate
A vulnerable person's injury does not by itself prove that the product was defective. Establish the product state, alleged safety shortfall and causal mechanism. Conversely, a person's vulnerability does not make the harm irrelevant or automatically shift responsibility away from the product. Avoid assumptions in either direction. The evidence should show how the product and circumstances interacted.
Article 10 starts with defectiveness, damage and a causal link, subject to specified rebuttable presumptions. The user's needs may be highly relevant to the first question while leaving the others unresolved. Medical or technical evidence can have different roles, and sensitive information should be included only where pertinent to the safety and harm questions being examined.
A useful user-context record
Document the intended group, product purpose, relevant tasks and the capabilities the design or instructions assume. Preserve supplied information, configuration and evidence of the protective function. Separate a general user-group characteristic from facts established about the incident. Where another person operated or maintained the product, record that relationship rather than treating all conduct as the injured person's own action.
The applicable national implementation, product scope and procedure still require checking before a particular dispute is assessed. Intended-user needs strengthen the factual foundation of a safety inquiry; they do not supply an automatic compensation result. A careful explanation states why those needs matter to the alleged defect and what additional evidence is needed to connect it with the damage.
Records that help the review
Use the following as a practical starting point. Select and preserve records appropriate to the product, incident and applicable procedure.
- Incident-time product identity and configuration
- Source documents and dated safety analysis
- Separate defect, damage and causation records
Independent educational information at EU Directive level. National implementing law and procedure require separate review.
Primary sources and legal scope
This page explains the EU Directive framework. Check national implementing law, the corrected temporal scope and relevant procedure before applying it to a case.
- Directive (EU) 2024/2853, consolidated text: Articles 7, 10 ↗
- Official Journal corrigendum, 7 May 2026: Article 2(1) ↗
- Directive (EU) 2024/2853, corrected text: defectiveness, proof and related liability provisions ↗
- Court of Justice, Boston Scientific, joined cases C-503/13 and C-504/13, judgment of 5 March 2015, paragraphs 37 to 43 ↗
Source register: corrected scope verified 16 October 2026. Article references identify the legal basis. No qualified legal review or national implementation status is claimed.