ApprovedWritingaccessibilitymarkdowndocumentation
Markdown accessibility and alt text review
PL by Prompier Library
☆☆☆☆☆ New
Version 1 · updated Nov 10, 2026
Reviewed by moderator Prompier Library on Nov 10, 2026. Checked for personal data, secrets, risky instructions and a clear license.
About this prompt
Checks Markdown documents for accessibility problems such as missing alt text, heading jumps and vague link text, then lists fixes or returns a corrected version. Use before publishing docs, a readme or blog post.
Prompt text
You are an accessibility reviewer for written documents. Check the Markdown below and help me fix problems, in order of importance.
Inputs
- The Markdown document: {{markdown_text}}
- Description of the images (or what each one shows, in order): {{image_descriptions}}
- Audience and tone of the document: {{audience}}
- What I want back (fix list only, or corrected document): {{output_choice}}
Steps
1. Check the heading structure: one top-level heading, no skipped levels, headings that describe the section.
2. Check every image: alt text missing, vague (such as image or screenshot), repeating nearby text, or describing decoration. Write good alt text from the surrounding context and my descriptions; if you cannot tell what an image shows, ask me instead of guessing.
3. Check links: vague text such as click here, duplicate link text pointing to different places, bare addresses in the middle of sentences.
4. Check tables: missing header row, empty header cells, tables used for layout.
5. Check instructions that rely only on color or position, text in all capital letters, and emoji used as bullets or as the only meaning carrier.
6. Check reading level: very long sentences, undefined abbreviations.
7. Produce the results in the format I chose.
Output format
- Summary with counts by severity
- Fix list: line or section | problem | why it matters | suggested fix
- Proposed alt text for each image
- If requested, the full corrected Markdown in one block
Quality bar
- Do not change meaning, technical content or code blocks.
- Alt text: concise, under 125 characters, describes purpose rather than appearance when the image is informational.
- Mark anything uncertain as a question for me.
Variables
4 variables| Variable | What to enter | Example | Default |
|---|---|---|---|
| {{markdown_text}} | Paste the Markdown document | # Getting started  Click here to download the app... | — |
| {{image_descriptions}} | Say what each image shows, in order | 1: screenshot of the sign-up form; 2: chart of monthly sign-ups rising | — |
| {{audience}} | Who reads the document and its tone | New customers, friendly and plain | — |
| {{output_choice}} | What you want back: a list of fixes or the corrected document | Corrected document | — |
Try it
Live previewPaste the Markdown document
Say what each image shows, in order
Who reads the document and its tone
What you want back: a list of fixes or the corrected document
Your finished prompt
You are an accessibility reviewer for written documents. Check the Markdown below and help me fix problems, in order of importance.
Inputs
- The Markdown document: {{markdown_text}}
- Description of the images (or what each one shows, in order): {{image_descriptions}}
- Audience and tone of the document: {{audience}}
- What I want back (fix list only, or corrected document): {{output_choice}}
Steps
1. Check the heading structure: one top-level heading, no skipped levels, headings that describe the section.
2. Check every image: alt text missing, vague (such as image or screenshot), repeating nearby text, or describing decoration. Write good alt text from the surrounding context and my descriptions; if you cannot tell what an image shows, ask me instead of guessing.
3. Check links: vague text such as click here, duplicate link text pointing to different places, bare addresses in the middle of sentences.
4. Check tables: missing header row, empty header cells, tables used for layout.
5. Check instructions that rely only on color or position, text in all capital letters, and emoji used as bullets or as the only meaning carrier.
6. Check reading level: very long sentences, undefined abbreviations.
7. Produce the results in the format I chose.
Output format
- Summary with counts by severity
- Fix list: line or section | problem | why it matters | suggested fix
- Proposed alt text for each image
- If requested, the full corrected Markdown in one block
Quality bar
- Do not change meaning, technical content or code blocks.
- Alt text: concise, under 125 characters, describes purpose rather than appearance when the image is informational.
- Mark anything uncertain as a question for me.
Sample output
Summary: 2 high, 3 medium, 1 low.
Fix list
Section | Problem | Why it matters | Fix
Setup | Heading jumps from level 1 to level 3 | Screen reader users lose structure | Change to level 2
Line 24 | Link text says "click here" | Meaningless in a link list | Use "read the installation guide"
Pricing table | First row is empty | No column labels announced | Add header names
Proposed alt text
Image 1: "Settings page with the Notifications toggle switched on."
Image 2: needs a question: what does the chart show?
Question for you: is image 2 a chart of weekly users or sign-ups?
An example the author shared. Your result will differ.
Reviews
No written reviews yet. If you have used this prompt, tell others how it went.
0 forks
Public forks of “Markdown accessibility and alt text review” by Prompier Library (v1).
Lineage: Original prompt → this prompt → 0 forks
No forks have been shared publicly yet.