# EN 301 549 Explained for Product Teams

> Updated 2026-10-25 - 8 min read

EN 301 549 is the European harmonised standard behind the European Accessibility Act and the EU Web Accessibility Directive - but it reads like a procurement specification, not an engineering checklist. If you're a product or engineering lead who's been handed "make sure we're EN 301 549 compliant" with no further context, this is the practical translation.

## The web/software content is almost entirely WCAG

Clause 9 (web) and Clause 11 (software) of EN 301 549 incorporate WCAG 2.1 success criteria directly by reference. If your product team has already built to WCAG 2.1/2.2 AA, you've covered the large majority of what EN 301 549 asks of your actual application.

## Where it goes beyond WCAG - and this is what product teams usually miss

- Documentation requirements (Clause 12) - user documentation and support content itself needs to be accessible, not just the product UI.
- Support-service requirements - accessible customer support channels, not just the product.
- Two-way voice communication, real-time text and relay-service support, where relevant.
- Hardware requirements (Clauses 4-8), if you ship physical devices - kiosks, terminals, ATMs - alongside software.

## What this means for a typical SaaS product team

If you're a pure web/software SaaS product with no hardware component, your real scope is Clauses 9 and 11 - essentially WCAG - plus Clause 12 (documentation and support), a much narrower slice than the full standard implies.

## Building it into your workflow, not bolting it on at the end

- Accessibility acceptance criteria in your Definition of Done, not a pre-launch audit scramble.
- A documentation and support-content review added to your content workflow, since this is the piece most engineering-led teams forget entirely.
- Automated checks (axe-core, eslint-plugin-jsx-a11y) in CI, backed by periodic manual assistive-technology testing.

## FAQ

**If we're WCAG 2.2 AA conformant, are we EN 301 549 compliant?**
For the web/software content, very close - but check your documentation and support-service accessibility too, since those are real EN 301 549 requirements WCAG doesn't cover at all.

**Do we need a separate EN 301 549 VPAT, or does our WCAG VPAT cover it?**
A dedicated EN 301 549 edition VPAT (or the INT edition) is what EU buyers and compliance teams expect to see by name, even if the underlying testing overlaps heavily with your WCAG work.