编写可复现的无障碍缺陷报告
将无障碍问题整理为含运行环境、复现步骤、实际与预期表现及影响程度的缺陷报告。
完整提示词
<context>
Accessibility bugs get closed as "cannot reproduce" or "works for me" more than most, because the reproduction depends on the exact assistive technology, browser and mode (NVDA browse versus focus mode, VoiceOver with Safari versus Chrome, TalkBack with explore by touch), and because developers who do not use a screen reader do not know what "it reads wrong" means. A good report states the setup, the exact keystrokes or gestures, what was announced word for word versus what should have been, the WCAG success criterion as a reference rather than a verdict, who is blocked and whether there is a workaround. Severity should follow user impact on the task (blocker: cannot complete; major: completes with difficulty or only with help; minor: annoying), not the WCAG level.
</context>
<task>
<finding>
{{finding}}
</finding>
{{#tracker_template}}
Fit this template:
{{tracker_template}}
{{/tracker_template}}
1. Write a title in the form "[Component] [problem] for [who] on [where]", for example "Date picker: selected date not announced to screen readers on checkout".
2. Write the environment: assistive technology and version, browser or app and version, operating system, device, and mode or setting used. Leave unknown items as "not stated", never guessed.
3. Write numbered reproduction steps with exact keys or gestures, starting from a URL or screen.
4. Write "Actual": what happened, with announcements quoted. Write "Expected": what should happen, with the expected announcement or behaviour.
5. Add the likely WCAG success criterion (number and name) with a one-line reason, and a severity with its reason in user terms, plus any workaround.
6. Add a suggested fix only if the cause is clear from the finding, labelled as a suggestion.
7. List the details that are missing and would make the report reproducible.
</task>
<constraints>
- Do not invent versions, URLs, announcements or steps the finding does not support; mark gaps.
- Use neutral, specific language; no blame, no "violates the law".
- One problem per report; if the finding contains several, split them and say so.
</constraints>
<output_format>
## Title
One line.
## Report
Environment, Steps, Actual, Expected, WCAG reference, Severity, Workaround, Suggested fix.
## Missing details
Bullets, or "none".
</output_format>可替换内容
- {{finding}}
- {{#tracker_template}}
- {{tracker_template}}
- {{/tracker_template}}
- [Component]
- [problem]
- [who]
- [where]
分类与标签
编程开发、无障碍测试、缺陷报告、屏幕阅读器、问题复现