ワンクリックでManusで任意のスキルを実行

a11y-scan

スター0

フォーク0

更新日2026年3月18日 09:46

"Run automated accessibility scan using axe-core via Playwright. Captures WCAG violations, tracks progress over time. Use when asked to "scan for accessibility", "run axe", or "check a11y automatically"."

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

badass-courses

badass-courses/a11y-agent

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Process

Check if Playwright and @axe-core/playwright are available (npx playwright --version)
If not installed, suggest: npm install -D @axe-core/playwright playwright && npx playwright install chromium
Generate the scan script from reference/axe-scan.md and write to a temp file
Execute the scan against the target URL
Parse results into severity categories (critical, serious, moderate, minor)
If previous scan results exist in a11y-scan-results/, compare and note changes
Store results in a11y-scan-results/YYYY-MM-DD.json
Present human-readable report with fix suggestions per violation

What Automated Scans Catch (30-50% of issues)

Can detect:

Missing alt text, labels, ARIA attributes
Color contrast violations (computed styles)
Duplicate IDs, missing lang, landmark issues
Invalid ARIA roles and attributes
Missing form labels

Cannot detect:

Keyboard operability (use a11y-test or manual testing)
Focus management logic (does focus return on close?)
Screen reader UX quality (is the reading order logical?)
Whether heading hierarchy is logical (only structural validity)
Whether alt text is meaningful (only that it exists)
Dynamic state issues (only tests what's rendered at scan time)

Always pair with manual testing via a11y-audit.

Scan Tips

Scan with menus/modals open — axe only tests what's rendered on screen
Scope rules with {{scope}} to reduce noise from known third-party widget issues
Run scans at multiple viewport sizes to catch responsive accessibility issues
For CI integration, use cy.checkA11y() at the integration test level — see a11y-test
Compare scan results over time to track remediation progress

このリポジトリの他の Skills

同じリポジトリ

a11y-advocate

badass-courses/a11y-agent

Build accessibility culture and communicate with stakeholders. Generate statements, prioritize issues, write tickets, create team checklists, produce risk assessments. Use when asked to "prioritize a11y", "accessibility statement", "convince PM about a11y", or "create testing process".

2026-03-180

a11y-agent

badass-courses/a11y-agent

Accessibility expertise for building inclusive web interfaces. Covers semantic HTML, ARIA, keyboard interaction, screen reader support, color contrast, focus management, responsive zoom, motion safety, automated testing, and organizational culture. Use when building or reviewing any web UI to ensure it works for everyone.

2026-03-180

a11y-audit

badass-courses/a11y-agent

Structured accessibility assessment following a structured testing order. Asks targeted questions, walks through keyboard → tools → contrast → zoom → screen readers, produces prioritized report with WCAG references. Use when asked to "check accessibility", "audit a11y", "test accessibility", or before shipping UI.

2026-03-180

a11y-component

badass-courses/a11y-agent

Scaffold accessible interactive components with correct ARIA, keyboard handling, and focus management. Supports modal, menu, tabs, accordion (v1), plus date picker, combobox, slideshow (v2). Use when building these from scratch.

2026-03-180

a11y-fix

badass-courses/a11y-agent

"Fix accessibility issues in current code. Works through findings from a11y-audit, a11y-scan, or a11y-review. Makes changes, explains rationale, notes what to test manually. Use when asked to "fix accessibility", "make this accessible", or after any a11y assessment."

2026-03-180

a11y-review

badass-courses/a11y-agent

Lightweight code review pass for accessibility. Checks markup, event handlers, ARIA, test coverage in changed files. Use for PR reviews, pre-merge checks, or when asked to "review for accessibility". For comprehensive assessment, use a11y-audit instead.

2026-03-180

name	a11y-scan
description	"Run automated accessibility scan using axe-core via Playwright. Captures WCAG violations, tracks progress over time. Use when asked to "scan for accessibility", "run axe", or "check a11y automatically"."

Run an automated accessibility scan on {{url}} scoped to {{scope}} if specified.

→ Consult the a11y-agent skill for accessibility standards and patterns.

Process

Check if Playwright and @axe-core/playwright are available (npx playwright --version)
If not installed, suggest: npm install -D @axe-core/playwright playwright && npx playwright install chromium
Generate the scan script from reference/axe-scan.md and write to a temp file
Execute the scan against the target URL
Parse results into severity categories (critical, serious, moderate, minor)
If previous scan results exist in a11y-scan-results/, compare and note changes
Store results in a11y-scan-results/YYYY-MM-DD.json
Present human-readable report with fix suggestions per violation

What Automated Scans Catch (30-50% of issues)

Can detect:

Missing alt text, labels, ARIA attributes
Color contrast violations (computed styles)
Duplicate IDs, missing lang, landmark issues
Invalid ARIA roles and attributes
Missing form labels

Cannot detect:

Keyboard operability (use a11y-test or manual testing)
Focus management logic (does focus return on close?)
Screen reader UX quality (is the reading order logical?)
Whether heading hierarchy is logical (only structural validity)
Whether alt text is meaningful (only that it exists)
Dynamic state issues (only tests what's rendered at scan time)

Always pair with manual testing via a11y-audit.

Scan Tips

Scan with menus/modals open — axe only tests what's rendered on screen
Scope rules with {{scope}} to reduce noise from known third-party widget issues
Run scans at multiple viewport sizes to catch responsive accessibility issues
For CI integration, use cy.checkA11y() at the integration test level — see a11y-test
Compare scan results over time to track remediation progress