Skip to main content
MCP Prompts are user-controlled templates that generate structured messages for accessibility workflows. Unlike tools (which the LLM executes automatically), prompts are invoked directly by users and provide guided analysis with detailed output formats.

What Are Prompts?

Prompts are pre-configured workflows that:
  • Combine multiple tools in specific sequences
  • Provide structured, comprehensive reports
  • Include expert guidance and remediation plans
  • Generate actionable checklists and code examples
  • Are designed for common accessibility scenarios

Available Prompts

PromptDescriptionBest For
full-accessibility-auditComprehensive audit using axe-core, Pa11y, and LighthouseMajor releases, compliance reviews
quick-accessibility-checkFast check with critical issues summaryDevelopment, CI/CD pipelines
lighthouse-auditLighthouse score-focused accessibility auditScore tracking, Lighthouse insights
pre-deploy-checkVerify compliance with score threshold before deploymentDeployment gates, release checklists
quick-wins-reportHigh-impact, low-effort fixes from all three toolsSprint planning, quick improvements
lighthouse-score-improvementPhased plan to reach a target accessibility scoreScore improvement, sprint planning
contrast-checkColor contrast analysis with fix suggestionsDesign reviews, APCA evaluation
explain-wcag-criterionDeep dive into any WCAG criterionLearning, team training

How to Use Prompts

In Claude Desktop

  1. Click the prompts icon (📝) in the input area
  2. Select the desired prompt from the list
  3. Fill in the required arguments (URL, etc.)
  4. Submit to start the analysis

In Cursor

  1. Use the slash command format: /full-accessibility-audit
  2. Or access via the MCP prompts panel
  3. Provide the required arguments when prompted

Example Usage

Use the full-accessibility-audit prompt with:
- url: https://my-site.com
- wcagLevel: AA

Prompts vs Tools

ScenarioUse PromptUse Tool Directly
Comprehensive audit with structured reportfull-accessibility-audit
Deployment gate with GO/NO-GO decisionpre-deploy-check
Quick check during developmentquick-accessibility-check
Focused contrast analysis with fixescontrast-check
Score-focused Lighthouse auditlighthouse-audit
Improve score toward a targetlighthouse-score-improvement
Learning about WCAG criteriaexplain-wcag-criterion
Custom analysis with specific options✅ Use tools directly
Automated scripts or CI/CD✅ Use tools directly
Comparing tool outputsanalyze-mixed

Key Differences

Prompts:
  • Pre-configured workflows with guided output
  • Ideal for common tasks
  • User-controlled templates
  • Provide structured reports and remediation plans
Tools:
  • Direct access to analysis engines
  • Full parameter control
  • Best for automation and custom workflows
  • Raw data output

Workflow Categories

Audit Prompts

Comprehensive analysis workflows for evaluating accessibility:

Workflow Prompts

Action-oriented workflows for specific tasks:

Educational Prompts

Learning and documentation workflows:

When to Use Each Prompt

During Development

Use quick-accessibility-check for rapid feedback during coding

Before Release

Use full-accessibility-audit for comprehensive pre-release review

Sprint Planning

Use quick-wins-report to identify easy improvements

Score Tracking

Use lighthouse-audit to monitor accessibility metrics

Best Practices

Start with Quick Checks: Use quick-accessibility-check during development, then run full-accessibility-audit before major releases.
Track Your Score: Use lighthouse-audit regularly to monitor trends, and lighthouse-score-improvement when you need to reach a specific target.
Manual Review Required: Prompts identify automated issues, but manual testing is essential for complete accessibility compliance.

Build docs developers (and LLMs) love