# Accessibility pass on page copy

> Use when a page has to work for screen reader users and the words, not the code, are the problem.

## املأها قبل التشغيل

- `{{PAGE_COPY}}`
- `{{IMAGE_LIST}}`
- `{{LINK_LIST}}`
- `{{PAGE_PURPOSE}}`

## البرومبت

```
You are reviewing page copy for accessibility. You are reviewing the words and their structure, not the code.

Page copy with heading levels marked: {{PAGE_COPY}}
Image list, each with what it shows and why it is on the page: {{IMAGE_LIST}}
Link text with destinations: {{LINK_LIST}}
What the page is for: {{PAGE_PURPOSE}}

Output:
1. Heading review of {{PAGE_COPY}}: the current order, where levels skip or repeat, and a corrected outline that still serves {{PAGE_PURPOSE}}.
2. Alt text table: Image from {{IMAGE_LIST}} | Decorative or informative | Proposed alt text under 125 characters | Why, including why it should be empty where it should.
3. Link text table: Current text from {{LINK_LIST}} | Does it stand up read on its own (yes/no) | Replacement | The destination it has to describe.
4. Copy issues: directional wording such as see below, colour-only references, unexpanded acronyms, first-use jargon, and sentences that only make sense with the layout.
5. Developer items: anything the copy cannot fix, listed separately.

Rules:
- Alt text describes the job the image does for {{PAGE_PURPOSE}}, not everything visible in it.
- Where {{IMAGE_LIST}} does not state an image's purpose, ask rather than writing alt text for it.
- Do not begin alt text with image of.
- No em dashes.
```

## كيف تحصل على نتيجة أفضل

- Say what each image is doing, since the same photo needs different alt text in a case study and a gallery.
- Read the link table aloud with nothing around it; that is roughly what a link list sounds like.
- This covers copy only, so pair it with a real audit against the success criteria.

---

من مكتبة برومبتات QuQi - https://www.quqi.io/ar/prompts/copy-accessibility-pass