返回提示词目录第 1162 页

编制产品无障碍符合性报告

依据审计证据整理符合性等级、问题说明与待补项,形成报告草稿并提示发布前需专业复核。

完整提示词

<context>
An Accessibility Conformance Report is a vendor's statement of how a product meets an accessibility standard, usually written on the VPAT template. Buyers read the remarks, not just the levels. Reports lose credibility (and can create legal exposure) when they claim "Supports" for criteria that were never tested, use vague remarks like "mostly accessible", omit the evaluation methods, or quietly drop known failures. The VPAT conformance terms are fixed: Supports, Partially Supports, Does Not Support, Not Applicable, and Not Evaluated (allowed only for Level AAA criteria in the WCAG tables).
</context>

<task>
Write an accessibility conformance report for {{product}} on the current VPAT template, edition: {{edition}} (wcag, section-508, en-301-549 or international). Use these results:
<audit_results>
{{audit_results}}
</audit_results>

1. If the audit does not say which WCAG version and level were tested, or what was in scope, ask and stop. Default to WCAG 2.2 Level A and AA if the user confirms no preference.
2. Fill the report header: product name and version, report date, description, contact placeholder, evaluation methods (tools, manual testing, assistive technologies with versions, and who tested), and the applicable standards for the edition.
3. For every success criterion at the levels in scope, in WCAG order, assign one conformance term:
   - **Supports**: tested, and no failures found.
   - **Partially Supports**: some functionality fails; name where.
   - **Does Not Support**: most or all functionality fails.
   - **Not Applicable**: the product has no content the criterion covers (for example no audio, no video); say why.
   Criteria the audit did not cover are not marked Supports: put `[NOT YET EVALUATED]` in the conformance cell and list them under Gaps before publishing, so the report cannot be published as finished. For WCAG 2.2, 4.1.1 Parsing is obsolete; follow the template's note for it instead of evaluating it.
4. Write remarks that a buyer can act on: which screens or components fail, how (for example "Date picker cannot be operated with the keyboard"), and a planned fix only if the user provided one. Keep remarks factual, without marketing language or promises.
5. For editions beyond WCAG, add the extra chapters the edition requires (for example Section 508 chapters 3, 5 and 6, or EN 301 549 clauses for functional performance, software and documentation) and mark the ones the audit does not address as gaps rather than guessing.
</task>

<constraints>
- Never upgrade a level beyond what the audit evidence shows, and never omit a known failure.
- Keep personal names out of the report unless the user supplies them for the contact field.
- The report is the vendor's own statement. Recommend a review by an accessibility specialist and, where the report goes into contracts or public procurement, by legal counsel before publishing.
</constraints>

<output_format>
## Report
The report in Markdown: header fields, evaluation methods, applicable standards, then one table per level or chapter with columns criterion, conformance level, remarks and explanations.
## Gaps before publishing
Numbered list: criteria not evaluated, missing header information, chapters the audit did not cover.
</output_format>

可替换内容

  • {{product}}
  • {{edition}}
  • {{audit_results}}
  • [NOT YET EVALUATED]

分类与标签

办公效率、无障碍报告、审计结果整理、采购文档、发布前复核

前往 AI 图片创作