Skip to content

Axcess — Design Accessibility Evaluation

by sicxz · remote · no sign-in to list tools · v0.2.0 · published by GitHub user sicxz

Evaluates UI designs for WCAG accessibility issues automated scanners miss. Paid via x402 on Base.

Changes · 2
CompareRegistry entry

3 tools: 2 change things and 1 only read.

Scanned Oct 21, 2026

2 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http axcess https://axcess-mcp-server.fly.dev/mcp

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • Warnevaluate_typography

    The server marks "evaluate_typography" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "evaluate_typography" says "evaluate": a word for a change.

    What this check looks for
  • Warnevaluate_accessibility

    The server marks "evaluate_accessibility" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "evaluate_accessibility" says "evaluate": a word for a change.

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 2Claude Code: ask
  • evaluate_accessibilityEvaluates UI elements for accessibility issues that automated scanners miss.1 finding

    Why it is in this group

    • The name "evaluate_accessibility" says "evaluate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "evaluate_accessibility" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "evaluate_accessibility" says "evaluate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Evaluates UI elements for accessibility issues that automated scanners miss. COST: $0.01 USDC via x402 on Base-compatible EVM network per call. Checks beyond what axe/Lighthouse/WAVE catch at the design stage: - Touch targets below 24×24px (WCAG 2.5.8 AA hard fail) - Touch targets below 44×44px (WCAG 2.5.5 AAA recommended) - Information conveyed by color alone without a secondary indicator (WCAG 1.4.1) - Missing focus indicators on interactive elements (WCAG 2.4.7) - Focus rings thinner than 2px (WCAG 2.4.11) - Focus ring contrast below 3:1 against adjacent background (WCAG 2.4.11) - Interactive elements below the practical usability height floor Args: - elements: Array of 1–50 UI element objects - screen_name: Optional label for the evaluation report Each element requires: element_type. Provide width_px/height_px for touch target checks. Provide uses_color_only + secondary indicator flags for 1.4.1 checks. Provide is_interactive + focus_visible + focus indicator properties for focus checks. Returns: Structured report with: - Per-element scores (0–100) and specific issues - Severity levels (critical/major/minor) with WCAG references - What automated tools miss and why - Concrete fix recommendations - Overall score and verdict (pass/needs_work/fail) - Top issues sorted by severity

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • evaluate_typographyEvaluates typography elements against a principled accessibility rubric.1 finding

    Why it is in this group

    • The name "evaluate_typography" says "evaluate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "evaluate_typography" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "evaluate_typography" says "evaluate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Evaluates typography elements against a principled accessibility rubric. COST: $0.05 USDC via x402 on Base-compatible EVM network per call. Goes beyond what axe/Lighthouse/WAVE can check — evaluates design judgment, not just numeric compliance. Catches issues like: - Contrast that passes WCAG 4.5:1 but fails visually due to thin font weight - Body text that meets minimum size requirements but is still too small for comfortable reading - Line heights that technically comply but impede readability for dyslexic users - Extended all-caps or italic text that passes all AA criteria but impairs reading - Text on gradient/image backgrounds where scanner sampling is unreliable - Heading sizes that are technically correct but visually indistinct from body Args: - elements: Array of 1–50 typography element objects with font/color properties - screen_name: Optional label for the evaluation report Each element requires: element_type, font_size, font_weight, line_height, color_hex, background_color_hex. Returns: Structured report with: - Per-element scores (0–100) - Specific issues with severity (critical/major/minor) - WCAG references and what automated tools miss - Concrete fix recommendations - Overall score and verdict (pass/needs_work/fail) - Top issues sorted by severity Example use: Extract text layer properties from Figma using get_design_context, pass the typography properties to this tool for evaluation before shipping.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Claude Code: allow
  • list_capabilitiesReturns available evaluation tools, what they check, and their pricing.No findings

    Why it is in this group

    • The name "list_capabilities" says "list": a word for reading.
    Description, as the server wrote it
    Returns available evaluation tools, what they check, and their pricing. Call this first to understand what Axcess can evaluate and how much each evaluation costs. This tool is FREE. All evaluation tools require USDC payment on Base network. Returns: JSON with tool descriptions, pricing, and rubric categories.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http axcess https://axcess-mcp-server.fly.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__axcess__list_capabilities"
    ],
    "ask": [
      "mcp__axcess__evaluate_typography",
      "mcp__axcess__evaluate_accessibility"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as axcess. Review it before you use it.