Web Data

Accessibility audit API

Run an automated WCAG accessibility audit on any page in a real browser. Get every violation with its impact, WCAG level, affected elements and how to fix it, the rules that need manual review and an overall score.

View documentation Try the free tool Explore all APIs

Endpoints Active

GET /v1/accessibility

Example request

curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/accessibility?url=example.com"

Example response 200 OK

{
  "status": "ok",
  "score": 84,
  "summary": { "violations": 4, "affected_elements": 23, "by_impact": { "critical": 1, "serious": 2, "moderate": 1, "minor": 0 } },
  "violations": [
    {
      "id": "image-alt",
      "impact": "critical",
      "wcag_level": "A",
      "help": "Images must have alternate text",
      "node_count": 6,
      "nodes": [{ "
...

Example request GET /v1/accessibility

Key Features 4

Frequently asked questions 4

HTTP status codes 200 / 400 / 401 / 402 / 429

Category Web Data

Endpoints 1

Key Features 4

Frequently asked questions 4

Used by people at these companies

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Live Service status

Check live service health and documented failure responses before you integrate.

OpenAPI API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

10,000 Free allowance

Start with 10,000 monthly credits and upgrade only when usage grows.

What this API helps you ship

Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.

Product workflows

Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.

Analyst automation

Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.

Clean JSON data

Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.

AI and ops tooling

Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.

Integration workflow

A simple path from first request to repeatable production usage.

Authenticate once

Send your API key with the documented header and keep requests consistent across services.

Query with examples

Start from the curl and HTTP samples, then map the parameters into your application code.

Operate and monitor

Use status codes, credit costs, and response fields to build retries, logs, and alerts.

Developer kit

Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.

OpenAPI schema

Generate clients or inspect every request and response shape.

Postman collection

Import ready-made requests for manual testing and team handoff.

SDKs and CLI

Use maintained packages and command-line workflows instead of writing boilerplate.

MCP integration

Expose domain intelligence to AI agents and internal assistant workflows.

Parameters and response map

Scan the inputs, output fields, and status codes before wiring the endpoint into your client.

Request parameters

Parameter

urlstandard

Response fields

Example response

statusscoresummaryviolationsaffected_elementsby_impactcriticalseriousmoderateminoridimpact

Status coverage

HTTP status codes

200400401402429

Endpoints

GET /v1/accessibility

Credits: 8Authentication: Authentication required

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Service status API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

Free allowance Sign up for free

Start with 10,000 monthly credits and upgrade only when usage grows.

Active Example request

Start from the curl and HTTP samples, then map the parameters into your application code.

Key Features

WCAG 2.x rules

Checks cover WCAG A and AA success criteria plus best practices, from missing alt text and labels to colour contrast and ARIA misuse.

Prioritized by impact

Violations are sorted from critical to minor, with the number of affected elements and sample selectors and HTML.

Manual review list

Rules that need a human decision are listed separately, so automated passes are never mistaken for full compliance.

Rendered pages

Pages are audited after JavaScript runs, so dynamic menus, forms and content are included.

Example request

GET /v1/accessibility?url=example.com bash

curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/accessibility?url=example.com"

Example response

200 OK json

{
  "status": "ok",
  "score": 84,
  "summary": { "violations": 4, "affected_elements": 23, "by_impact": { "critical": 1, "serious": 2, "moderate": 1, "minor": 0 } },
  "violations": [
    {
      "id": "image-alt",
      "impact": "critical",
      "wcag_level": "A",
      "help": "Images must have alternate text",
      "node_count": 6,
      "nodes": [{ "target": "main > img.hero", "html": "<img src="/hero.jpg">" }]
    }
  ]
}

Frequently asked questions

Does a high score mean the site is compliant?

No. Automated tools catch a part of accessibility barriers. Use the results to fix clear problems, then test manually and with assistive technology.

How is the score calculated?

Passed rules are compared with violations weighted by impact: critical 3, serious 2, moderate 1 and minor 0.5.

Which standard is checked?

WCAG 2.0, 2.1 and 2.2 at levels A and AA, plus common best practices, tagged on each violation.

How many credits does it cost?

Eight credits per audit. Blocked or failed pages are refunded.

Related tools and resources

HTTP status codes

These are the HTTP status codes to handle, so you can tell apart successful responses, auth issues, credits, rate limits, missing data, and upstream failures.

OK 200

Request successful

Bad Request 400

Invalid parameters

Unauthorized 401

Missing or invalid API key/session.

Payment Required 402

Not enough credits to run this request.

Too Many Requests 429

Rate limit exceeded

Audit accessibility

Start free View documentation Try the free tool