Find source-visible labeling, semantics and keyboard risks, while separating code findings from checks that require a browser.
No public result for version 1 yet
Version 1 · 2 variables · 2 required
Fill in the values below — the customized prompt updates as you type. marks a required value.
Relevant HTML/component markup and behavior code. Default: <div onclick="save()">Save</div> <input type="email" placeholder="Email"> <div id="message"></div>
The task, states and relevant interaction expectations. Default: A visitor enters an email address and saves notification preferences. A success or validation message appears after submission.
Review this interface source for accessibility:
<div onclick="save()">Save</div>
<input type="email" placeholder="Email">
<div id="message"></div>
Intended interaction and users:
A visitor enters an email address and saves notification preferences. A success or validation message appears after submission.
Find source-visible issues involving semantic elements, accessible names, form labels, focus order, keyboard operation, dynamic updates and error messaging. For each finding, quote the relevant element, explain the user impact, and suggest the smallest concrete correction.
Separate confirmed source findings from questions needing rendered-page or assistive-technology testing. Do not infer color contrast, focus visibility or actual screen-reader behavior from missing styles or runtime context.
Provide a short manual test sequence covering keyboard-only use and the main user task. Prioritize blockers over cosmetic improvements. Avoid a compliance score or a claim that the page satisfies an accessibility standard based on source inspection alone.No public examples yet for version 1
No public results yet
Break a dependency replacement into reviewable stages with compatibility checks, exit criteria and realistic rollback limits.
No public results yet
Define realistic traffic, workload data, measurements and stopping rules for an authorized performance test.
No public results yet
Map feature assets, trust boundaries and data flows to concrete threats, existing controls and targeted verification tasks.
No public results yet
Turn an API contract into a small client design that handles retryable failures, deadlines and idempotency deliberately.
No public results yet
Interpret supplied plan evidence and prioritize query or index experiments without inventing costs or speedups.
No public results yet
Check whether keys, constraints and relationships actually enforce the application's stated data rules.
Oldest first · one level of replies
Sign in to join the discussion. Share what you learned or made with this prompt.
No comments yet
Be the first to share how this prompt worked for you.