PUBLIC · REVIEW & REFINE

Check an interface for accessibility barriers

Review interaction and readability, and identify what needs manual testing.

When to use it

Before a screen ships, or when a report says it cannot be used with a keyboard or a screen reader.

What to expect

Issues with location, affected users, reproduction steps, and a proposed correction; automated checks separated from the manual verification still required.

Example

A sign-up form with a custom dropdown and an inline error message.

Add your context

Optional. Leave fields blank to copy a reusable template. What you type stays in this tab.

interface or sourcekey user flowsDOM, code, or test output, pasted as textstandard and version

PROMPT TEMPLATE

Review {{INTERFACE}} for accessibility barriers affecting {{KEY_USER_FLOWS}}.

Available evidence: {{AVAILABLE_EVIDENCE}}
Target standard: {{TARGET_STANDARD}}

Inspect semantics, accessible names, focus order and visibility, keyboard behavior, errors, contrast, text enlargement, and responsive reflow. Only report checks supported by the evidence available.

For each issue provide location, affected users, reproduction steps, and a proposed correction. Separate automated checks from required manual verification. Do not claim certification or complete compliance from a partial review.

4 of 4 context fields remaining.

Free to copy. Use it in the tools you already have.

← Back to the library