EN 301 549 web accessibility API
Submit a rendered page against the EN 301 549 V3.2.1 web profile. Findings retain their clause lineage and related WCAG mapping so procurement and engineering can work from the same technical record.
For public-sector integrators and vendors with EN 301 549 acceptance criteria
en-301-549-v3.2.1-web@1.2.0202 AcceptedPOST /v1/scans
Idempotency-Key: EU-ICT-2026-114
{
"asset": {
"type": "url",
"url": "https://portal.example/service"
},
"profiles": [
"en-301-549-v3.2.1-web@1.2.0"
],
"metadata": {
"tender_id": "EU-ICT-2026-114"
}
}id: scn_01J…profile resolved- Mapping
- EN 301 549 V3.2.1 web clauses
- Lineage
- Clause + related WCAG criterion
- Handoff
- Technical acceptance evidence
Preserve the clause path in every actionable finding.
Engineering gets a source-locatable failure while the acceptance record retains the standard reference and profile version.
- Profile
- en-301-549-v3.2.1-web@1.2.0
- Clause
- Mapped EN 301 549 requirement
- Related standard
- Applicable WCAG success criterion
- Location
- URL + selector + rendered evidence
- Engine
- Pinned browser and rule versions
- Review
- Untested or partially tested requirements
Make technical acceptance reproducible across delivery stages.
The same profile can travel from supplier QA to the receiving organization without reducing the standard to a screenshot or spreadsheet status.
- Supplier
Scan before handoff
Attach the tender or work-package ID as tenant-safe metadata.
- Integrator
Resolve findings at the source
Use clause lineage and browser evidence to route the defect.
- Buyer
Review the same versioned record
Inspect coverage and unresolved human requirements before acceptance.
Package engineering proof and technical acceptance context together.
Each layer answers a different handoff question without turning a web scan into a procurement conclusion.
- Finding
Source-locatable failure
Selector, observed state, and repair guidance
- Mapping
Clause lineage
EN requirement and related WCAG criterion
- Acceptance
Open review record
Untested requirements and owner decisions
Inspect the policy behind the API profile.
Before EN 301 549 web becomes a production gate, review its source mapping, supported input, automation boundary, and required human checks.
Put the EN 301 549 web 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.
Automated preflight is not an accessibility certification or legal determination.