SaaS companies that sell into the European market fall under the European Accessibility Act (EAA) if their product qualifies as a service provided to consumers in the EU. The law took effect on June 28, 2025, and applies to digital services offered within EU member states regardless of where the company is headquartered. Preparing means understanding what the EAA covers, confirming your product is in scope, and aligning your web app with WCAG 2.1 AA conformance.
A US-based or UK-based SaaS company with EU customers does not get an automatic exemption. The EAA applies based on where the service is consumed, not where the company is incorporated.
| Area | What SaaS Companies Need to Know |
|---|---|
| Scope | SaaS products serving EU consumers in covered categories are subject to EAA requirements |
| Technical Standard | WCAG 2.1 AA conformance is the practical baseline for digital accessibility under the EAA |
| Timeline | The EAA became applicable on June 28, 2025 |
| Documentation | Companies must maintain records showing how accessibility requirements are met |
| Enforcement | Each EU member state designates a market surveillance authority with power to issue penalties |
Does the EAA Apply to SaaS Companies Outside the EU?
Yes. The EAA regulates services provided to consumers within the EU. If a SaaS company based in the United States, Canada, or anywhere else has paying customers in an EU member state, and the product falls within a covered service category, the EAA applies.
Covered service categories include e-commerce, banking and financial services, electronic communications, and access to audiovisual media. SaaS products that enable or facilitate these services for EU consumers are in scope.
The determining factor is whether the service reaches EU consumers, not the company’s physical location. A SaaS company with no EU office but thousands of EU subscribers still carries obligations under the act.
What the EAA Requires from Digital Services
The EAA requires that covered digital services be perceivable, operable, understandable, and robust. These four principles map directly to the POUR framework in WCAG. In practice, WCAG 2.1 AA conformance satisfies the technical accessibility expectations of the EAA for web-based products.
For SaaS companies, this means the entire user-facing application needs to conform. Login screens, dashboards, settings panels, billing flows, onboarding sequences, help documentation, and any embedded third-party components all fall within scope.
Accessibility is not limited to the marketing website. The product itself is the service, and the product is what must be accessible.
Step 1: Confirm Whether Your Product Is in Scope
Start by reviewing the EAA scope for products and services. Not every SaaS product is covered. The act targets specific categories of services. If your product does not fall into a covered category and is not used in the provision of a covered service, it may not be subject to EAA requirements.
If there is any ambiguity, treat the product as in scope. The cost of conforming to WCAG 2.1 AA is far lower than the cost of being found non-compliant after an enforcement action.
Step 2: Conduct a WCAG 2.1 AA Audit on Your Digital Asset
An accessibility audit (manual) conducted by a qualified third party is the only way to identify where your product stands against WCAG. Automated scans cannot determine conformance. They can only detect approximately 25% of accessibility issues. An audit evaluates your product across real user flows through expert analysis, providing the complete picture that scans are unable to deliver.
Accessible.org audits are fully manual and test against every applicable WCAG 2.1 AA criterion. The audit report identifies each issue, maps it to the relevant success criterion, and provides remediation guidance your development team can act on.
For SaaS products, the audit should cover representative pages and application states, including authenticated views, form interactions, dynamic content, modals, and error handling.
Step 3: Remediate and Track Progress
Once the audit report is in hand, the development team works through each identified issue. Prioritization matters. Risk Factor and User Impact prioritization formulas help teams address the most consequential issues first rather than working through a flat list.
The Accessibility Tracker Platform is built for this stage. It takes audit results and turns them into a managed workflow where each issue is assigned, tracked, and validated through resolution. For SaaS companies managing multiple product areas or release cycles, a dedicated tracking system prevents issues from losing freshness in a backlog.
Step 4: Build Documentation
The EAA includes explicit documentation obligations. Service providers must be able to demonstrate how their product meets accessibility requirements. This goes beyond a one-time audit report.
Documentation should include the audit report itself, a record of remediation actions taken, an accessibility statement, and ongoing records of conformance monitoring. If your product changes frequently, your documentation needs to reflect that cadence.
Companies that maintain a living record of their accessibility work are in a stronger position during any market surveillance review than those who can only point to a single past audit.
Step 5: Establish an Ongoing Process
EAA compliance is not a one-time project. SaaS products ship updates constantly. Each release can introduce new accessibility issues. A sustainable process includes accessibility checks during development, periodic re-audits, and a system for tracking new issues as they appear.
Teams that integrate accessibility into their development workflow catch issues before they reach production. Teams that treat accessibility as an annual checkbox accumulate technical debt that compounds with every release.
What Happens If a SaaS Company Is Not Compliant?
Each EU member state sets its own enforcement mechanisms and penalties. Market surveillance authorities can require corrective action, restrict access to the market, or impose fines. The specifics vary by country, but the directive gives member states broad authority to act.
Beyond enforcement, non-compliance carries commercial risk. EU procurement processes increasingly require evidence of accessibility conformance. Enterprise buyers in Europe ask for ACRs (Accessibility Conformance Reports) and accessibility statements as part of vendor evaluation. A SaaS company that cannot produce these documents loses deals to competitors who can.
Do SaaS Companies Need a VPAT/ACR for the EAA?
The EAA does not formally require a VPAT or ACR. But the practical reality is that European enterprise buyers request them. An ACR documents how your product maps to accessibility standards criterion by criterion. It is the clearest way to communicate your conformance posture to a potential customer or a regulatory body.
For SaaS companies already producing ACRs for US procurement (Section 508 or WCAG edition), extending coverage to include the EN 301 549 edition aligns the document with European expectations.
Can a SaaS Company Claim Disproportionate Burden?
The EAA includes a disproportionate burden exception, but it is narrow. A company must demonstrate through documented assessment that meeting a specific requirement would impose a burden that is disproportionate relative to the benefit. This is evaluated on a per-requirement basis, not as a blanket exemption for the entire product.
For most SaaS companies with meaningful revenue from EU customers, the exception is unlikely to apply broadly. It exists for edge cases, not as a compliance strategy.
How quickly should a SaaS company act if it is not yet EAA compliant?
Immediately. The EAA went into effect on June 28, 2025. Companies that have not started are already behind. An audit gives you a clear picture of the gap, and remediation can begin the same week the report is delivered.
Does the EAA apply to B2B SaaS products?
The EAA primarily targets services provided to consumers (B2C). A purely B2B SaaS product with no consumer-facing element may fall outside scope. However, if the product is used in the provision of a covered service to consumers, the obligations can extend. When the line is unclear, conforming to WCAG 2.1 AA removes the risk entirely.
What WCAG version does the EAA reference?
The EAA references the EN 301 549 standard, which currently maps to WCAG 2.1 AA. Auditing to WCAG 2.1 AA satisfies the technical accessibility requirements for digital services under the act.
SaaS companies that sell into Europe and wait for enforcement to force action will spend more, move slower, and carry more risk than those who prepare now. The requirements are clear, the standard is established, and the tools to get there exist today.
Contact Accessible.org to start an EAA compliance audit or build a preparation plan for your SaaS product.
