Skip to main content
Glama
joe-watkins

WCAG MCP Server

by joe-watkins

Related Servers

Alternatives to WCAG MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Provides comprehensive access to the W3C WAI-ARIA specification for querying roles, states, properties, and accessibility requirements. It enables developers and AI agents to validate ARIA attributes and receive smart role suggestions based on UI component descriptions.
      21
      6 npm
      5
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables automated WCAG 2.2 AA accessibility audits of Figma designs and webpages. Generates detailed markdown reports with severity-grouped violations, specific criterion references, and concrete fix recommendations.
      -
    • F
      license
      A
      quality
      Not graded
      maintenance
      Provides accessibility acceptance criteria for 51 web and 42 native components from the MagentaA11y project. Enables searching, retrieving component specs, and generating accessibility documentation in multiple formats including Gherkin syntax and developer notes.
      11
      -
    • A
      license
      A
      quality
      B
      maintenance
      Scans live web pages and single-page apps across multiple viewports to detect WCAG 2.1 AA accessibility violations and returns concrete, browser-verified fixes grounded in WCAG success criteria and techniques.
      5
      506 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting different WCAG entities (criteria, techniques, glossary terms, guidelines), but some overlap exists: get-criteria-by-level and list-success-criteria both retrieve criteria with filtering, and get-criterion/get-success-criteria-detail/get-full-criterion-context all provide criterion details with varying depth. Descriptions help differentiate these, but an agent might initially confuse them.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, using kebab-case uniformly. Verbs like get, list, search, and count are applied predictably to nouns like criteria, techniques, glossary-terms, and guidelines, making the set easy to navigate and understand.

    Tool Count4/5

    With 20 tools, the count is slightly high but reasonable for the comprehensive WCAG domain, covering principles, guidelines, criteria, techniques, and glossary terms. It feels thorough rather than bloated, though some consolidation (e.g., merging criterion detail tools) could streamline it without losing functionality.

    Completeness5/5

    The toolset provides complete coverage for exploring WCAG 2.2, including listing, retrieving details, and searching across all key components (principles, guidelines, success criteria, techniques, glossary). It supports filtering, contextual information, and even highlights updates in WCAG 2.2, leaving no obvious gaps for an agent working in this domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues