Accessibility Audit (WCAG 2.2)
Audit and improve web accessibility following WCAG 2.2 guidelines
- What
- Audit and improve web accessibility following WCAG 2.2 guidelines
- Cost
- Free
- Needs
- none beyond a working agent; a rendered page and Lighthouse/axe tooling unlock the full live-audit workflow
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — an evidence-led accessibility audit workflow based on WCAG 2.2: run a live Lighthouse accessibility audit, localize issues from failed audit nodes, inspect the rendered accessibility tree, exercise flows with the keyboard, fix the source and re-verify — organized around the POUR principles (Perceivable, Operable, Understandable, Robust) with conformance levels A/AA/AAA, and an honest reminder that a Lighthouse score of 100 is not WCAG conformance. By @addyosmani, listed here with credit to its creator. Honest caveats: automated tools detect only a subset of barriers — real keyboard and screen-reader testing is still on you; the full live workflow needs a rendered page and audit tooling available to the agent. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Accessibility Audit is an audit workflow based on WCAG 2.2. It runs a Lighthouse audit, localizes issues from audit nodes, inspects the accessibility tree, keyboard-tests flows, fixes the source and re-verifies, POUR principles, Perceivable, Operable, Understandable and Robust, with levels A, AA and AAA. Note a Lighthouse score of 100 is not WCAG conformance, and automated tools detect some barriers.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit afa8da9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: none beyond a working agent; a rendered page and Lighthouse/axe tooling unlock the full live-audit workflow Install "Accessibility Audit (WCAG 2.2)" for me. Audit and improve web accessibility following WCAG 2.2 guidelines Repository: https://raw.githubusercontent.com/addyosmani/web-quality-skills/afa8da942115f2961fdbfa80807ea0b232ff6c00/skills/accessibility/SKILL.md Pinned version: install the code at commit afa8da942115f2961fdbfa80807ea0b232ff6c00 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the addyosmani-accessibility skill from the repository into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "addyosmani-accessibility". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- afa8da9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.