Accessibility Audit

Audit a page against WCAG 2.1: colour contrast, alt text, form labels, ARIA roles, heading order, link text and page language.

Pay by wallet (x402) accessibility-audit

Example

Input

{
  "url": "https://example.com"
}

Answer

{
  "url": "https://example.com",
  "score": 95,
  "passes": [
    "Heading hierarchy is sequential",
    "All links have descriptive text",
    "Page language is declared",
    "Viewport meta tag present"
  ],
  "summary": {
    "low": 1,
    "medium": 0,
    "critical": 0,
    "passed_checks": 4
  },
  "violations": [
    {
      "fix": "Use semantic HTML5 elements (nav, main, header, footer) or ARIA landmark roles",
      "rule": "WCAG 1.3.1 - Landmark Regions",
      "element": "page structure",
      "severity": "low",
      "description": "No landmark regions found (nav, main, header, footer elements or ARIA roles)"
    }
  ],
  "violation_count": 1,
  "manual_review_needed": [
    "Keyboard navigation and focus management",
    "Screen reader compatibility",
    "Color contrast for all text (not just inline styles)",
    "Dynamic content accessibility",
    "Video captions and audio descriptions"
  ]
}

Inputs

Field	Type	Required	What it is
`url`	string	Yes	URL to audit

Output fields

How reliably each field appears in a successful answer.

Field	Type	Appears
`score`	integer	Always (present in every successful answer)
`passes`	array	Always (present in every successful answer)
`violations`	array	Always (present in every successful answer)
`manual_review_needed`	array	Always (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "accessibility-audit",
    "inputs": {
      "url": "https://example.com"
    },
    "max_price_cents": 30
  }'

{
  "tool": "strale_execute",
  "arguments": {
    "slug": "accessibility-audit",
    "inputs": {
      "url": "https://example.com"
    },
    "max_price_cents": 30
  }
}

import { Strale } from "straleio";

const strale = new Strale({ apiKey: process.env.STRALE_API_KEY! });
const result = await strale.do({
  capability_slug: "accessibility-audit",
  inputs: {
    "url": "https://example.com"
  },
  max_price_cents: 30,
});

import os
from straleio import Strale, DoRequest

strale = Strale(api_key=os.environ["STRALE_API_KEY"])
result = strale.do(DoRequest(
    capability_slug="accessibility-audit",
    inputs={
        "url": "https://example.com",
    },
    max_price_cents=30,
))

# No account. The first request answers 402 with the price in USDC;
# an x402 client pays it from your wallet and repeats the request.
curl -i 'https://api.strale.io/x402/v2/accessibility-audit?url=https%3A%2F%2Fexample.com'

Limitations

Manual accessibility testing is still needed
Automated HTML analysis checks common WCAG criteria — cannot assess cognitive accessibility, screen reader behaviour, or keyboard-only navigation
What to do instead: Use as a first pass and follow up with manual testing using a screen reader (NVDA, VoiceOver) for full WCAG compliance