系统状态可见性

本词条尚无可操作样本；插画为编辑示意。产品中仍需验证：状态变化是否真的能被辅助技术播报、反馈到达的实际时延是否匹配交互场景、以及呈现的状态文案是否对应系统已核实的真实结果。

{
  "evidenceType": "可用性启发式与无障碍标准",
  "limit": "本条目只约束状态是否被传达及传达方式，不规定具体机制的像素、时长或系统实际性能。"
}

{
  "id": "visibility-of-system-status",
  "type": "principle",
  "name": {
    "zh": "系统状态可见性",
    "en": "Visibility of System Status"
  },
  "aliases": [
    "Nielsen Heuristic #1",
    "状态可见性",
    "可见性原则"
  ],
  "granularity": "experience",
  "intents": [
    "inform",
    "track-progress"
  ],
  "tags": [
    "反馈",
    "状态",
    "可用性启发式",
    "无障碍",
    "响应时间"
  ],
  "definition": "系统应始终让用户了解当前发生了什么，通过恰当的反馈在合理时间内传达状态；这是 Nielsen 十大可用性启发式中的第一条。",
  "boundary": "这是一条原则，不是具体机制：确定进度条、不确定进度、状态消息、按下状态反馈都是它在不同场景下的具体落地。它关心的是状态是否被传达，而不是系统实际运行得有多快——响应更快属于性能问题，不属于本条目的范围。",
  "signature": [
    "任何耗时或结果不确定的操作都有对应的状态呈现",
    "反馈在与该交互匹配的时间窗口内出现，而非用户已经重试之后",
    "状态呈现的内容是系统已核实的事实，而非提前假定的结果"
  ],
  "when": [
    "操作有延迟、多个步骤或不确定结果，用户需要判断系统是否收到指令",
    "选择用哪种具体机制（进度条、状态消息、按下反馈等）来体现当前状态",
    "评估现有界面是否让用户在等待中感到失联或重复操作"
  ],
  "when_not": [
    "把本原则当作某个具体控件的实现规范去套用像素或时长",
    "用它来证明系统必须做得更快——它约束的是沟通是否到位，不是性能指标",
    "为满足可见性而堆砌无关紧要的状态提示，制造视觉与听觉噪音"
  ],
  "tradeoff": "持续传达状态能建立用户信任并减少误操作，但状态呈现本身占用界面空间和用户注意力，实现和维护多种状态展示也增加成本。",
  "comparison": {
    "focus": "用户是否始终知道系统在做什么",
    "mechanism": "通过界面反馈、进度、消息等在合理时间内传达当前状态",
    "cost": "需要为每类状态设计并维护对应的呈现方式"
  },
  "sources": [
    {
      "id": "nng-ten-heuristics",
      "title": "NN/g · 10 Usability Heuristics for User Interface Design",
      "url": "https://www.nngroup.com/articles/ten-usability-heuristics/",
      "claim": "将“系统状态可见性”列为第一条可用性启发式，原文表述为设计应始终通过恰当反馈在合理时间内让用户了解当前发生了什么。",
      "checkedAt": "2026-09-15",
      "archive": {
        "lookupUrl": "https://web.archive.org/web/20260915*/https://www.nngroup.com/articles/ten-usability-heuristics/",
        "status": "available",
        "checkedAt": "2026-09-15T18:21:57.626Z",
        "jobId": "spn2-c214ca6ca65135f964d23731cb22d3701cb6d598",
        "url": "https://web.archive.org/web/20260915182252/https://www.nngroup.com/articles/ten-usability-heuristics/",
        "timestamp": "20260915182252"
      }
    },
    {
      "id": "nng-visibility-system-status",
      "title": "NN/g · Visibility of System Status (Usability Heuristic #1)",
      "url": "https://www.nngroup.com/articles/visibility-system-status/",
      "claim": "详细阐述该启发式：系统状态传达得越好，用户越能理解当前状况、判断下一步操作，并建立对系统和品牌的信任；文中强调即时反馈有助于用户尽快发现并纠正错误。",
      "checkedAt": "2026-09-15",
      "archive": {
        "lookupUrl": "https://web.archive.org/web/20260915*/https://www.nngroup.com/articles/visibility-system-status/",
        "status": "available",
        "checkedAt": "2026-09-16T03:50:48.236Z",
        "jobId": "spn2-2b8f64f0221fac8cb374582c6ce79b84f5e28f16",
        "url": "https://web.archive.org/web/20260916035119/https://www.nngroup.com/articles/visibility-system-status/",
        "timestamp": "20260916035119"
      }
    },
    {
      "id": "wcag22-status-messages",
      "title": "W3C · Understanding SC 4.1.3 Status Messages (WCAG 2.2)",
      "url": "https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html",
      "claim": "AA 级准则要求状态消息可通过角色或属性被程序化确定，使辅助技术能够在不获得焦点的情况下将其呈现给用户，这是状态可见性在无障碍层面的具体要求。",
      "checkedAt": "2026-09-15",
      "archive": {
        "lookupUrl": "https://web.archive.org/web/20260915*/https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html",
        "status": "pending",
        "checkedAt": "2026-09-15T18:35:44.910Z",
        "error": "status-request-failed",
        "jobId": "spn2-2f1c0e8f56c74acc0181032b2c86b53260ff4025"
      }
    }
  ],
  "relations": [
    {
      "target": "determinate-progress",
      "kind": "realized_by",
      "condition": "系统能提供可靠的已完成量和总量",
      "reason": "确定进度条是本原则在可量化任务上的一种具体落地。",
      "basis": "editorial"
    },
    {
      "target": "status-message",
      "kind": "realized_by",
      "condition": "需要报告一次操作的结果或非阻断的状态变化",
      "reason": "状态消息是本原则在结果反馈场景下的具体落地。",
      "basis": "editorial"
    },
    {
      "target": "calm-technology",
      "kind": "related",
      "condition": "决定状态提示应当多显眼、多频繁",
      "reason": "可见性要求状态被传达，平静技术约束传达的方式不应抢夺注意力，两者共同决定实际体验。",
      "basis": "editorial"
    },
    {
      "target": "error-prevention",
      "kind": "composes_with",
      "condition": "用户在提交或执行不可逆操作之前",
      "reason": "让用户看清当前状态是预防误操作的前提之一，两者常需配合。",
      "basis": "editorial"
    }
  ],
  "rules": [
    {
      "when": "某个状态变化是用户关心的（如提交结果、连接状态、处理进度）",
      "instruction": "用辅助技术可播报的文本传达该变化，不能只靠颜色、图标等纯视觉手段。",
      "strength": "must",
      "basis": "editorial"
    },
    {
      "when": "设计反馈出现的时机",
      "instruction": "让反馈到达的时间与交互本身匹配，不要让用户在已经重试或怀疑系统失效之后才看到反馈。",
      "strength": "recommend",
      "basis": "editorial"
    },
    {
      "when": "呈现“已保存”“已同步”等状态文案",
      "instruction": "只报告系统已经核实的状态，不得在尚未确认成功前提前展示该文案。",
      "strength": "must",
      "basis": "editorial"
    }
  ],
  "principle": {
    "evidenceType": "可用性启发式与无障碍标准",
    "limit": "本条目只约束状态是否被传达及传达方式，不规定具体机制的像素、时长或系统实际性能。"
  },
  "demo": null,
  "version": "0.1.0",
  "editorialStatus": "drafted",
  "requirements": [],
  "demoCapabilities": [],
  "implementationNote": "本词条尚无可操作样本；插画为编辑示意。产品中仍需验证：状态变化是否真的能被辅助技术播报、反馈到达的实际时延是否匹配交互场景、以及呈现的状态文案是否对应系统已核实的真实结果。",
  "image": {
    "src": "/images/visibility-of-system-status.webp",
    "alt": "虚构的 FIELDNOTES 界面顶部有一条常驻的小状态条，左侧是一个同步状态圆点和一段简短文字，下方是一行进度提示，主内容区域保持完整未被遮挡。"
  },
  "searchTerms": [
    "feedback",
    "status",
    "usability heuristic",
    "accessibility",
    "response time"
  ]
}