Writing clear, specific prompts helps you get better accessibility analysis results. This guide shows you how to craft prompts that return actionable insights.
Good Prompts Specific with Context Analyze the checkout page at https://store.com/checkout and prioritize issues affecting screen reader users
Result: You’ll get issues filtered and prioritized for screen reader users, making it easier to focus on the most critical improvements for that audience.With Clear Constraints Give me only critical issues (severity: critical) from https://example.com that have low remediation effort (remediationEffort: low)
Result: A short list of high-impact issues that can be fixed quickly, perfect for sprint planning.Request Interpretation Analyze https://form.com and explain which are the 3 most urgent problems to solve and why
Result: Curated analysis with business context, helping you make informed decisions about what to fix first.With Business Objectives We're launching the site in 2 days. Analyze https://pre-prod.com and tell me which issues I MUST fix before launch
Result: A GO/NO-GO decision with critical blockers clearly identified.Section-Specific Analysis Check only the header contrast of my page at https://example.com
Result: Focused analysis on one component, making results easier to act on and verify.Educational Focus Analyze https://demo.com and explain in detail the WCAG 1.1.1 issue (Non-text content): - Which users it affects - Real example of how it impacts them - How to fix it step by step
Result: Educational explanation with context, perfect for team training or understanding complex issues.Prompts That Can Be Improved Too Vague Problems:
No URL provided
Too broad
No actionable criteria
Binary yes/no doesn’t help
Analyze the accessibility of https://my-site.com and summarize the main issues by severity
Improvements:
Specific URL
Asks for analysis, not yes/no
Requests organized output (by severity)
Actionable
No Action Context Analyze https://example.com
Problems:
No goal stated
No guidance on what to do with results
Unclear what you’re optimizing for
Analyze https://example.com and create a prioritized list of fixes I can complete this sprint
Improvements:
Clear goal (sprint planning)
Asks for prioritization
Time-bound scope
Ready for action
Mixing Analysis Types Analyze https://example.com and also src/components/*.vue
Problems:
Mixing live URL with source files
Different analysis types
Unclear priority
Do two separate analyses: 1. Analyze the accessibility of https://example.com 2. Review src/components/*.vue for accessibility patterns
Improvements:
Separated concerns
Clear sequence
Each analysis is focused
Missing URL Check the contrast of my page
Problems:
No URL
“my page” is ambiguous
Can’t be executed
Check the contrast of https://my-site.com/landing-page
Improvements:
Specific URL
Can be executed immediately
Clear target
Overly Broad Find all accessibility problems everywhere
Problems:
No target specified
“Everywhere” is impossible
No prioritization
Overwhelming results
Analyze https://my-site.com with all available tools and group issues by WCAG principle
Improvements:
Specific target
Uses all tools for coverage
Organized output (by WCAG principle)
Manageable scope
Best Practices 1. Be Specific About What You Want
❌ Vague “Check my site” “Find problems” “Is it accessible?”
✅ Specific “Analyze https://example.com ” “List critical and serious issues” “Does it meet WCAG AA requirements?“ 2. Provide Context Include relevant information:
What to analyze ✅ URL: https://my-site.com/page ✅ HTML: Paste HTML snippet directly ❌ “My homepage” (ambiguous)
Which users to prioritize ✅ “Focus on screen reader users” ✅ “Prioritize keyboard navigation issues” ✅ “Check for color blind users”
When fixes are needed ✅ “Launching in 2 days” ✅ “Planning next sprint” ✅ “Long-term backlog review”
Specific sections or components ✅ “Only the checkout flow” ✅ “Just the header component” ✅ “Focus on the dashboard”
3. Request Structured Output Ask for organization that helps you take action:
By Priority and Effort
By User Impact
By WCAG Level
Group issues by: 1. Critical + low effort (fix today) 2. High + low effort (fix this week) 3. Everything else by WCAG principle
4. Use MCP Prompts for Common Tasks For standard workflows, use the built-in MCP prompts:
Task MCP Prompt When to Use Full audit before release full-accessibility-auditPre-deployment Quick check during development quick-accessibility-checkFeature branches Deployment decision pre-deploy-checkGO/NO-GO decision Color contrast review contrast-checkDesign QA Sprint planning quick-wins-reportBacklog grooming Learning about WCAG explain-wcag-criterionTeam education Lighthouse scoring lighthouse-auditTracking metrics Score improvement plan lighthouse-score-improvementSetting goals
Usage: Use the pre-deploy-check prompt for https://staging.my-site.com
MCP prompts provide consistent, well-structured output for common scenarios.
5. Iterate Based on Results Start broad, then narrow down:
Initial broad analysis
Analyze https://my-site.com with all tools
Focus on critical issues
Focus on the 5 critical issues and suggest fixes
Deep dive on specific issue
Explain the color-contrast issue in detail with code examples
Verify fixes
Re-check the contrast after applying the suggested fixes
Prompt Templates Copy and customize these templates:
Development Check Analyze https://[your-site]/[page] and show me: 1. Critical issues that block functionality 2. Quick wins (high priority + low effort) 3. Grouped by WCAG principle
Sprint Planning Analyze https://[your-site] and create a prioritized list of: - High/critical priority issues - With low/medium remediation effort - That can be completed in a 2-week sprint
Pre-Deployment We're deploying https://[staging-url] tomorrow. Show me critical issues that would block the release. Focus on WCAG Level A violations.
Contrast Check Check the color contrast of https://[your-site] for WCAG [AA/AAA] compliance. Suggest color fixes that maintain brand colors as much as possible.
Learning / Training Analyze https://[example-site] and: 1. Find examples of [specific issue type] 2. Explain why it's a problem 3. Show how it impacts [specific user group] 4. Provide step-by-step fix with code examples
Comparison Compare the accessibility of: 1. Current production: https://[prod-url] 2. New version: https://[staging-url] What improved? What regressed?
Advanced Prompt Techniques Filtering and Sorting Analyze https://my-site.com and show me: - Only severity: critical or serious - Affecting: screen-reader users - WCAG Level: A or AA - Sorted by: remediationEffort (low first)
Conditional Logic Analyze https://my-site.com. If Lighthouse score > 90: show me areas for AAA compliance If Lighthouse score < 90: show me issues preventing a 90+ score
Multi-Step Analysis 1. Run full analysis on https://my-site.com 2. Identify the 3 most impactful issues by affected user count 3. For each issue, provide: - WCAG explanation - Code example showing the problem - Code example showing the fix - Estimated time to fix 4. Create a GitHub issue template for each
Comparison with Context We redesigned our homepage. Compare: - Old: https://my-site.com/old-homepage - New: https://my-site.com/new-homepage Did we introduce any new accessibility issues? What improved?
Workflows Recommended workflows for common tasks
Interpreting Results How to prioritize findings
Prompts Reference Available MCP prompts
MCP Server Concepts Understanding MCP tools and prompts
