These prompts help researchers and developers apply AI at key stages of accessibility testing — from generating alt text to planning remediation sprints. Each prompt includes placeholders for your specific project data.
Prompt 1: Generate alt text for a batch of product images
I have [number] product images from an e-commerce site that need alt text meeting WCAG 2.1 SC 1.1.1 (Non-text Content).
For each image, I will provide:
- The image file name
- The product name
- The page context (product listing, detail page, or category page)
Rules for generating alt text:
1. Describe the product as a sighted user would see it — include color, material, and key features visible in the image.
2. Keep alt text between 50-125 characters.
3. Do not start with "Image of" or "Photo of" — screen readers already announce the element as an image.
4. If the image is purely decorative (a background pattern, a divider), output alt="" with a note explaining why.
5. If the image contains text (e.g., a badge saying "Sale"), include that text in the alt text.
Here are the images:
[Paste list: filename | product name | page context]
Output format: a table with columns: Filename | Alt Text | Character Count | Notes.Prompt 2: Audit a page’s heading structure for WCAG compliance
I am auditing the heading structure of a web page for WCAG 2.1 SC 1.3.1 (Info and Relationships) and SC 2.4.6 (Headings and Labels).
Here is the full heading hierarchy extracted from the page (tag and text):
[Paste heading list, e.g.:
h1: Welcome to Our Store
h3: Featured Products
h2: Categories
h4: Electronics
h4: Clothing
h2: About Us]
Please:
1. Check whether the heading hierarchy is logical and sequential (h1 → h2 → h3, no skipped levels).
2. Identify any heading level skips and explain which WCAG criterion they violate.
3. Check whether heading text is descriptive enough for a screen reader user to understand page structure from headings alone.
4. Suggest a corrected heading hierarchy that fixes all issues.
5. Note any headings that appear to be used for visual styling rather than semantic structure (a common violation).Prompt 3: Generate a WCAG compliance remediation plan from scan results
I ran an automated accessibility scan on [site/app name] and got the following results. Each issue includes the WCAG success criterion violated, the number of instances, and the element type affected.
Scan results:
[Paste results, e.g.:
- SC 1.1.1 (Non-text Content): 47 images missing alt text
- SC 1.4.3 (Contrast Minimum): 23 text elements below 4.5:1 ratio
- SC 4.1.2 (Name, Role, Value): 12 buttons without accessible names
- SC 2.4.4 (Link Purpose): 8 links with text "click here" or "read more"
- SC 1.3.1 (Info and Relationships): 5 form fields without associated labels]
Please:
1. Prioritize these issues by user impact (critical / major / minor) and explain the reasoning.
2. For each issue, provide a specific code-level fix with a before/after HTML example.
3. Estimate the development effort for each fix (quick fix: <1 hour, medium: 1-4 hours, significant: >4 hours).
4. Group the fixes into a 3-sprint remediation plan, starting with quick wins and critical issues.
5. Note any issues that likely indicate a systemic problem in a component or template.Prompt 4: Draft an accessibility audit executive summary
I completed an accessibility audit of [product name]. Here are the key findings:
Testing methods used: [automated scan with axe, manual expert review, user testing with N participants with disabilities]
WCAG standard: [2.1 AA / 2.2 AA]
Pages/flows tested: [list]
Summary of findings:
- Total issues found: [number]
- Critical (blocks task completion): [number]
- Major (significant difficulty): [number]
- Minor (inconvenience): [number]
- WCAG criteria tested: [number] | Passed: [number] | Failed: [number]
- Top 3 most impacted user groups: [e.g., screen reader users, keyboard-only users, users with cognitive disabilities]
Key themes from user testing:
[List 3-5 key observations from user sessions]
Please draft a 3-paragraph executive summary that:
1. Opens with the overall compliance status and business risk (legal exposure, user abandonment).
2. Summarizes the most critical barriers and which user groups they affect.
3. Recommends immediate next steps and a timeline for remediation.
Keep the tone professional and factual. No jargon beyond WCAG references.