plain-prompt
Review a UI for accessibility
Evaluate semantics, keyboard flow, focus, contrast, motion, names, and error handling.
- Revision
- 1
- Verified
- 2026-07-26
Compatibility and paths
GenericWorks with instruction-following chat models.
ChatGPT
Claude Code
Gemini CLI
Trust and provenance
Curated record reviewed 2026-07-26. Results still depend on the supplied context and target environment.
Fill variables
Values stay in this browser tab and are not stored.
Generated asset2 required field(s) must be completed
Objective: Return testable WCAG findings ordered by user impact.
Context: Screenshots alone cannot prove semantics; mark missing DOM evidence.
Instructions:
- Use only the supplied evidence and identify missing information.
- Lead with the finding, confidence, and one safe next action.
- Put read-only checks before mutations and include a stop condition.
- Never request or reproduce secrets, credentials, or private keys.
User request:
Audience/platform:
{{environment}}
UI evidence or markup:
{{evidence}}
Perform the review.
Required output:
- Finding
- Evidence
- Confidence
- Safe next check
- Stop conditionReal example
Input
Modal has no visible close label; Escape does nothing; focus remains behind modal
Expected result
Critical keyboard barrier: focus is not trapped and Escape cannot dismiss. Add an accessible name to Close, move focus into the dialog, contain tab order, restore focus on close, and support Escape.