Web requirements
WCAG-derived web conditions remain connected to the EN 301 549 clause structure.
Preflight web content against the current EN 301 549 V3.2.1 web profile. Keep its WCAG 2.1 foundation and the standard’s additional ICT requirements visible as a pinned technical mapping.
en-301-549-v3.2.1-webSend en-301-549-v3.2.1-web with the asset and keep this profile’s evidence boundary in the returned result.
The profile is a cross-standard map. Findings keep both the AccessPreflight rule identity and the technical reference needed for review.
WCAG-derived web conditions remain connected to the EN 301 549 clause structure.
Applicable requirements outside the web-only clause remain distinguishable from the WCAG mapping.
The profile records the mapping version; it does not infer which law or procurement contract applies.
The page separates the shared web criteria from applicable requirements that live elsewhere in the ICT standard.
The profile is a technical map: web conditions lead, while generic ICT requirements and review boundaries remain attached.
WCAG-backed web requirements
Applicable cross-cutting conditions
Versioned technical lineage
Kept outside the automated verdict
The EN 301 549 web 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.