EU Web Accessibility Directive API

Connect a WAD-oriented technical profile to public-sector publishing. The API keeps the selected mapping, coverage, findings, and scan history inspectable while leaving full-site monitoring and legal enforcement outside a single asset result.

For public bodies and integrators operating repeatable monitoring workflows

API profileeu-wad-current@2026.3
Illustrative request202 Accepted
POST /v1/scans
Idempotency-Key: q3-sample:essential-services

{
  "asset": {
    "type": "url",
    "url": "https://municipality.example/services"
  },
  "profiles": [
    "eu-wad-current@2026.3"
  ],
  "metadata": {
    "sample_id": "q3-sample:essential-services"
  }
}
queuedid: scn_01J…profile resolved
Inputs
Public-sector web and supported documents
History
Pinned scans for repeat monitoring
Limit
One scan is not complete WAD monitoring

Make each sampled asset traceable to the monitoring plan.

Project and sample metadata let teams organize repeated technical checks without pretending the API chose a representative sample.

Sample

Name the service and selection

Attach sampling-plan IDs, asset categories, and the organization’s external reference.

Scan

Pin the current technical profile

Retain resolved mappings, source evidence, coverage, and engine versions.

Review

Combine automation with manual work

Use the result as one input to broader monitoring, user testing, and declaration work.

Move one public-sector scan across delivery, monitoring, and evidence systems.

The API record can travel between teams because its technical identity, source mapping, and review boundary remain attached.

  • Supplier preview
  • Public URL
  • Document upload
AccessPreflightDirective technical profile
  • Engineering issue
  • Monitoring evidence
  • Review checkpoint

Use asset evidence within the monitoring method.

A versioned scan is reproducible technical evidence. The surrounding monitoring design remains an organizational responsibility.

Asset-level result

  • Findings tied to a URL or uploaded document
  • Requirement mappings and coverage decisions
  • Baseline comparison across repeated scans
  • Open manual checks for the selected asset

Program-level work

  • Representative sampling and complete coverage
  • Mobile-app and end-to-end task evaluation
  • Accessibility statement and feedback process
  • National monitoring and enforcement procedure

Inspect the policy behind the API profile.

Before EU Web Accessibility Directive becomes a production gate, review its source mapping, supported input, automation boundary, and required human checks.

Put the EU Web Accessibility Directive API in the path you already own.

Start with one asset flow, pin the profile, and keep evidence and unresolved human work attached to every result.

Check a website freeCreate an account

Automated preflight is not an accessibility certification or legal determination.