Accessibility Conformance Test Evidence Pack
Prepare evidence for audits and customers.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Help me organize the evidence for an accessibility conformance claim. Product or site: [PRODUCT_OR_SITE]. Standard and level targeted (for example WCAG 2.2 AA): [STANDARD_AND_LEVEL]. Testing done so far (automated scans, manual checks, assistive technology tests, user testing): [TESTING_DONE]. Known issues: [KNOWN_ISSUES].
Create the pack as tables:
1. Scope table: Page or screen | Template type | Included in sample (yes/no) | Reason for inclusion.
2. Test matrix: Success criterion | Tested how | Tool or technology and version | Tester | Date | Result (supports, partially supports, does not support, not applicable) | Evidence reference.
3. Issues log: ID | Criterion | Description | Severity | Impact on users | Status | Fix date.
4. Assistive technology matrix: Combination (screen reader, browser, operating system) | Tasks tested | Result.
5. Remediation roadmap: milestone | owner | date.
Then draft the structure of a conformance report (similar to a VPAT-style document) with honest wording, and list statements that must not be made ("fully accessible") unless evidence supports them. Mark every part where a specialist's judgement is needed as [VERIFY]. Do not invent test results.
Treat all output as a draft for discussion. Have a qualified accessibility specialist, and a lawyer who knows [JURISDICTION] where legal risk matters, verify it before you rely on it or publish it.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into ChatGPT, Gemini, Claude or another assistant.