a11y-toolkit
Related Servers
Alternatives to a11y-toolkit
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to perform comprehensive web accessibility checks (WCAG 2.1/2.2) including color contrast analysis, ARIA validation, and full accessibility report generation without requiring any API key.8MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with web accessibility analysis tools via MCP, enabling checks for alt text, heading hierarchy, color contrast, ARIA validation, and form accessibility.40 npmMIT
- FlicenseBqualityDmaintenanceEnables AI agents to perform comprehensive accessibility audits on websites using Playwright and axe-core against WCAG standards. Provides detailed compliance reports with violation summaries and remediation guidance across multiple browsers.3-
- AlicenseAqualityBmaintenanceEnables AI agents to perform real accessibility audits by controlling a browser, running axe-core scans, reviewing page structure, images, tab order, and WCAG 2.2 color contrast, all over MCP with local session logging.21727 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceAutonomous WCAG 2.1 accessibility auditor that scans, fixes, re-verifies, and generates VPAT 2.5 EN 301 549 reports using AI vision analysis + DOM scanning.9,148 npm1MIT
- AlicenseAqualityCmaintenanceProvides conversational, actionable accessibility testing for AI agents, including auditing, prioritization, and code-level fixes.2218 npmMIT
TDQS
Scored across 23 tools
Each tool has a distinct, well-defined purpose: contrast pair vs image, URL vs DOM audit, snapshot vs transcript, diff vs diff_urls, and specialized checks like keyboard, reflow, scroll, and forms. No two tools overlap ambiguously; even similar-sounding ones (e.g., audit_url vs audit_dom) are clearly differentiated by scope and use case.
All tools share a consistent 'a11y_' prefix and use descriptive snake_case names. Most follow a verb_noun pattern (audit_url, suggest_color, generate_declaration), though a few are bare nouns (badge, evidence, criterion) or verb-only (disprove, hover). The pattern is predictable and readable, with only minor deviation from a strict convention.
With 23 tools, the count is at the upper boundary of the 'well-scoped' range. However, the toolkit covers a broad spectrum of accessibility auditing needs—from basic audits to specific WCAG checks, regression tools, evidence building, and legal declaration generation—so each tool earns its place. It is dense but not bloated.
The surface is remarkably complete for WCAG 2.2 auditing: it includes static and rendered audits, contrast checks, keyboard and reflow tests, scroll and form validation, snapshot/diff workflows, transcript generation, auto-fixes, evidence packs, and even a coverage ledger and disprover. There are no obvious dead ends; the toolkit supports a full audit lifecycle.