Accesslint Scan

Community

FrancoStino

accesslint-scan

Audit a live page for accessibility issues, locate each WCAG violation precisely, and return a selector-grounded fix worklist without editing.

Overview

Publisher	FrancoStino
Repository	`opencode-skills-collection`
Skill name	`accesslint-scan`
Stars	90
Forks	12
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by FrancoStino on GitHub. Read the source before you install it.

Installation

Install the Accesslint Scan AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/FrancoStino/opencode-skills-collection/tree/main/bundled-skills/accesslint-scan
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/FrancoStino/opencode-skills-collection/tree/main/bundled-skills/accesslint-scan

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/FrancoStino/opencode-skills-collection.git /tmp/opencode-skills-collection
mkdir -p .claude/skills
cp -r /tmp/opencode-skills-collection/bundled-skills/accesslint-scan .claude/skills/accesslint-scan

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Accesslint Scan in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Accesslint Scan on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Accesslint Scan is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Audit a live page and report what's broken and where. Locate; don't fix. If no URL in $ARGUMENTS, ask for one.

When to Use

A supplied page needs an automated contrast, accessible-name, or semantic-markup audit.
You need selector-grounded findings after a UI change, without modifying the application.
Manual assistive-technology checks or site-wide conformance assessment are separate work.

1. Audit

Use an already reviewed, project-pinned installation of @accesslint/chrome and @accesslint/cli; confirm their local binaries and CLI help before execution. Do not silently download and execute @latest. Confirm the URL and whether browser access could expose authenticated or sensitive content.

For a project whose locked installation exposes these binary names:

bash
session_file="$(mktemp)"
./node_modules/.bin/accesslint-chrome ensure > "$session_file"

Read the complete JSON result once, record port and managed, and substitute the returned port in ./node_modules/.bin/accesslint scan "<target>" --port "<returned-port>" --format json. Never parse arbitrary stdout chunks as complete JSON. Confirm the actual binary names from the installed packages; they may differ by version. The current upstream command shape is scan <target> --port <port> --format json.

Flags as needed: --selector, --wait-for "<selector>", --include-aaa, --disable <rules>.

2. Report

Counts by impact, then one entry per violation:

where — selector verbatim + file:line (symbol) if source is present — never fabricate. If no violation has source, note "source mapping unavailable — located by selector only".
evidence — contrast ratio, missing attribute, empty name
fix — mechanical change or NEEDS HUMAN

Return the worklist without editing. Remediation requires a separate authorized task; current upstream names it accesslint:accessibility-fix, which may not be installed in this host.

3. Tear down

Stop only the managed browser session created for this audit, using the installed helper's supported session/port-specific stop operation. If it only supports stop --all, check for other managed sessions first and do not terminate unrelated audits. Skip teardown of an unmanaged browser.

Gotchas

ensure always determines the port — never hardcode 9222.
CLI exit 2 = bad URL or page never loaded; check the dev server.

Limitations

Automated rules cannot certify full WCAG conformance; retain human-required findings and record scan failures separately from zero violations.
Upstream CLI shape checked against AccessLint scan source; this AAS skill does not bundle the CLI or install it.
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Frequently asked questions

What does the Accesslint Scan AI skill do?

Audit a live page for accessibility issues, locate each WCAG violation precisely, and return a selector-grounded fix worklist without editing.

Why use Accesslint Scan on TypingMind?

Because you install it once and use it with any model. Accesslint Scan is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Accesslint Scan in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/FrancoStino/opencode-skills-collection/tree/main/bundled-skills/accesslint-scan. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Accesslint Scan?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Accesslint Scan?

As many as you like. As long as a model supports skills, you can use Accesslint Scan with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Accesslint Scan AI skill free?

Yes. It is published on GitHub by FrancoStino under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Algorithmic Art

anthropics

OrganizationPopular

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or…

Doc Coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This…

Authoring Skills

How to create and maintain agent skills in .agents/skills/. Use when creating a new SKILL.md, writing skill descriptions, choosing frontmatter fields, or deciding what content belongs in a skill vs…

Dce Edge

DCE-safe require() patterns and edge runtime constraints. Use when writing conditional require() calls, guarding Node-only imports (node:stream etc.), or editing define-env-plugin.ts / app-render /…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

When to Use

1. Audit

2. Report

3. Tear down

Gotchas

Limitations

Frequently asked questions

Related AI Skills

Set up your own AI workspace now