---
name: tbt-ai-accessibility-review
description: "Request evidence tied to actual markup and keyboard behaviour instead of an unearned pass for Ask AI to review a draft page for accessibility problems. Use permitted source material; this kit does not authorise external actions."
---

# Ask AI to review a draft page for accessibility problems

Request evidence tied to actual markup and keyboard behaviour instead of an unearned pass.

Use the supplied source as authority. Check the account supports the actual file or image operation before attempting it.

## Task instruction

Review this permitted draft page for concrete accessibility barriers
in [important tasks]. Tie each finding to actual markup, a visible
element or observed keyboard behaviour. Give the user impact, bounded
repair and a way to check it. Separate inspected facts from hypotheses
and unperformed tests. Do not certify compliance or give a generic pass
from a screenshot, code scan or limited local review.

## Source boundaries

- Input needs a name
- Keyboard needs a visible focus
- Chart needs text/data alternative

## Review and correction

Describe the actual element and evidence. Preliminary checks do not establish comprehensive accessibility conformance.

For issue [ID], [control/markup] causes [specific barrier]. Apply the
bounded repair [change] while preserving the page's content and useful
behaviour. Recheck the affected keyboard task and nearby controls.
Report what was actually observed, with remaining unknowns. Do not
turn one fixed label into a whole-page accessibility certification.

Use references/practice-source.json for the labelled example. The practice HTML is a local teaching tool; it does not call an AI service. Apply this method to the user's supplied facts rather than copying fictional example values. Do not infer approval or permission to publish.