Skip to main content
Verify accessibility compliance before deployment using axe-core, Pa11y, and Lighthouse with clear GO/NO-GO decision.

​
Description

This prompt performs a deployment-focused accessibility check using all three analysis tools, providing a clear GO/NO-GO decision based on both critical issues and the Lighthouse accessibility score. It includes a minimum score threshold gate, identifies blocking vs non-blocking issues, and provides a risk assessment for deployment. Best for: Deployment gates, release checklists, and compliance verification.

​
Arguments

ArgumentTypeRequiredDefaultDescription
urlstring✅-URL of the staging/pre-production page
minScorenumber90Minimum Lighthouse accessibility score to pass (0-100)

​
Example Usage

​
Basic Usage

Use the pre-deploy-check prompt for https://staging.my-app.com

​
With Custom Score Threshold

Use the pre-deploy-check prompt with:
- url: https://staging.my-app.com
- minScore: 95

​
Natural Language

Check if https://staging.my-site.com is ready to deploy from an accessibility standpoint

​
Output Includes

The prompt generates a deployment-focused report with:

​
1. GO/NO-GO Decision

Clear deployment recommendation based on both Lighthouse score and issues: | Decision | Meaning | |----------|---------|| | ✅ GO | Lighthouse score >= threshold AND no critical/serious issues | | ⚠️ GO WITH CAUTION | Score >= threshold with minor issues, OR score slightly below threshold with no critical issues | | ❌ NO-GO | Score well below threshold OR critical/serious issues found |

​
2. Lighthouse Score Gate

  • Current score vs threshold
  • PASS/FAIL result
  • Key failing audits

​
3. Blocking Issues

Critical problems from all three tools that must be fixed before deployment

​
4. Non-Blocking Issues

Issues to track in backlog but don’t block deployment

​
5. Compliance Summary

  • Lighthouse score
  • WCAG 2.1 Level AA conformance status
  • Issues grouped by WCAG principle

​
6. Risk Assessment

Deployment risk level with recommendations
  • For NO-GO: Score-improvement suggestions
  • For GO: Post-deployment fixes to track

​
Example Output Structure

## Pre-Deploy Accessibility Check

### 🚦 Deployment Decision: ⚠️ GO WITH CAUTION

---

### Lighthouse Score Gate
- **Score**: 91/100 — Good
- **Threshold**: 90
- **Result**: ✅ PASS

### Summary
- **Critical Issues**: 0
- **Serious Issues**: 2
- **Moderate Issues**: 4

### Blocking Issues
None - no critical accessibility violations detected and score meets threshold.

### Non-Blocking Issues (Track in Backlog)

#### Serious (2)

1. **Insufficient contrast on footer links**
   - Impact: Low-vision users may struggle to read
   - Risk: Low - affects non-critical content
   - Detected by: axe-core, Lighthouse
   - Track as: JIRA-1234

2. **Missing skip-to-content link**
   - Impact: Keyboard users must tab through navigation
   - Risk: Medium - affects keyboard navigation
   - Detected by: Pa11y
   - Track as: JIRA-1235

### Compliance Summary
- **Lighthouse Accessibility Score**: 91/100
- **Perceivable**: ⚠️ 2 issues
- **Operable**: ✅ Pass
- **Understandable**: ✅ Pass
- **Robust**: ✅ Pass

### Risk Assessment
**Low Risk** - Score exceeds threshold and issues are non-critical.
Recommend deploying with issues tracked in backlog for next sprint.

### Recommended Actions
1. ✅ Review and accept non-blocking issues
2. ✅ Create tickets for backlog items
3. Target score of 95 for next deployment cycle

​
Decision Logic

Criteria:
  • Lighthouse score >= minimum threshold
  • No critical issues from any tool
  • No serious issues, OR only minor serious issues in non-critical areas
Action: Deploy and track minor issues in backlog
Criteria:
  • Score meets threshold but has some serious issues
  • OR score slightly below threshold (1-3 points) with no critical issues
Action: Deploy but prioritize fixes in next sprint
Criteria:
  • Score well below threshold (>3 points)
  • OR any critical issues detected
  • OR multiple serious issues affecting core functionality
Action: Fix blocking issues before deploying

​
When to Use

ScenarioRecommended
Before production deployment✅ Yes
Release gate check✅ Yes
Staging environment review✅ Yes
During developmentUse quick-accessibility-check instead
Comprehensive auditUse full-accessibility-audit instead
This prompt makes a deployment recommendation based on automated testing only. Manual accessibility testing should still be part of your release process.

​
Workflow Integration

​
CI/CD Pipeline Example

# GitHub Actions example
name: Pre-Deploy Accessibility Gate

on:
  pull_request:
    branches: [main]

jobs:
  accessibility:
    runs-on: ubuntu-latest
    steps:
      - name: Deploy to Staging
        run: npm run deploy:staging
      
      - name: Accessibility Check
        run: |
          # Use pre-deploy-check prompt via MCP
          # Parse decision from output
          # Fail pipeline if NO-GO
      
      - name: Block Deployment on NO-GO
        if: failure()
        run: |
          echo "Accessibility check failed - deployment blocked"
          exit 1

​
Release Checklist

## Release Checklist

- [ ] Code review approved
- [ ] Tests passing
- [ ] **Pre-deploy accessibility check: GO** ✅
- [ ] Security scan passed
- [ ] Deploy to production

​
Technical Details

This prompt internally executes: 
// Step 1: Run axe-core + Pa11y
analyze-mixed({
  url: "<your-url>",
  tools: ["axe-core", "pa11y"],
  options: {
    wcagLevel: "AA",
    deduplicateResults: true
  }
})

// Step 2: Run Lighthouse with score threshold
analyze-with-lighthouse({
  url: "<your-url>",
  options: {
    wcagLevel: "AA"
  }
})

// Step 3: Compare score to threshold and evaluate issues
Set your minScore threshold based on your organization’s accessibility standards. Common values: 85 (minimum), 90 (recommended), 95 (excellent).

​
Customizing Thresholds

ThresholdMeaningRecommended For
85Minimum acceptableInternal tools, early-stage products
90Industry standardPublic-facing websites, SaaS products
95High complianceGovernment, healthcare, finance, education
98ExcellenceAccessibility-focused products

Quick Accessibility Check

Faster check for development

Full Accessibility Audit

Comprehensive audit with remediation

Lighthouse Score Improvement

Plan to reach a target score

Quick Wins Report

Identify easy fixes

Build docs developers (and LLMs) love

Get started for freeTalk to us