No user-submitted related servers found.
Scored across 37 tools
Most tools have clearly distinct targets: static vs rendered audits, PDF/DOCX/VTT screening, contrast pair/image/DOM, snapshot vs diff, and remediation vs evidence/report generation. There is some conceptual overlap among page-audit entry points (a11y_audit_url, a11y_html_validate, a11y_disprove) and the conformance-artifact tools (evidence, scope, VPAT, OpenACR, declaration), but descriptions and the router make the intended selection explicit.
All tool names use a consistent a11y_ snake_case prefix, and most follow a recognizable verb_noun or action-oriented pattern (audit_url, generate_vpat, suggest_color, diff_urls). A few are noun-only artifacts (a11y_ledger, a11y_evidence, a11y_badge, a11y_patches), but the convention remains predictable rather than chaotic.
At 37 tools, the surface is far above the well-scoped range and imposes a significant selection burden even for a broad accessibility domain. The router helps, and many tools are genuinely specialized, but the count is still heavy enough that it exceeds what most agents can comfortably navigate without routing assistance.
The lifecycle is unusually complete: routing, static/rendered audits, document and caption screening, keyboard/forms/hover/scroll/reflow/motion checks, remediation, regression diffing, evidence packaging, legal/conformance reports, and knowledge lookup. Minor gaps remain around manual-review checklist generation and live assistive-technology interaction, but there are no obvious dead ends for the core automated accessibility workflow.