A11Y Toolkit
PYPI · A11Y-TOOLKIT · SCANNED SEP 20
The accessibility layer for AI coding agents: audit, fix, document and watch - WCAG 2.2.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4517 tokens (~196/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the A11Y Toolkit MCP server?
A11Y Toolkit runs locally as a PyPI package, launched with uvx a11y-toolkit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · a11y-toolkit
claude mcp add kinti-a11y-toolkit -- uvx a11y-toolkit
{
"mcpServers": {
"kinti-a11y-toolkit": {
"command": "uvx",
"args": [
"a11y-toolkit"
]
}
}
} {
"servers": {
"kinti-a11y-toolkit": {
"command": "uvx",
"args": [
"a11y-toolkit"
]
}
}
} codex mcp add kinti-a11y-toolkit -- uvx a11y-toolkit
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kinti-a11y-toolkit": {
"type": "local",
"command": [
"uvx",
"a11y-toolkit"
],
"enabled": true
}
}
} openclaw mcp add kinti-a11y-toolkit --command uvx --arg a11y-toolkit
mcp_servers:
kinti-a11y-toolkit:
command: "uvx"
args: ["a11y-toolkit"] {
"McpServers": {
"kinti-a11y-toolkit": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"a11y-toolkit"
]
}
}
} assistant mcp add kinti-a11y-toolkit -t stdio -c uvx -a a11y-toolkit
{
"mcpServers": {
"kinti-a11y-toolkit": {
"command": "uvx",
"args": [
"a11y-toolkit"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +16
- Stability: 0.37 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Schema quality: 3565 → 4517 ▼ functional
- Schema quality: 3565 → 4243 ▼ functional
- Schema quality: 3565 → 3997 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 3.13.2 → 3.20.0 functional
- Package version: 3.13.2 → 3.19.0 functional
- Package version: 3.13.2 → 3.18.0 functional
- Package version: 3.13.2 → 3.17.0 functional
- Package version: 3.13.2 → 3.16.0 functional
- 18 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 3.12.1 → 3.13.2 functional
- Package version: 3.12.1 → 3.13.0 functional
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Sept 26 −12
- Malware scan: pass → unverified ▼ security
- Stability: 0.23 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 146 → 196 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 35% → 100% ▲ functional
- Schema quality: good → excellent functional
- Package version: 3.10.0 → 3.12.1 functional
- Package version: 3.10.0 → 3.12.0 functional
- 14 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 3.8.0 → 3.10.0 functional
- Package version: 3.8.0 → 3.9.0 functional
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/a11y-toolkit@3.20.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
a11y_aria_live_snippet a11y-toolkit: aria-live monitor snippet ~85
Returns injectable JavaScript for an aria-live announcement monitor (bookmarklet or page.evaluate): logs every dynamic-region announcement with time, politeness, role and text — what a screen reader would say, visible on screen. — Diagnostics aid to inject in a browser; not an audit by itself.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | monitor panel language (en default) |
No output schema declared.
No examples provided.
a11y_audit_dom a11y-toolkit: Rendered WCAG audit ~227
Deep RENDERED WCAG audit via local Playwright/Chromium: real computed text contrast against effective backgrounds with alpha compositing (1.4.3), minimum target size 24×24 (2.5.8, new in WCAG 2.2), visible focus indicator heuristic (2.4.7), plus rendered versions of the static checks (alt, accessible names, labels, headings, lang/title, tabindex, aria-hidden, captions, tables). Findings include remediation. Requires playwright: pip install playwright && playwright install chromium. — Use instead of a11y_audit_url on JS-heavy pages; needs local Playwright.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_state | string | – | Path to a Playwright storage_state JSON (exported session) to audit behind login — local file, never uploaded |
| lang | string | – | Output language for findings and remediation (default en) |
| timeout | number | – | page load timeout seconds (45 default) |
| url | string | yes | Page URL to load in Chromium (http/https or file:// for local fixtures) |
No output schema declared.
No examples provided.
a11y_audit_url a11y-toolkit: Express WCAG audit ~394
Express WCAG 2.2 audit of a URL or an HTML string: 20+ automated signals with a weighted 0-100 score — images without alt (1.1.1), controls without accessible names (4.1.2), form fields without labels (3.3.2), missing autocomplete on user-data fields (1.3.5), click handlers on non-interactive elements (2.1.1), unknown ARIA roles and broken aria-labelledby (4.1.2), duplicated unnamed landmarks, timed meta refresh (2.2.1), missing skip mechanism (2.4.1), lang/title (3.1.1, 2.4.2), heading structure (1.3.1), blocked zoom (1.4.4), captions (1.2.2), autoplay audio (1.4.2), generic/duplicated link text (2.4.4), target=_blank without warning (3.2.5), positive tabindex (2.4.3), aria-hidden on focusable elements, tables without th, duplicate ids, duplicate accesskeys. Each finding includes concrete remediation. Filter, not verdict: automation covers ~1/3 of WCAG; query a11y_criterion for what a criterion means. — Prefer a11y_audit_dom when JS renders the content or contrast/2.5.8/focus matter; use pages for light multi-page sampling.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | – | raw HTML to audit directly (overrides url) |
| lang | string | – | output language (en default) |
| pages | integer | – | light same-domain crawl: audit up to N pages, aggregated by score and recurring signals (default 1, max 20) |
| timeout | number | – | fetch timeout seconds (30 default) |
| url | string | – | URL to fetch and audit |
No output schema declared.
No examples provided.
a11y_autofix a11y-toolkit: Deterministic safe auto-fixes ~183
DETERMINISTIC safe auto-fixes applied to HTML — the honest anti-overlay: a short closed list of fixes where the correct answer is unique (unblock viewport zoom 1.4.4, add the exact autocomplete token 1.3.5, fill missing html lang and empty title when provided). Everything requiring judgment (alt text, contrast, accessible names) is NOT touched — it returns no_aplicados with the reason and remediation instead. Returns fixed_html + aplicados + no_aplicados. — Only the closed allowlist of provably safe fixes; judgment fixes come back as no_aplicados with remediation.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | raw HTML to fix |
| lang | string | – | only if provided and <html> lacks lang |
| title | string | – | only if provided and <title> is empty |
No output schema declared.
No examples provided.
a11y_badge a11y-toolkit: Honest SVG badge ~132
Returns an HONEST accessibility badge as accessible SVG: score, date and scope (automated screening ≈ 1/3 of WCAG), color-coded by score. Deliberately does NOT say "conformant" — the honest seal. Embed it in audited sites or statements. — Scope: the honest SVG seal for audited sites; the machine-readable bundle is a11y_evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| fecha | string | – | ISO date (today by default) |
| lang | string | – | Badge language (default en) |
| score | number | yes | 0-100 (from an audit result) |
No output schema declared.
No examples provided.
a11y_contrast_image a11y-toolkit: Text-over-image contrast ~203
TEXT OVER IMAGE contrast: pixel-level sampling of the real background behind the text box → worst/median/p95 ratio, % of area passing AA, and automatic hostile-zone detection on a 3×3 grid (zona_peor). What pair-only checkers cannot do. region="x,y,w,h" recommended. — Use instead of a11y_contrast_pair whenever the background is a photo/gradient.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Output language (default en) |
| path | string | yes | Local path to the screenshot/image the text sits on (PNG/JPG/PPM) |
| region | string | – | Text bounding box as "x,y,width,height" in pixels (strongly recommended: defines what to sample) |
| sample | integer | – | Pixel step: 4 samples every 4px (auto-raised for huge regions) |
| text_color | string | yes | The text color as rendered over the image (must be opaque) |
No output schema declared.
No examples provided.
a11y_contrast_pair a11y-toolkit: Contrast ratio + verdicts ~166
Exact WCAG contrast ratio for a color pair: per-criterion verdicts 1.4.3 (AA), 1.4.6 (AAA), 1.4.11 (non-text). Accepts #hex, rgb(), hsl(), CSS color names; rgba/hsl with alpha is composited over the background. If AA fails, suggests the nearest passing color. — For flat pairs; text over images needs a11y_contrast_image.
| Name | Type | Req | Description |
|---|---|---|---|
| bg | string | yes | Background color: same formats; alpha composites over white |
| fg | string | yes | Foreground/text color: #hex, rgb(), hsl() or a CSS color name; alpha composites over bg |
| lang | string | – | output language (en default) |
No output schema declared.
No examples provided.
a11y_criterion a11y-toolkit: WCAG criterion explained ~135
Explains a WCAG 2.2 success criterion in plain language (es/en): what it requires, typical failures, and how to verify it with this toolkit (which tool automates which part). Codes like "1.4.3", "2.5.8", "4.1.2". Use it whenever you need to explain WHY a finding matters or what the criterion actually says. — Knowledge lookup; does not fetch or audit anything.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | criterion number, e.g. 1.4.3 |
| lang | string | – | Explanation language (default en) |
No output schema declared.
No examples provided.
a11y_diff a11y-toolkit: Snapshot regression diff ~102
Regression diff between two accessibility snapshots (before/after a deploy): added/removed/renamed interactives and focus-order changes. ok=false means a regression to review. Accepts inline JSON (starting with "{") or file paths. — Compares two existing snapshots; a11y_diff_urls snapshots both for you.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | BEFORE snapshot (inline JSON or path) |
| b | string | yes | AFTER snapshot (inline JSON or path) |
No output schema declared.
No examples provided.
a11y_diff_urls a11y-toolkit: Staging vs production diff ~78
Snapshot two URLs and diff them in a single call (e.g. staging vs production). Requires local Playwright. — Convenience for staging-vs-production; manual control is snapshot + a11y_diff.
| Name | Type | Req | Description |
|---|---|---|---|
| url_a | string | yes | First URL (usually staging) |
| url_b | string | yes | Second URL (usually production) |
No output schema declared.
No examples provided.
a11y_disprove a11y-toolkit: Disprover: re-verify findings ~143
Disprover pattern (from Cloudflare's security-audit-skill): re-runs the audit against the live page and marks each finding confirmed or rejected — findings that don't reproduce are rejected with the reason. Catches false positives, race conditions, and page changes between audit and report. Returns a fresh score over confirmed findings only. — Run this before acting on any audit report.
| Name | Type | Req | Description |
|---|---|---|---|
| informe | object | – | existing audit report (optional; if absent, audits first) |
| lang | string | – | Output language (en default) |
| timeout | number | – | Timeout seconds (30 default) |
| url | string | yes | URL to re-verify against |
No output schema declared.
No examples provided.
a11y_evidence a11y-toolkit: Evidence pack (countersignature-ready) ~272
Builds the COUNTERSIGNATURE-READY evidence pack: the machine→human handoff object for WCAG conformance work. Takes one or more audit reports (any mode — static, rendered, reflow, keyboard, scroll) and returns: a full criteria matrix (automated-fail / automated-review / not-flagged — NOT pass / manual-only), the list of A/AA criteria with no automated signal anywhere (the human reviewer homework list), every artifact SHA-256-hashed with timestamps, an empty signature block (name, credential, date) whose statement must reference the pack's own sha256, and the tamper-evidence rule stated. Vendor-neutral: any qualified human can countersign it. Evidence, never conformance. — The tier-3 handoff object; feed it every audit report you have.
| Name | Type | Req | Description |
|---|---|---|---|
| evaluador | object | – | {"nombre":…, "credencial":…, "fecha_revision":…} to prefill the signature block |
| informes | array | yes | audit report objects (any mode) |
| snapshot | object | – | a11y_snapshot output (optional) |
| verificados | array | – | Criterion codes an agent/human verified against this sample (manual checklist protocol) — they become agent-verified in the matrix; automated-fail stays fail |
No output schema declared.
No examples provided.
a11y_forms a11y-toolkit: Form error testing ~188
Form error testing (3.3.1 Error Identification, 3.3.3 Error Suggestion) — the guided flow no competitor automates: fills every validatable field with INVALID data, really submits, and judges the post-submit DOM — are errors identified in text and associated with the field (aria-invalid + aria-describedby, error summary, role=alert), or does the form swallow them? Native browser validation counts as identification (unless the form has novalidate); forms that navigate on submit are honestly noted as not measurable in-page. Requires local Playwright.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_state | string | – | Path to a Playwright storage_state JSON to test forms behind login |
| lang | string | – | Output language (en default) |
| timeout | number | – | Page load timeout seconds (45 default) |
| url | string | yes | Page URL with the form(s) to test |
No output schema declared.
No examples provided.
a11y_generate_declaration a11y-toolkit: Accessibility statement (EAA/RD 1112) ~401
Generates an Accessibility Statement in HTML: art. 10 RD 1112/2018 (Spanish public sector, marco="rd1112") or European Accessibility Act wording (Directive (EU) 2019/882 / Ley 11/2023, marco="eaa"; EN output uses Directive (EU) 2016/2102 / EAA wording). The generated document is itself accessible. Saves to output_path when given. — Legal statement generator; drive contenido_no_accesible from audit findings and a11y_evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| contenido_no_accesible | array | – | Non-accessible content list: one string per item, ideally criterion + reason + alternative |
| disponibilidad_alternativa | string | – | Where to get the content in an alternative accessible format |
| entidad | string | yes | Legal entity name as it should appear in the statement (company, body…) |
| estado | string | yes | Compliance state: plena | parcial | no_conforme (parcial is the honest default when findings exist) |
| fecha_evaluacion | string | – | ISO date of the last evaluation (YYYY-MM-DD) |
| fecha_revision | string | – | ISO date of the next scheduled review |
| feedback | string | – | Contact channel for accessibility feedback (email or URL) |
| lang | string | – | Statement language (default en; es uses the Spanish legal wording) |
| marco | string | – | Legal framework: rd1112 (Spanish public sector, art. 10) or eaa (European Accessibility Act / private sector) |
| metodo | string | – | How conformance was evaluated (e.g. "self-evaluation: a11y-toolkit screening + manual review") |
| output_path | string | – | save the HTML here (optional) |
| reclamacion | string | – | Claim/complaint procedure URL or address (legally required in several jurisdictions) |
| url | string | yes | Website URL the statement covers |
No output schema declared.
No examples provided.
a11y_hover a11y-toolkit: Hover dismissibility (1.4.13) ~116
Content on Hover or Focus (1.4.13): finds tooltip/overlay candidates, hovers each, and tests whether Escape dismisses the result — tooltips that do not dismiss are flagged. Requires local Playwright. — Scope: tooltips only; full audit is a11y_audit_dom, keyboard traps are a11y_keyboard.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Output language (en default) |
| timeout | number | – | Page load timeout (45 default) |
| url | string | yes | Page URL to test |
No output schema declared.
No examples provided.
a11y_html_validate a11y-toolkit: W3C Nu validation ~220
The W3C's own parser as a toolkit mode: checks a URL or raw HTML against the Nu Html Checker (validator.w3.org/nu) — doctype, encoding, structural validity, plus alt/lang/role issues from the authoritative source, mapped to WCAG criteria where they overlap. PRIVACY: html mode POSTs the document to the W3C service (url mode shares only the URL, like a11y_audit_url); self-hosted vnu instances supported via base_url for sensitive content.
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | – | Base URL of a self-hosted vnu instance (docker ghcr.io/validator/validator) instead of the public W3C service |
| html | string | – | Raw HTML to validate — POSTs the content to validator.w3.org/nu; use url or a self-hosted instance for sensitive pages |
| lang | string | – | Output language (en default) |
| url | string | – | Page URL to validate (shares the URL with the W3C service) |
No output schema declared.
No examples provided.
a11y_keyboard a11y-toolkit: Keyboard-trap detector ~193
Keyboard-trap detection (2.1.2) with REAL Tab walking in Chromium: up to 60 real tab stops, cycle detection (the modal pattern), then the decisive test — does ESCAPE release the cycle? A modal that cycles and releases on Escape is correct and NOT reported; a cycle Escape cannot leave is a trap (high severity). Returns the full tab stop list too. Requires local Playwright. — Scope: keyboard traps (2.1.2); focus visibility is part of a11y_audit_dom.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_state | string | – | Path to a Playwright storage_state JSON (exported session) to Tab-walk behind login |
| lang | string | – | Output language (default en) |
| max_pasos | integer | – | max real Tab presses (60 default) |
| url | string | yes | Page URL to Tab-walk (http/https or file://) |
No output schema declared.
No examples provided.
a11y_ledger a11y-toolkit: Coverage ledger (persistent) ~131
Coverage ledger (from Cloudflare's security-audit-skill): persistent record of what has been audited, when, and with what result. Actions: record (add audit result), gaps (what has never been checked on a URL), summary (portfolio overview). Accumulates across runs — second audits show resolved findings.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What to do |
| informe | object | – | audit report object (for record) |
| ledger_path | string | – | ledger file path (default: a11y-ledger.json) |
| url | string | – | URL (for record/gaps) |
No output schema declared.
No examples provided.
a11y_reflow a11y-toolkit: 320px reflow check ~220
Reflow check at 320px — criterion 1.4.10 (AA), the check axe and Lighthouse do not automate. Loads the URL at 1280px, then at 320px, and reports real horizontal scroll + the overflowing elements. Method note: browser zoom RE-LAYS OUT at 320 CSS px (that is the standard's own equivalence: 1280 @ 400% zoom = 320px), so the correct measurement is a 320px viewport. Requires local Playwright. — Scope: 320px reflow only (1.4.10); for the full rendered pass use a11y_audit_dom.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_state | string | – | Path to a Playwright storage_state JSON (exported session) to test behind login |
| lang | string | – | Output language (default en) |
| timeout | number | – | Page load timeout in seconds (default 45) |
| url | string | yes | Page URL to test at 320px (http/https or file://) |
No output schema declared.
No examples provided.
a11y_scroll a11y-toolkit: Infinite-scroll audit ~248
Infinite-scroll accessibility audit — the documented disaster nobody automates (Deque guidance + ARIA APG Feed pattern; criteria 2.4.3, 4.1.3, 2.2.2). Real scrolling batches in Chromium with a live-region observer: does the focused element SURVIVE each batch (re-render destroys it — the documented failure)? Is new content ANNOUNCED (aria-live/status receives text, role=feed)? Does the feed END or offer a load-more alternative (footer reachability)? APG feed pattern as positive signal. Honest guard: if no standard items are detected (login walls, non-standard markup) the unfounded signals are skipped with a note. Requires local Playwright. — For paginated feeds only; general page audit is a11y_audit_url/dom.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_state | string | – | Path to a Playwright storage_state JSON (exported session) to audit an authenticated feed |
| lang | string | – | Output language (default en) |
| max_tandas | integer | – | scroll batches (5 default) |
| url | string | yes | Feed URL to audit (best on feeds you own or can authenticate into) |
No output schema declared.
No examples provided.
a11y_snapshot a11y-toolkit: A11y snapshot + tab order ~151
Accessibility snapshot of a URL: interactive elements (tag, role, accessible name, href) in DOM order, the REAL tab focus order, and when Playwright ≥1.49 is available the computed ACCESSIBILITY TREE (aria snapshot — what a screen reader announces). Save it before a deploy and compare after with a11y_diff. Requires local Playwright. — Capture half of the watch loop; compare with a11y_diff (or a11y_diff_urls for two live URLs).
| Name | Type | Req | Description |
|---|---|---|---|
| auth_state | string | – | Path to a Playwright storage_state JSON (exported session) to snapshot behind login |
| url | string | yes | Page URL to snapshot (http/https or file://) |
No output schema declared.
No examples provided.
a11y_sr_transcript a11y-toolkit: Screen reader transcript ~130
Screen reader TRANSCRIPT: what a blind user HEARS on this page. Walks the accessibility tree linearly and returns the announcement text with roles, names and states — the linearized reading experience, as prose an agent can READ to understand the page from a blind user's perspective. — Read-only: for structure use a11y_snapshot, for keyboard traps use a11y_keyboard. Requires Playwright.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Output language (en default) |
| timeout | number | – | Page load timeout (45 default) |
| url | string | yes | Page URL to transcribe |
No output schema declared.
No examples provided.
a11y_suggest_color a11y-toolkit: Nearest passing color ~126
Nearest opaque color (RGB distance) to fg that reaches the target ratio against bg (4.5 default). Returns the color, its ratio and whether it lightens or darkens. — The fixer companion to a11y_contrast_pair failures.
| Name | Type | Req | Description |
|---|---|---|---|
| bg | string | yes | The background it must pass against |
| fg | string | yes | The failing foreground color to fix |
| target | number | – | Ratio to reach: 4.5 normal text, 3.0 large text/UI, 7.0 AAA (default 4.5) |
No output schema declared.
No examples provided.
What is the A11Y Toolkit MCP server?
A11Y Toolkit is an MCP server listed in the public MCP registry as io.github.kinti/a11y-toolkit. The accessibility layer for AI coding agents: audit, fix, document and watch - WCAG 2.2. This page covers its PyPI package (a11y-toolkit).
Is the A11Y Toolkit MCP server safe to use?
A11Y Toolkit scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the A11Y Toolkit MCP server expose?
A11Y Toolkit exposes 23 tools: a11y_audit_url, a11y_audit_dom, a11y_contrast_pair, a11y_contrast_image, a11y_suggest_color, and 18 more. Their descriptions and schemas cost roughly 4,244 tokens of context every time the server is loaded.
Is the A11Y Toolkit MCP server still maintained?
A11Y Toolkit is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the A11Y Toolkit MCP server under?
A11Y Toolkit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.