Skip to content
Back to search

accesslint

MarketplaceWorks with Claude CodeGitHub

Web accessibility (a11y) tooling for Claude Code — WCAG 2.2 scanning, keyboard and screen-reader checks, WCAG-EM conformance audits, remediation, and CI regression diffing.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/accesslint--skills/badge.svg)](/listings/accesslint--skills)

HTML

<a href="/listings/accesslint--skills"><img src="/api/listings/accesslint--skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Any agent (skills CLI)

npx skills add AccessLint/skills

Installs the five skills. `accessibility-scan` and `accessibility-diff` work immediately (they shell out to [`@accesslint/cli`](https://www.npmjs.com/package/@accesslint/cli)). `accessibility-fix` needs the MCP server below; `accessibility-audit` and `accessibility-inspect` also use it for rule metadata (`list_rules` / `explain_rule`) when it's available.

Claude Code (plugin)

claude plugin marketplace add accesslint/skills
claude plugin install accesslint@accesslint

Adds the skills and the bundled MCP server together, and namespaces the skills as `accesslint:accessibility-scan` and so on.

MCP server on its own

{
  "mcpServers": {
    "accesslint": {
      "command": "npx",
      "args": ["-y", "@accesslint/mcp@latest"]
    }
  }
}

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 39 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "accesslint",
  3. "description": "Web accessibility (a11y) tooling for Claude Code — WCAG 2.2 scanning, keyboard and screen-reader checks, WCAG-EM conformance audits, remediation, and CI regression diffing.",
  4. "owner": {
  5. "name": "AccessLint",
  6. "email": "support@accesslint.com"
  7. },
  8. "plugins": [
  9. {
  10. "name": "accesslint",
  11. "displayName": "AccessLint — Accessibility (a11y)",
  12. "source": "./plugins/accesslint",
  13. "description": "Web accessibility (a11y) skills for Claude Code: audit a site for WCAG 2.2 conformance, scan a page with the rule engine, run hands-on keyboard and screen-reader checks, fix violations, and catch regressions in CI. Live-DOM audits auto-launch Chrome; no manual setup.",
  14. "version": "0.10.2",
  15. "author": {
  16. "name": "AccessLint",
  17. "email": "support@accesslint.com"
  18. },
  19. "homepage": "https://github.com/AccessLint/skills",
  20. "repository": "https://github.com/AccessLint/skills",
  21. "license": "MIT",
  22. "category": "code-quality",
  23. "keywords": [
  24. "accessibility",
  25. "a11y",
  26. "wcag",
  27. "wcag22",
  28. "screen-reader",
  29. "keyboard-navigation",
  30. "color-contrast",
  31. "aria",
  32. "section-508",
  33. "audit",
  34. "conformance",
  35. "inclusive-design"
  36. ]
  37. }
  38. ]
  39. }
README.md · README · 144 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # AccessLint — web accessibility (a11y) skills
  2. Agent Skills for finding and fixing web accessibility issues, powered by [`@accesslint/core`](https://github.com/AccessLint/accesslint/tree/main/core). They cover the WCAG 2.2 audit workflow end to end: automated scanning, hands-on keyboard and screen-reader checks, WCAG-EM conformance auditing, remediation, and regression diffing.
  3. Works with any agent the [skills CLI](https://www.skills.sh) supports — Claude Code, Cursor, Codex, Copilot, Windsurf, Gemini, Cline, Amp, and more.
  4. **Keywords:** accessibility · a11y · WCAG 2.2 · Section 508 · screen reader · keyboard navigation · color contrast · ARIA · inclusive design
  5. ## The skills
  6. Five skills, each with one responsibility. Each finding is graded on two axes — severity (user impact) and evidence basis (● verified · ◐ confirm with a human · ○ human-required).
  7. | Skill | Scope | Does |
  8. |---|---|---|
  9. | `accessibility-scan` | one page | Runs the rule engine against the live DOM. Returns a worklist: selector, `file:line (symbol)` where source mapping is available, evidence, fix directive. Locates; doesn't edit. |
  10. | `accessibility-inspect` | one page | Drives the page through what the engine can't decide: keyboard and focus order, names/roles/states, reflow and zoom, reduced motion, form errors, target size. Assesses; doesn't edit. |
  11. | `accessibility-audit` | whole site | WCAG-EM: defines scope, samples representative pages and flows, runs the other two per page, reports per-criterion conformance as pass, fail, or undetermined. |
  12. | `accessibility-fix` | a target or worklist | Baseline, edit, verify. Applies mechanical fixes as given; leaves `TODO`s for visual or contextual judgment. Only fixes. |
  13. | `accessibility-diff` | a change | Diffs a page against a baseline — uncommitted changes by default, or a branch. Reports only what the change introduced or fixed. |
  14. ```
  15. LOCATE ASSESS REMEDIATE GUARD
  16. accessibility-scan (automated) ┐
  17. ├─► accessibility-audit ─► accessibility-fix ─► accessibility-diff
  18. accessibility-inspect (manual) ┘ (WCAG-EM) (edit→verify) (regression)
  19. ```
  20. The methodology they follow — WCAG-EM, the two grading axes, the boundary against standing in for real assistive-technology users — is in [`plugins/accesslint/skills/shared/methodology.md`](plugins/accesslint/skills/shared/methodology.md).
  21. ## Install
  22. ### Any agent (skills CLI)
  23. ```bash
  24. npx skills add AccessLint/skills
  25. ```
  26. Installs the five skills. `accessibility-scan` and `accessibility-diff` work immediately (they shell out to [`@accesslint/cli`](https://www.npmjs.com/package/@accesslint/cli)). `accessibility-fix` needs the MCP server below; `accessibility-audit` and `accessibility-inspect` also use it for rule metadata (`list_rules` / `explain_rule`) when it's available.
  27. ### Claude Code (plugin)
  28. ```bash
  29. claude plugin marketplace add accesslint/skills
  30. claude plugin install accesslint@accesslint
  31. ```
  32. Adds the skills and the bundled MCP server together, and namespaces the skills as `accesslint:accessibility-scan` and so on.
  33. ### MCP server on its own
  34. ```json
  35. {
  36. "mcpServers": {
  37. "accesslint": {
  38. "command": "npx",
  39. "args": ["-y", "@accesslint/mcp@latest"]
  40. }
  41. }
  42. }
  43. ```
  44. ## Use
  45. Ask in plain language — "audit this site for accessibility", "is localhost:3000 accessible", "fix the a11y issues in Nav.tsx" — or invoke a skill directly if your agent supports slash commands:
  46. ```
  47. /accessibility-scan http://localhost:3000/dashboard
  48. /accessibility-audit --level AA http://localhost:3000/
  49. /accessibility-diff --branch main
  50. ```
  51. Every skill takes a URL, a named target from `accesslint.config.json`, or nothing (the default target). Run `npx @accesslint/cli init` to set targets up once, then drop the URL.
  52. | Flag | Skills | Purpose |
  53. |---|---|---|
  54. | `--selector <css>` | scan, inspect, audit, diff | Scope to one component |
  55. | `--wait-for <css>` | scan, inspect, audit, diff | Gate on async content or a rebuild |
  56. | `--include-aaa` | scan, diff | Include AAA rules |
  57. | `--disable <rules>` | scan | Skip specific rules |
  58. | `--level AA\|AAA` | audit | Conformance target (default AA) |
  59. | `--deep` | inspect | Drive every triggered checkpoint through its full procedure (default is the lean ledger pass) |
  60. | `--branch [<name>]` | diff | Diff against a branch instead of uncommitted changes |
  61. ## Requirements
  62. Most a11y violations only appear after JS runs, so these skills work against a rendered page. `scan`, `diff`, `audit`, and `fix` reach the live DOM over CDP, auto-launching Chrome when no debug session is reachable — no setup.
  63. `accessibility-inspect` drives the page, which needs a browser MCP (`chrome-devtools`, Playwright, or Puppeteer). Without one it runs the static checks and hands off the rest. In Claude Code:
  64. ```bash
  65. claude mcp add chrome-devtools npx -- -y chrome-devtools-mcp@latest
  66. ```
  67. For a page behind a login, start a headed debuggable Chrome (`npx @accesslint/chrome ensure --headed`) and sign in there; `accessibility-fix` attaches to that session instead of launching its own.
  68. ## MCP tools
  69. The plugin bundles [`@accesslint/mcp`](https://github.com/AccessLint/accesslint/tree/main/mcp), which backs `accessibility-fix`'s baseline and verify runs and supplies rule metadata. The tools are also callable directly.
  70. | Tool | Purpose |
  71. |---|---|
  72. | `audit_live` | Live-DOM audit over CDP; auto-launches Chrome if needed |
  73. | `audit_html` | Audit an HTML string or file |
  74. | `list_rules` | List the active rule set |
  75. | `explain_rule` | One rule in full: WCAG criterion, fixability, remediation guidance |
  76. Installed standalone they are `mcp__accesslint__<tool>`; installed as a Claude Code plugin, `mcp__plugin_accesslint_accesslint__<tool>`.
  77. ## The hosted connector
  78. The server this plugin bundles runs on your machine. It drives a Chrome you can watch, reaches
  79. `localhost`, staging and production alike, and keeps nothing — each call audits and returns.
  80. [AccessLint's hosted connector](https://mcp.accesslint.com/mcp) is a different server for the
  81. work that needs memory: a **user journey** across several pages, a site **re-checked over time**,
  82. findings that **persist**, and a **report** someone else can read. There those are flows, runs and
  83. violations. You add it in a chat client — Claude.ai, ChatGPT, or any MCP client — as a custom
  84. connector rather than installing it from npm, and it signs you in to an
  85. [accesslint.com](https://www.accesslint.com) account:
  86. ```
  87. https://mcp.accesslint.com/mcp
  88. ```
  89. It cannot reach `localhost`. Both servers register under the name `accesslint`; this is the one
  90. with a way into your dev server.
  91. ## WCAG coverage
  92. Level A and AA — perceivable (alt text, contrast, structure), operable (keyboard, focus), understandable (labels, language), robust (ARIA, accessible names). AAA rules are opt-in via `--include-aaa`. Run `list_rules` for the active set in your installed version.
  93. The engine catches what is mechanically detectable. Content clarity, announcement quality, keyboard-flow coherence, and lived experience need a person — these skills name and hand those off rather than guessing at them.
  94. ## Resources
  95. - [WCAG 2.2 Guidelines](https://www.w3.org/WAI/WCAG22/quickref/)
  96. - [WCAG-EM evaluation methodology](https://www.w3.org/TR/WCAG-EM/)
  97. - [WAI-ARIA Authoring Practices](https://www.w3.org/WAI/ARIA/apg/)
  98. - [`@accesslint/mcp` on npm](https://www.npmjs.com/package/@accesslint/mcp)
  99. - [AccessLint hosted MCP connector](https://mcp.accesslint.com/mcp) — flows, runs and violations for a deployed site
  100. ## License
  101. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.