guide
EN 301 549 for saas & software: requirements, priorities, and audit checklist
EN 301 549 compliance for SaaS products requires applying EN 301 549 — Accessibility requirements for ICT products and services to the specific failure points typical of the saas & software industry — including component libraries without semantic markup, modal dialogs that trap focus incorrectly, data tables without programmatic structure.
Does EN 301 549 apply to SaaS products?
EN 301 549 is the harmonised European standard for digital accessibility, maintained jointly by ETSI, CEN, and CENELEC, that incorporates WCAG 2.1 AA for web and mobile content and adds requirements for hardware, software, documentation and support — and is the technical reference for both the European Accessibility Act and the Web Accessibility Directive.
SaaS & Software accessibility — the lay of the land
SaaS vendors face accessibility through two channels: their own marketing site (subject to ADA Title III), and their product (subject to procurement-driven VPAT requirements and EAA scope for consumer services). Enterprise procurement increasingly requires a current VPAT.
Where EN 301 549 bites hardest in SaaS products
• Component libraries without semantic markup
• Modal dialogs that trap focus incorrectly
• Data tables without programmatic structure
• Drag-and-drop without keyboard alternatives
• Status messages not announced to AT (4.1.3)
Remediation priorities
• Core admin / dashboard navigation
• Forms, validation, and error recovery
• Tables, charts, and data export
• Component library (button, input, modal, menu primitives)
• Embedded customer-facing widgets
How to comply with EN 301 549 on a SaaS & Software site
1. Identify in-scope chapters: Map your product across chapters 5–13. A web app covers chapters 9, 11, 12.
2. Test WCAG 2.1 AA: Chapter 9 references WCAG directly.
3. Cover hardware/software: Add chapter 5/11 requirements where applicable.
4. Document conformance: Produce VPAT 2.5 EU or equivalent ACR.
Sources
- EN 301 549 v3.2.1 — ETSI
- Section508.gov VPAT — GSA
FAQ
Frequently asked questions
Cited answers. Sourced. Updated as standards and case law change.
Does EN 301 549 apply to saas & software websites?
EN 301 549 is the harmonised European standard for digital accessibility, maintained jointly by ETSI, CEN, and CENELEC, that incorporates WCAG 2.1 AA for web and mobile content and adds requirements for hardware, software, documentation and support — and is the technical reference for both the European Accessibility Act and the Web Accessibility Directive.
What are the most common EN 301 549 failures in SaaS products?
Component libraries without semantic markup Modal dialogs that trap focus incorrectly Data tables without programmatic structure
What conformance level should a saas & software site target?
WCAG 2.2 Level AA is the consensus target for legal compliance and the level referenced by virtually every national accessibility law.
Do SaaS vendors need a VPAT?
Increasingly yes. Enterprise procurement teams — particularly in higher education, healthcare, government, and large finance — require a current VPAT/ACR before purchase. Federal vendors require Section 508 VPATs explicitly.
Is the SaaS marketing site or the product more important for accessibility?
Both are in scope under different regimes. The marketing site is ADA Title III (public accommodation). The product is procurement-VPAT-driven and increasingly EAA-driven for consumer offerings. A vendor should not treat one as adequate cover for the other.
What is the most cost-effective way for a SaaS team to start?
Three steps: (1) accessibility-instrumented component library so new screens inherit conformance; (2) axe-core in CI for regression; (3) annual manual audit against WCAG 2.2 AA with an IAAP-certified team.
Stop guessing. Get the audit a Fortune 500 a11y team would have written.
Free audit on your live URL. No sign-up. IAAP-format report. Ready in hours.
founders@accessivepath.com · +977 9851094056