Run a Maestro-style accessibility audit for WCAG compliance, ARIA usage, keyboard navigation, and screen reader compatibility.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Maestro Accessibility Audit
Call `get_skill_content` with resources: ["architecture"].
## Protocol
Before delegating, call `get_skill_content` with resources: ["delegation"] and follow the returned methodology.
## Workflow
1. Define the accessibility audit scope and target conformance level (A, AA, AAA)
2. Identify UI components, pages, and interactive elements
3. Audit WCAG compliance: ARIA usage, keyboard navigation, focus management, color contrast, screen reader compatibility
4. Present findings with WCAG criterion reference, severity, user impact, location, and remediation code patterns
5. Note any manual verification gaps if the environment cannot exercise the UI directly
## Constraints
- Present findings before proposing remediation
- Do not modify code without explicit user approval
The line at the top of this page pins the label git:20260410.f5a5165, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_oc6apvbmytkwkv22
GET https://markdownregistry.com/api/v1/resolve?ref=josstei/maestro-orchestrate/a11y-audit
GET https://markdownregistry.com/api/v1/blob/e27c108fda380718cbd14764094ba787fbe767f3443ef385ab40af0ebf9b62f7
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
josstei/maestro-orchestrate · claude/skills/compliance-check/SKILL.md · Run a Maestro-style regulatory compliance review for GDPR/CCPA, cookie consent, data handling, and licensing
josstei/maestro-orchestrate · claude/skills/orchestrate/SKILL.md · Run the full Maestro workflow for complex engineering tasks that need a mandatory design dialogue, approved…
josstei/maestro-orchestrate · claude/skills/perf-check/SKILL.md · Run a Maestro-style performance assessment for hotspots, regressions, and optimization planning
josstei/maestro-orchestrate · claude/skills/resume-session/SKILL.md · Resume an interrupted Maestro session using the existing active-session file and shared phase tracking
plugin87/ux-ui-agent-skills · .claude/skills/a11y-audit/SKILL.md · Audit a UI or design against WCAG 2.2 AA/AAA and ARIA patterns, returning criterion-referenced findings with severity…
borghei/claude-skills · engineering/a11y-audit/SKILL.md · This skill should be used when the user asks to "check accessibility", "audit WCAG compliance", "scan HTML for a11y…
josstei/maestro-orchestrate · plugins/maestro/skills/a11y-audit/SKILL.md · Run a Maestro-style accessibility audit for WCAG compliance, ARIA usage, keyboard navigation, and screen reader…
arcasilesgroup/ai-engineering · skills/ai-verify/tiers/3-chain/a11y-audit/SKILL.md · Audit the UI for accessibility defects against WCAG 2.2 AA — semantic structure, keyboard operability, focus…
