accessibility
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseAccessibility
无障碍访问
Make accessibility part of the interaction design rather than a compliance pass at the end.
将无障碍访问纳入交互设计环节,而非仅在最后进行合规性检查。
Always
基本原则
- Context — inspect what is already known before asking the user to repeat it. Use when product purpose or outcome can change the answer, and load only the additional project context the task needs.
.ux/INTENT.md - User — ground the work in the people affected, their goal, task, context, and available evidence. Do not invent user needs, behaviors, or personas.
- Evidence — keep known, inferred, assumed, unknown, and conflicted information distinct when the difference matters.
- System — prefer established product language, components, patterns, and rules before inventing new ones.
- Clear — lead with the useful point, use the minimum structure needed, and remove generic AI filler.
- Trust — never invent evidence, requirements, rationale, implementation status, or compliance.
- Outcome — for substantial multi-step work, keep intent active, use a small only when continuity needs it, prioritize the highest-impact unresolved gap before polishing, and verify the actual experience against intent before declaring completion.
.ux/STATE.md
Do not recite these rules to the user unless one of them materially affects the answer.
Do not introduce research questions, personas, or discovery work when the user and task are already clear or the missing information would not materially change the work.
- 上下文 — 在要求用户重复信息前,先核查已知内容。当产品目标或结果会影响答案时,使用,且仅加载任务所需的额外项目上下文。
.ux/INTENT.md - 用户 — 基于受影响用户的目标、任务、场景及现有证据开展工作。不得凭空捏造用户需求、行为或角色。
- 证据 — 当信息差异至关重要时,需明确区分已知、推断、假设、未知及存在冲突的信息。
- 系统 — 优先采用已确立的产品语言、组件、模式及规则,而非自行创造新内容。
- 清晰性 — 开门见山呈现核心要点,使用最少必要结构,剔除通用AI生成的冗余内容。
- 可信度 — 不得捏造证据、要求、理由、实施状态或合规性信息。
- 成果导向 — 对于复杂的多步骤工作,保持意图明确;仅当需要维持工作连续性时使用小型;在优化细节前优先处理影响最大的未解决问题;在宣布完成前,需验证实际体验是否符合设计意图。
.ux/STATE.md
除非这些原则对答案有实质性影响,否则无需向用户复述。
当用户及任务已明确,或缺失信息不会对工作产生实质性改变时,无需引入研究问题、用户角色或探索性工作。
Establish the actual target
明确实际目标
Read accessibility expectations from the smallest relevant context when present, then inspect organizational policy, project standards, design-system accessibility documentation, and relevant platform requirements. If the project does not define a target, state what standard you are using as a review baseline rather than inventing a requirement.
.ux/若存在最小相关上下文,从中读取无障碍访问期望;随后核查组织政策、项目标准、设计系统无障碍文档及相关平台要求。若项目未定义目标,需说明审查所采用的基准标准,而非自行制定要求。
.ux/Inspect behavior, not just appearance
审查行为,而非仅看外观
Review only the dimensions relevant to the work, including:
- semantic structure and programmatic relationships;
- accessible names, labels, instructions, status, and errors;
- keyboard operation and visible focus;
- focus movement after navigation, validation, async updates, dialogs, and errors;
- screen-reader announcements for meaningful dynamic change;
- reading and interaction order;
- contrast when actual values can be verified;
- zoom, text resize, reflow, orientation, and responsive behavior;
- target size and pointer alternatives;
- motion, timing, auto-updating, or flashing content;
- cognitive load, error prevention, and recovery;
- alternatives for sensory-only cues;
- authentication or verification interactions that may create barriers.
Use established accessible behavior from the design system rather than redesigning it locally.
仅审查与工作相关的维度,包括:
- 语义结构及程序化关联;
- 无障碍名称、标签、说明、状态及错误提示;
- 键盘操作及可见焦点;
- 导航、验证、异步更新、弹窗及错误发生后的焦点移动;
- 有意义的动态变化对应的屏幕阅读器提示;
- 阅读与交互顺序;
- 可验证实际数值的对比度;
- 缩放、文本调整、重排、方向及响应式行为;
- 目标尺寸及指针替代方案;
- 动效、计时、自动更新或闪烁内容;
- 认知负荷、错误预防及恢复机制;
- 仅依赖感官提示的替代方案;
- 可能造成障碍的身份验证或验证交互。
优先采用设计系统中已确立的无障碍行为,而非在本地重新设计。
Separate design findings from verification
区分设计发现与验证
A static design can reveal missing intent but cannot prove runtime accessibility. Code inspection can reveal likely behavior but does not replace keyboard, browser, screen-reader, zoom/reflow, or other appropriate testing.
Never claim WCAG or Section 508 compliance solely from a design review.
静态设计可揭示缺失的意图,但无法证明运行时的无障碍性。代码审查可预判可能的行为,但无法替代键盘、浏览器、屏幕阅读器、缩放/重排或其他合适的测试。
不得仅通过设计审查就宣称符合WCAG或Section 508标准。
Output
输出结果
Lead with barriers that can block task completion or create exclusion. For each material issue, state the condition, expected accessible behavior, available evidence, and what must be verified in implementation.
Avoid dumping the entire WCAG checklist when most criteria are irrelevant to the artifact.
优先呈现可能阻碍任务完成或造成排斥性的障碍。对于每个实质性问题,需说明问题场景、预期的无障碍行为、现有证据以及实施中需验证的内容。
当WCAG清单中多数标准与审查工件无关时,避免全盘罗列。
Examples
示例
- "Accessibility-review this flow."
- "What does engineering need to implement here for keyboard and screen readers?"
- "Check this against our 508 expectations."
- "Can I call this WCAG compliant yet?"
- "对该流程进行无障碍审查。"
- "工程师在此处需要实现哪些键盘和屏幕阅读器相关的功能?"
- "对照我们的508要求检查此项内容。"
- "我现在可以宣称这符合WCAG标准吗?"