Skip to main content
Fast accessibility check using axe-core with summary of critical issues.

​
Description

This prompt performs a rapid accessibility scan of a web page, focusing on the most important issues. It provides a concise summary with quick fixes and next steps, ideal for development workflows. Best for: Quick sanity checks during development or CI/CD pipelines.

​
Arguments

ArgumentTypeRequiredDefaultDescription
urlstring✅-URL of the page to analyze

​
Example Usage

​
Basic Usage

Use the quick-accessibility-check prompt for https://staging.my-site.com

​
Natural Language

Do a quick accessibility check on https://example.com

​
Output Includes

The prompt generates a concise report with:

​
1. Summary by Severity

Quick count of issues by severity level:
  • Critical issues requiring immediate attention
  • Serious issues that should be fixed soon
  • Moderate issues for backlog tracking

​
2. Critical & Serious Issues

List with quick fix suggestions for each issue:
  • Issue description
  • Affected element/location
  • Quick fix recommendation

​
3. Next Steps

Recommendations for further analysis if needed

​
Example Output Structure

## Quick Accessibility Check: example.com

### Summary
- ❌ Critical: 2
- ⚠️ Serious: 3
- ℹ️ Moderate: 5

### Critical Issues (Fix Immediately)

1. **Missing form labels** (2 instances)
   - Location: Contact form
   - Quick fix: Add `<label>` elements or `aria-label` attributes

2. **Images without alt text** (1 instance)
   - Location: Header logo
   - Quick fix: Add descriptive `alt` attribute

### Serious Issues

1. **Insufficient color contrast** (3 elements)
   - Quick fix: Increase contrast ratio to at least 4.5:1

### Next Steps
- Run `full-accessibility-audit` for detailed remediation plan
- Use `contrast-check` for color-specific fixes

​
When to Use

ScenarioRecommended
During development✅ Yes
Pull request review✅ Yes
Quick sanity check✅ Yes
Compliance documentationUse full-accessibility-audit instead
Pre-deployment gateUse pre-deploy-check instead
This prompt uses only axe-core for speed. For comprehensive coverage, use full-accessibility-audit which includes Pa11y and Lighthouse.

​
Speed vs Coverage

Aspectquick-accessibility-checkfull-accessibility-audit
Toolsaxe-core onlyaxe-core + Pa11y + Lighthouse
SpeedFast (~5-10 seconds)Slower (~30-60 seconds)
CoverageCore WCAG issuesComprehensive
OutputConcise summaryDetailed report
Best forDevelopment, PR reviewsReleases, compliance

​
What Gets Checked

  • Missing alt text on images
  • Form inputs without labels
  • Insufficient color contrast
  • Invalid ARIA attributes
  • Keyboard accessibility problems
  • Missing document language
  • Heading hierarchy problems
  • Link purpose issues
  • Missing skip links
  • Form validation errors
  • Redundant ARIA
  • Minor contrast issues
  • Non-critical semantic problems

​
Technical Details

This prompt internally executes: 
axe-core({
  url: "<your-url>"
})
Only automated issues are detected. Manual testing is still required for complete accessibility compliance.

​
Integration Examples

​
GitHub Actions

name: Accessibility Check

on: [pull_request]

jobs:
  a11y:
    runs-on: ubuntu-latest
    steps:
      - name: Quick A11y Check
        run: |
          # Use quick-accessibility-check prompt
          # Fail if critical issues found

​
Pre-commit Hook

#!/bin/bash
# Run quick accessibility check before committing
echo "Running accessibility check..."
# Execute quick-accessibility-check prompt

Full Accessibility Audit

More comprehensive analysis with all three tools

Pre-Deploy Check

Deployment-focused with GO/NO-GO decision

Quick Wins Report

Focus on easy fixes across all tools

Lighthouse Audit

Score-focused analysis
  • axe-core - Direct axe-core tool access

Build docs developers (and LLMs) love

Get started for freeTalk to us