Skip to main content
Glama
530,294 tools. Updated 2026-09-07 20:14

"A tool for comprehensive WCAG 2.2 AA testing with screenshots and additional features" matching MCP tools:

  • Get the Designesy WCAG 2.2 AA accessibility verification framework: 11 conformance checks (a01-a11) plus a ready-to-run Playwright + axe-core 4.13.0 script template targeting your URL. Use this to audit a site for accessibility violations. When NOT to use: for a full design-contract score (not just a11y), use designesy_score. Does NOT run the scan — axe-core needs a real browser DOM. Returns the 11 checks + a Playwright script you execute locally (npm i -D @axe-core/playwright). The score comes from your local run, not from this tool. Returns JSON: { checks[{id (a01–a11), name, status: "PENDING_EXECUTION"}], playwright_script, install_command, run_command }. Pass config (JSON string) to customize axe.configure() — e.g. branding overrides, rule disables. Omit for standard WCAG 2.2 AA.
    ConnectorNo auth
  • Returns the structured offering for TESSA's WCAG 2.2 AA Accessibility Audit: scope, deliverables, timeline, pricing bands (hourly + engagement range), paired service-type slugs, and the URL of TESSA's profile in the TESSA Compliance Registry. Use this when a buyer agent needs TESSA's accessibility audit offering in structured form.
    ConnectorNo auth
  • Automated technical accessibility pre-check (WCAG 2.1/2.2 AA via axe-core) for one public https:// URL, rendered in a real headless browser, mapped to German BFSG requirements. Catches roughly 57% of WCAG violations — NOT a substitute for a manual audit and never a conformity proof. Results are cached 6h per (url, standard); a cache hit still costs the full price. 500 credits, requires an API key.
    ConnectorNo auth
  • Check the WCAG contrast ratio between a foreground and background color, with AA/AAA pass/fail for normal and large text.
    ConnectorNo auth
  • Structured offering for TESSA's WCAG 2.2 AA Accessibility Audit: scope, deliverables, timeline, pricing bands (hourly + engagement range), paired service-type slugs, and TESSA's profile URL in the Compliance Registry. Use when a buyer agent wants accessibility audit details in structured form.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Disposable test mailboxes on a real domain: send, receive and assert on real email.

  • Search the AI Tool Directory catalog: tool details, status checks (alive/acquired/deceased + cause and date), alternatives, and side-by-side comparisons. Read-only.

  • [utility] 2色間のWCAG 2.1コントラスト比とAA/AAA適合判定を計算 / Calculates WCAG 2.1 contrast ratio and AA/AAA compliance between two colors. [use_cases: design]
    ConnectorNo auth
  • WCAG contrast ratio between two hex colors (AA/AAA). When: WCAG contrast ratio for UI color pairs.
    ConnectorNo auth
  • A colour contrast fixer — the nearest accessible colour that passes WCAG AA. A HelpySelf tool (helpyself.com).
    ConnectorNo auth
  • Analyze a website URL for WCAG 2.1 Level A accessibility issues. Automated static HTML analysis covering approximately 30-40% of WCAG 2.1 Level A criteria. Checks include: image alt text, form labels, heading hierarchy, page title, html lang, empty links/buttons, ARIA labels, duplicate IDs, skip navigation, table headers, landmarks, viewport zoom, autoplay media, and tabindex ordering. Manual testing is required for full WCAG compliance assessment. Results are cached for fast subsequent lookups. Rate limited to 1 request per minute per domain. Args: url: The website URL to analyze (e.g., "https://example.com"). Returns: WCAG analysis with: - url: The analyzed URL - score: Accessibility score (0-100) - grade: Letter grade (A-F) - issues: Categorized issues (critical, warnings, info) - meta: Extracted accessibility metadata - recommendations: Prioritized improvements - coverage_note: Disclaimer about automated coverage - cached: Whether result was from cache
    ConnectorNo auth
  • Submits an enquiry to LEV Testing Cost — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Happy for my details to go to relevant LEV testing companies, who'll quote me directly."
    ConnectorNo auth
  • Submits an enquiry to Penetration Testing Cost — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Happy for my details to go to relevant penetration testing providers, who'll contact me directly."
    ConnectorNo auth
  • WCAG contrast ratio between a foreground and background color, for accessibility. Both accept a hex, CSS name, RNV brand name, or saved-palette reference. Returns the ratio (1.0-21.0) plus pass/fail for AA and AAA at normal and large text sizes and for UI components. Read-only and deterministic, with no side effects. Use this for legibility and accessibility checks; to measure raw perceptual difference between two colors rather than readability use color_difference instead.
    ConnectorNo auth
  • 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
    ConnectorNo auth
  • WCAG contrast ratio between a foreground and background color, for accessibility. Both accept a hex, CSS name, RNV brand name, or saved-palette reference. Returns the ratio (1.0-21.0) plus pass/fail for AA and AAA at normal and large text sizes and for UI components. Read-only and deterministic, with no side effects. Use this for legibility and accessibility checks; to measure raw perceptual difference between two colors rather than readability use color_difference instead.
    ConnectorNo auth
  • Use this when checking whether a text/background color pair meets WCAG 2.x accessibility contrast. Computes the relative-luminance contrast ratio (1-21, rounded to 2 decimals) and returns pass/fail booleans for normal and large text at AA and AAA levels (thresholds 4.5 / 7 / 3 / 4.5), plus a suggested passing foreground hex when normal-text AA fails (null when it already passes or none is found). Accepts 3- or 6-digit hex, with or without a leading '#'; echoed colors are normalized to 6-digit hex. Deterministic: same input, same output. Example: {foreground:'777', background:'fff'} -> ratio 4.48, normalAA false, largeAA true, suggestedForeground '#767676'.
    ConnectorNo auth
  • Analyze teaching text with Flesch-Kincaid readability and leveling advice. FREE. Typical input {"text": "<passage>", "target_grade": 6} returns {"flesch_kincaid_grade": 8.2, "reading_ease": 62.1, "sentences": N, "words": N, "avg_words_per_sentence": N, "long_sentences_over_25w": N, "polysyllabic_words_sample": [...], "target_grade": 6, "gap": 2.2, "suggestions": ["..."]}. Use on teaching text where the reading level matters. Not for scores students earned (grade_curve) and not for general prose style, which the creator server's analyze_writing covers. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "empty text"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • Discover available product features, API/MCP URLs, versions, content limits, and interpretation boundaries before choosing a content tool. Returns product.capabilities.v1 metadata, without fetching stories or checking upstream freshness. Public and read-only; no credentials or arguments. Use latest_stories for recent records or get_health for endpoint compatibility. The mobile app distribution channel remains separately suspended.
    ConnectorNo auth
  • Run a WCAG accessibility audit on a page using axe-core in a real browser, and report the violations with the elements responsible. Because it runs against a genuinely rendered page, colour-contrast and other rules that depend on layout and computed colour actually fire — these are silently skipped by audits that parse HTML without a layout engine. Use this to check a page meets WCAG before shipping.
    ConnectorNo auth
  • Analyze teaching text with Flesch-Kincaid readability and leveling advice. FREE. Typical input {"text": "<passage>", "target_grade": 6} returns {"flesch_kincaid_grade": 8.2, "reading_ease": 62.1, "sentences": N, "words": N, "avg_words_per_sentence": N, "long_sentences_over_25w": N, "polysyllabic_words_sample": [...], "target_grade": 6, "gap": 2.2, "suggestions": ["..."]}. Use on teaching text where the reading level matters. Not for scores students earned (grade_curve) and not for general prose style, which the creator server's analyze_writing covers. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "empty text"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth