Audit checklist
- Identify whether the product is web content, software, documentation or support.
- For web pages, test clause 9 via WCAG A and AA criteria.
- Record which clauses are automated and which require manual assessment.
- Keep evidence for tested URLs, rule sets and dates.
- Use the result to update the accessibility statement and remediation plan.
How EN 301 549 relates to WCAG
Many teams search for EN 301 549 and expect a separate web checklist. In practice, web content is tested through WCAG criteria. EN 301 549 provides the European ICT framework; WCAG provides the concrete web success criteria used by most testing engines.
This distinction matters for documentation. Developers need WCAG references to fix code; procurement and compliance teams often ask for EN 301 549 language because it is the European standard named in public-sector and market-access contexts.
What an automated EN 301 549 scan can and cannot cover
Automated browser testing can detect many web content issues: missing accessible names, invalid ARIA, contrast failures, unlabeled forms and semantic problems. It cannot fully judge whether a document is understandable, whether alt text is meaningful, whether captions are accurate or whether customer support channels meet accessibility requirements.
A trustworthy report should be explicit about those limits. That honesty is better for compliance than claiming a single script proves everything.
Build an evidence trail
Keep a consistent audit trail: standard version, rulesets, tested pages, findings, fixes and verification dates. When a customer asks for accessibility evidence, this is stronger than a vague statement that the site was checked once.
FAQ
Is EN 301 549 the same as WCAG?
No. EN 301 549 is a broader European ICT standard. For web content, it references WCAG requirements, so a WCAG audit is the core of an EN 301 549 web audit.
Which EN 301 549 clauses does a website audit cover?
For ordinary web pages, clause 9 is the key area. Software, documentation and support clauses may also apply to a wider digital product and require separate review.
Can Axively generate EN 301 549 evidence?
Axively records tested URLs, rulesets and violations and maps web findings to the standards used in EU accessibility work. Manual review is still needed for non-automatable clauses.