Rendered service
Versioned technical findings and coverage
Run repeatable technical checks for public-sector websites and supported documents while keeping monitoring, mobile apps, accessibility statements, feedback mechanisms, and complete service evaluation visible as broader work.
eu-wad-currentSend eu-wad-current with the asset and keep this profile’s evidence boundary in the returned result.
Automated preflight supports the technical part of the cycle while public bodies retain responsibility for broader evaluation and follow-up.
Record the scope and environment instead of presenting one URL as the whole service.
Keep EN 301 549 mappings, evidence, and coverage attached to every result.
Resolve questions that code and document structure cannot decide.
Carry verified findings and unresolved limitations into the organization’s public process.
Use baselines to distinguish new, recurring, and resolved findings.
The scan result is one layer in a wider process that also includes statements, monitoring, feedback, and organizational review.
Versioned technical findings and coverage
Format-native evidence and human checkpoints
Owned and maintained by the organization
Operational process beyond the scan
Three different references answer three different questions and should remain traceable in the result.
Defines the public-sector framework and obligations.
Supplies the applicable technical mapping for covered ICT.
Runs selected supported checks and records coverage and evidence.
The EU Web Accessibility Directive source and its legal or standards context can change. AccessPreflight pins the profile version used for a scan; your organization should re-review applicability and the source when requirements change.
Keep the profile, coverage boundary, evidence, and human-review queue attached to every result.
Automated preflight is not an accessibility certification or legal determination.