Name the service and selection
Attach sampling-plan IDs, asset categories, and the organization’s external reference.
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
eu-wad-current@2026.3202 AcceptedPOST /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"
}
}id: scn_01J…profile resolvedProject and sample metadata let teams organize repeated technical checks without pretending the API chose a representative sample.
Attach sampling-plan IDs, asset categories, and the organization’s external reference.
Retain resolved mappings, source evidence, coverage, and engine versions.
Use the result as one input to broader monitoring, user testing, and declaration work.
The API record can travel between teams because its technical identity, source mapping, and review boundary remain attached.
A versioned scan is reproducible technical evidence. The surrounding monitoring design remains an organizational responsibility.
Before EU Web Accessibility Directive becomes a production gate, review its source mapping, supported input, automation boundary, and required human checks.
Start with one asset flow, pin the profile, and keep evidence and unresolved human work attached to every result.
Automated preflight is not an accessibility certification or legal determination.