Pandus Accessibility

WCAG 2.2 rule reference for free; with an API key: what to fix on your sites and new checks.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
100%
Naming quality
87%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~519Tokens (tool definitions)
~941 BTypical response size
Minimal attention impact (0.41% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "accessibility": {
      "url": "https://pandus.online/mcp"
    }
  }
}

Remote endpoints

https://pandus.online/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢search_rules(query, locale)

Searches the Pandus library of accessibility rule cards (the axe-core rules Pandus checks, explained for business owners) by words, an axe rule id or a WCAG success criterion such as 1.4.3. Free, no API token needed.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "description": "Words, an axe-core rule id (color-contrast) or a WCAG criterion (1.4.3).",
      "type": "string"
    },
    "locale": {
      "description": "Language of the texts.",
      "default": "en",
      "enum": [
        "en",
        "uk",
        "de",
        "pl",
        "cs",
        "ro",
        "ru"
      ],
      "type": "string"
    }
  },
  "required": [
    "query"
  ]
}
🟢explain_rule(rule, locale, platform)

Explains one accessibility rule (an axe-core rule id such as image-alt or color-contrast): what is wrong, why it matters for customers, who is affected, how to fix it in code and on Shopify, WooCommerce, PrestaShop or Shoptet, and the WCAG 2.2 / EN 301 549 clauses. Free, no API token needed.

Input Schema

{
  "type": "object",
  "properties": {
    "rule": {
      "description": "axe-core rule id, for example image-alt.",
      "type": "string"
    },
    "locale": {
      "description": "Language of the card.",
      "default": "en",
      "enum": [
        "en",
        "uk",
        "de",
        "pl",
        "cs",
        "ro",
        "ru"
      ],
      "type": "string"
    },
    "platform": {
      "description": "Only the tip for this platform, for example shopify or woocommerce.",
      "type": "string"
    }
  },
  "required": [
    "rule"
  ]
}
🟢explain_wcag_criterion(criterion, locale)

Explains a WCAG 2.2 level A or AA success criterion (for example 2.4.7) in plain words: what it asks, examples, how to test it by hand and what automated checks can and cannot find. Free, no API token needed.

Input Schema

{
  "type": "object",
  "properties": {
    "criterion": {
      "description": "WCAG success criterion number, for example 1.4.3.",
      "type": "string"
    },
    "locale": {
      "description": "Language of the text.",
      "default": "en",
      "enum": [
        "en",
        "uk",
        "de",
        "pl",
        "cs",
        "ro",
        "ru"
      ],
      "type": "string"
    }
  },
  "required": [
    "criterion"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools