Agent skill

Accessibility Inspect

by AccessLint in AccessLint/skills

One page, hands-on manual tier — drive a live page through the web accessibility (a11y) checks a rule engine can't decide: keyboard operation and focus order, screen-reader names, roles and states…

No licenceAuto-check: notesFrontend & Design

Install Accessibility Inspect

skills CLI
$ npx skills add AccessLint/skills --skill accessibility-inspect -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AccessLint/skills accessibility-inspect --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AccessLint/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/accesslint/skills/accessibility-inspect .claude/skills/accessibility-inspect && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
accessibility-inspect
GitHub stars
103
Used in
1 other repo
Token cost
~3k tokens
SKILL.md length
1,348 words
Files
2 (incl. references)
Skills in repo
5
Repo updated
First seen
Licence
None found

At a glance

One page, hands-on manual tier — drive a live page through the web accessibility (a11y) checks a rule engine can't decide: keyboard operation and focus order, screen-reader names, roles and states…

  • Keyboard testing
  • SKILL.md covers Grading, The ledger — a denominator,…, Evidence budget — cap spend by… and Prerequisite: a browser to drive, plus 5 more sections
  • Calls claude and npx
  • Focus-order checks

What it does

Accessibility Inspect is an agent skill from AccessLint/skills. One page, hands-on manual tier — drive a live page through the web accessibility (a11y) checks a rule engine can't decide: keyboard operation and focus order, screen-reader names, roles and states from the accessibility tree, reflow and zoom, reduced motion, form errors, and target size. Grades each finding by evidence basis (verified / confirm-with-a-human / human-required) and severity, and closes every criterion in a ledger: verified, flagged, not exercised, or N/A. Locates and assesses; does not fix (use…

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/checkpoints.md`).

It sits in Frontend & Design, covering Accessibility.

When your agent uses it

  • Keyboard testing
  • Focus-order checks
  • A11y-tree review
  • Reflow and zoom at 200%

Example prompts

  • “is this operable, not just lint-clean”
  • “/accessibility-inspect”

Requirements

  • Node.js
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Bash, Skill, mcp__chrome-devtools__take_snapshot, mcp__chrome-devtools__take_screenshot, mcp__chrome-devtools__press_key, mcp__chrome-devtools__click, mcp__chrome-devtools__hover, mcp__chrome-devtools__fill, mcp__chrome-devtools__fill_form, mcp__chrome-devtools__resize_page, mcp__chrome-devtools__emulate, mcp__chrome-devtools__evaluate_script, mcp__chrome-devtools__navigate_page, mcp__chrome-devtools__new_page, mcp__chrome-devtools__list_pages, mcp__chrome-devtools__select_page, mcp__chrome-devtools__wait_for, mcp__plugin_accesslint_accesslint__explain_rule

What it can do on your machine

Read from SKILL.md and the folder at commit 2e9d733. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Bash
    • Skill
    • mcp__chrome-devtools__take_snapshot
    • mcp__chrome-devtools__take_screenshot
    • mcp__chrome-devtools__press_key
    • mcp__chrome-devtools__click
    • mcp__chrome-devtools__hover

    …and 11 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • claude
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Accessibility Inspect loads about 3k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 202 tokens; SKILL.md has 1,348 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~202
When it runs · the whole SKILL.md, loaded when a task matches
~3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Glob, Grep, Bash, Skill, mcp__chrome-devtools__take_snapshot, mcp__chrome-devtools__take_scree

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 1,348 words (~3,017 tokens).

“This is the semi-automated manual tier of a WCAG assessment: the checks that need interaction (keyboard, focus, state changes, reflow) or human review (focus visibility, error recovery, reading order), which a static rule engine can't decide. Work against the running…”

— opening of SKILL.md by AccessLint
name
accessibility-inspect
allowed-tools
Read, Glob, Grep, Bash, Skill, mcp__chrome-devtools__take_snapshot, mcp__chrome-devtools__take_screenshot, mcp__chrome-devtools__press_key, mcp__chrome-devtools__click, mcp__chrome-devtools__hover, mcp__chrome-devtools__fill, mcp__chrome-devtools__fill_form, mcp__chrome-devtools__resize_page, mcp__chrome-devtools__emulate, mcp__chrome-devtools__evaluate_script, mcp__chrome-devtools__navigate_page, mcp__chrome-devtools__new_page, mcp__chrome-devtools__list_pages, mcp__chrome-devtools__select_page, mcp__chrome-devtools__wait_for, mcp__plugin_accesslint_accesslint__explain_rule
argument-hint
[target|url] [--selector <css>] [--wait-for <css>] [--deep]

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file (references) in plugins/accesslint/skills/accessibility-inspect of AccessLint/skills.

  • SKILL.md
  • references/checkpoints.md

Open the folder on GitHubat commit 2e9d733

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in AccessLint/skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Accessibility Inspect next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Accessibility Inspect compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Accessibility Inspect this skillAccessLint/skills1031 repos~3kAutomated safety check: NotesNone
Web Interface Guidelines Reviewervercel-labs/openreview1.7k98 repos~308Automated safety check: PassNone
Accessibility Reviewmarkmead/hyperui12k1 repos~1.1kAutomated safety check: PassMIT
Web Animation DesignbaptisteArno/typebot.io11k2 repos~2.7kAutomated safety check: PassCustom licence
Accessibility Fixeribelick/ui-skills9.5k4 repos~1.2kAutomated safety check: PassMIT
Wcag Audit PatternsvmDeshpande/ai-agent-automation17811 repos~610Automated safety check: PassApache-2.0

Similar skills

  • Web Interface Guidelines Reviewer

    vercel-labs/openreview

    Official

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…

    1.7k GitHub starsUsed in 98 repos~308 tokens
    Frontend & DesignAuto-check passed
  • Accessibility Review

    markmead/hyperui

    Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.

    12k GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed
  • Web Animation Design

    baptisteArno/typebot.io

    Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.

    11k GitHub starsUsed in 2 repos~2.7k tokens
    Frontend & DesignAuto-check passed
  • Accessibility Fixer

    ibelick/ui-skills

    Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.

    9.5k GitHub starsUsed in 4 repos~1.2k tokens
    Frontend & DesignAuto-check passed
  • Wcag Audit Patterns

    vmDeshpande/ai-agent-automation

    Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.

    178 GitHub starsUsed in 11 repos~610 tokens
    Frontend & DesignAuto-check passed
  • Baseline UI

    ibelick/ui-skills

    Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.

    9.5k GitHub starsUsed in 8 repos~855 tokens
    Frontend & DesignAuto-check passed

More from AccessLint/skills

  • Accessibility Audit

    AccessLint/skills

    Whole site or product — a full web accessibility (a11y) audit against WCAG 2.2, following the WCAG-EM methodology.

    103 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check: notes
  • Accessibility Diff

    AccessLint/skills

    Regression check — diff a live page's web accessibility (a11y) violations against a baseline.

    103 GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check: notes
  • Accessibility Scan

    AccessLint/skills

    One page, automated tier — run the web accessibility (a11y) rule engine against a live page and locate every violation it can detect mechanically.

    103 GitHub starsUsed in 1 repo~682 tokens
    Auto-check: notes
  • Accessibility Fix

    AccessLint/skills

    Remediation only — repair web accessibility (a11y) violations against WCAG 2.2 with a baseline, edit, and verify loop.

    103 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check: notes

Questions about Accessibility Inspect

What does Accessibility Inspect do?

One page, hands-on manual tier — drive a live page through the web accessibility (a11y) checks a rule engine can't decide: keyboard operation and focus order, screen-reader names, roles and states…. Accessibility Inspect is an agent skill from AccessLint/skills. One page, hands-on manual tier — drive a live page through the web accessibility (a11y) checks a rule engine can't decide: keyboard operation and focus order, screen-reader names, roles and states from the accessibility tree, reflow and zoom, reduced motion, form errors, and target size.

When should I use Accessibility Inspect?

Accessibility Inspect fits situations like: keyboard testing; focus-order checks; A11y-tree review; reflow and zoom at 200%.

How do I install Accessibility Inspect in Claude Code?

Run `npx skills add AccessLint/skills --skill accessibility-inspect -a claude-code`. Or copy the skill folder (plugins/accesslint/skills/accessibility-inspect in AccessLint/skills) into .claude/skills/accessibility-inspect in your project. Claude Code loads it when a task matches its description.

How do I install Accessibility Inspect in Codex?

Run `npx skills add AccessLint/skills --skill accessibility-inspect -a codex`. Or copy the skill folder (plugins/accesslint/skills/accessibility-inspect in AccessLint/skills) into .agents/skills/accessibility-inspect in your project. Codex loads it when a task matches its description.

Can I use Accessibility Inspect in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AccessLint/skills --skill accessibility-inspect -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/accessibility-inspect, .gemini/skills/accessibility-inspect, .github/skills/accessibility-inspect and .opencode/skills/accessibility-inspect in your project.

What does Accessibility Inspect need to run?

Going by SKILL.md and its folder, Accessibility Inspect needs the command-line tools its instructions call (claude and npx). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Glob, Grep, Bash, Skill, mcp__chrome-devtools__take_snapshot, mcp__chrome-devtools__take_screenshot, mcp__chrome-devtools__press_key, mcp__chrome-devtools__click, mcp__chrome-devtools__hover, mcp__chrome-devtools__fill, mcp__chrome-devtools__fill_form, mcp__chrome-devtools__resize_page, mcp__chrome-devtools__emulate, mcp__chrome-devtools__evaluate_script, mcp__chrome-devtools__navigate_page, mcp__chrome-devtools__new_page, mcp__chrome-devtools__list_pages, mcp__chrome-devtools__select_page, mcp__chrome-devtools__wait_for, mcp__plugin_accesslint_accesslint__explain_rule.

Does Accessibility Inspect access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Accessibility Inspect safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Accessibility Inspect use?

No licence was found for Accessibility Inspect or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Accessibility Inspect use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Accessibility Inspect?

Skills that share tags, products or a category with Accessibility Inspect: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Accessibility Inspect?

AccessLint (a GitHub organization) maintains it in AccessLint/skills, which has 103 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on August 25, 2026.

Source: AccessLint/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.