轮椅使用说明书的可读性评价

结论：说明书的作用是被理解，写了但看不懂等于没写

轮椅的说明书承载着安全信息——载重限制、使用限制、调节方法、检查要点、警示。但这些信息只有在被使用者理解之后才起作用。

而实际情况是：多数使用者不会完整读说明书，读了也不一定看懂。 原因包括篇幅长、术语多、排版不便于查找、字号小、以及翻译生硬。

轮椅使用者中老年人比例高，部分人有视力、认知或阅读方面的限制，这使可读性的要求高于一般消费品。

可读性不是主观感受，它有可以评价的维度和可以改进的方向。

可读性的维度

维度	内容
语言	用词、句长、术语
结构	章节组织、查找便利
版式	字号、行距、对比度
图示	图的清晰度与配合
重点突出	关键信息是否醒目
完整性	信息是否齐全
一致性	术语与表述的统一

语言方面的考察

用词的通俗性。 避免不必要的专业术语，必须用的要解释。

句子长度。 长句难以理解，应当拆短。

主动语态。 「按下按钮」比「按钮应被按下」更直接。

明确的指令。 「每月检查一次」比「定期检查」更可执行。

避免否定的堆叠。 「不要不检查」这类表述容易误读。

翻译的自然度。 从其他语言翻译的说明书，语句是否通顺。

「明确的指令」是实用的改进方向。 把「定期检查」改成「每月检查一次」，把「发现异常应停止使用」改成具体的可观察现象，使用者才知道该怎么做。

结构方面的考察

目录与索引。 能否快速找到需要的内容。

章节的逻辑。 按使用流程组织比按功能罗列更便于查找。

分级清晰。 标题层次不宜过多。

交叉引用。 相关内容之间的引导。

快速参考。 常用信息是否有便于查阅的汇总。

「按使用流程组织」对说明书的实用性提升明显。 使用者查说明书通常是遇到了具体问题——怎么折叠、怎么调座高、怎么换脚垫，按这些任务组织比按「结构说明」「技术参数」「维护保养」组织更好找。

版式方面的考察

字号。 考虑老年使用者的视力，字号不宜过小。

对比度。 文字与背景的对比。浅灰字在白底上难以辨认。

行距与段落。 过密的排版难以阅读。

留白。 适当的留白降低阅读压力。

字体。 便于辨认的字体。

纸张与印刷。 反光的纸张影响阅读。

「字号和对比度」是最容易改进也最有效的方面。 为了美观使用小字号浅色字，对目标使用者是实际的障碍。

图示的考察

图示对操作类信息尤其有效：

图的清晰度。 线条、细节是否清楚。

图文配合。 图与对应文字的位置关系。

操作步骤的分解。 多步骤操作用分步图示。

方向与顺序的表达。 箭头、编号的使用。

图中的标注。 部件名称与文中一致。

「分步图示」对调节和装配类操作的帮助明显，比大段文字描述有效得多。

重点信息的突出

警示的层级。 危险、警告、注意的区分与表达。

警示的位置。 在相关操作说明的附近，而不是集中在开头。

视觉突出。 框线、颜色、图标。

关键参数的醒目。 载重上限、坡度限制这类关键信息。

「警示放在相关操作附近」比集中在开头有效。 使用者在做某个操作时看到对应的警示，比在开头读过一遍要有效得多。

评价的方法

专家审阅。 由熟悉产品和使用者的人员审阅。

可读性指标。 句长、用词难度等可以量化的指标。

使用者测试。 请目标使用者按说明书完成特定任务，观察是否能完成。这是最直接的评价方法。

任务完成率。 使用者能否按说明书完成操作。

理解测试。 读完某段后能否正确回答相关问题。

查找测试。 能否快速找到特定信息。

「使用者测试」的价值在于它暴露真实的问题。 设计者认为清楚的表述，使用者可能完全理解不了，这只有通过实际测试才能发现。

常见的问题

篇幅过长。 关键信息淹没在大量文字中。

术语过多。 使用者不理解的专业词汇。

警示集中在开头。 与具体操作脱节。

缺少图示。 操作说明只有文字。

字号过小。 对老年使用者不友好。

查找困难。 没有目录或索引。

指令不具体。 「定期」「适当」「必要时」这类模糊表述。

翻译生硬。 直译导致的难以理解。

多语言版本的问题

面向多个市场的产品需要多语言说明书，相关的问题：

翻译质量。 技术翻译的准确性和语句的自然度。

参数的一致性。 各语言版本中的数值和单位一致。

文化适应。 某些表述或图示在不同文化中的理解可能不同。

版面的适配。 不同语言的文字长度不同，版面要能适应。

版本管理。 各语言版本与主版本的对应和同步更新。

「各语言版本的同步更新」是管理上的难点。 主版本修订后，各语言版本如果不同步更新，会出现内容不一致。建议建立版本对应表并纳入变更流程。

电子说明书

部分产品采用电子说明书，相关考虑：使用者能否获取（网络条件、设备）；纸质版的提供要求；内容的可读性（屏幕阅读与纸质不同）；以及版本的可追溯。

对于轮椅这类使用者可能是老年人的产品，完全依赖电子说明书需要谨慎，纸质版或产品上的关键标识仍然必要。

我们的做法

说明书的可读性评价与我们的检测工作不是同一类，但说明书中的技术参数与检测报告的一致性，是我们会关注的内容。

我们在出具报告时会建议委托方做一次核对：说明书中出现的每个技术参数，都应当在检测报告中找到对应的实测值。 这一项不一致是审查中常被指出的问题。

另外，说明书中的检查要点和使用限制，应当与检测中发现的产品特性对应——比如某个部位在疲劳试验中表现出较早的磨损，说明书的检查要点就应当包含这个部位。

如果你需要核对说明书参数与检测数据的一致性，或者需要检测方面的技术支持，可以联系：132 4819 8029。检测能力见服务介绍，产品分类见手动轮椅检测与电动轮椅检测，案例见案例。

English version

Conclusion. Wheelchair instructions carry safety information: weight limits, use limitations, adjustment methods, check points and warnings. That information only works once the user understands it. In reality, most users do not read instructions fully, and those who do may not understand them, for reasons including length, terminology, layout that resists searching, small type and stilted translation. Wheelchair users include a high proportion of older people, some with visual, cognitive or reading limitations, so readability requirements exceed those for ordinary consumer products. Readability is not a matter of impression; it has assessable dimensions and improvable directions.

Dimensions of readability. Language covers vocabulary, sentence length and terminology. Structure covers chapter organisation and ease of searching. Layout covers type size, line spacing and contrast. Illustration covers clarity and coordination with text. Emphasis covers whether key information stands out. Completeness covers whether the information is there. And consistency covers uniform terminology and expression.

Examining language. Vocabulary should be plain, avoiding unnecessary technical terms and explaining those that are necessary. Sentences should be short, since long ones resist comprehension. Active voice reads more directly than passive. Instructions should be definite, since check monthly is more actionable than check periodically. Stacked negatives should be avoided, since constructions like do not fail to check are easily misread. And translation should read naturally, since translated instructions can read awkwardly. Definite instructions are the practical improvement: changing check periodically to check monthly, and stop using if abnormal to a specific observable condition, tells the user what to do.

Examining structure. A contents list and index determine whether information can be found quickly. Chapter logic organised by task is easier to search than a functional listing. Heading hierarchy should not run too deep. Cross-references guide between related content. And a quick reference summarises commonly needed information. Organising by task improves usability noticeably: users consult instructions because they have a specific problem, such as how to fold, how to adjust seat height or how to change a ferrule, and organising around those tasks works better than sections headed construction, specifications and maintenance.

Examining layout. Type size should allow for older users' eyesight and not be too small. Contrast between text and background matters, since pale grey on white is hard to read. Line spacing and paragraphing affect readability, dense setting resisting it. White space reduces the effort of reading. Typefaces should be legible. And paper and printing matter, since reflective stock impedes reading. Type size and contrast are the easiest and most effective improvements: small pale type chosen for appearance is a real obstacle to the intended readers.

Examining illustrations. Illustration works particularly well for operational information. Clarity covers whether lines and detail are legible. Coordination covers the position of illustrations relative to their text. Step breakdown covers using sequential illustrations for multi-step operations. Direction and sequence should be conveyed through arrows and numbering. And callouts should use component names matching the text. Sequential illustration helps markedly with adjustment and assembly tasks, far more than extended written description.

Emphasising key information. Warning hierarchy distinguishes danger, warning and caution. Warning placement should be near the relevant operating instruction rather than collected at the front. Visual emphasis uses rules, colour and symbols. And key parameters such as weight limits and gradient limits should stand out. Placing warnings near the relevant operation works better than collecting them at the front: seeing the warning while performing the operation is far more effective than having read it once at the beginning.

Assessment methods. Expert review by people familiar with the product and its users. Readability measures such as sentence length and vocabulary difficulty, which can be quantified. User testing, asking target users to complete specific tasks using the instructions and observing whether they succeed, which is the most direct method. Task completion rate, measuring whether users can perform operations from the instructions. Comprehension testing, asking questions after reading a section. And search testing, measuring whether specific information can be found quickly. User testing is valuable because it exposes real problems: wording the designer considers clear may be wholly incomprehensible to users, which only actual testing reveals.

Common problems. Excessive length, burying key information. Excessive terminology unfamiliar to users. Warnings collected at the front, detached from the operations they concern. Missing illustrations, with operating instructions in text only. Type too small for older users. Difficult searching, with no contents or index. Vague instructions using words like periodically, appropriately and as necessary. And stilted translation from literal rendering.

How we handle it. Readability assessment is not the same work as our testing, though consistency between the technical parameters in the instructions and the test reports is something we attend to. When issuing reports we suggest that clients check that every technical parameter appearing in the instructions has a corresponding measured value in the reports; inconsistency there is frequently raised during review. We also suggest that the check points and use limitations in the instructions correspond to product characteristics found during testing: where a location shows early wear in fatigue testing, for instance, the instructions' check points should include it.

If you need to reconcile instruction parameters with test data, or need technical support on testing, get in touch: +86 132 4819 8029.