September 19, 2025

SaaS EAA Compliance: Meeting European Accessibility Act EN 301 549 Requirements

By: David Gibson

Remember the GDPR scramble of 2018? The frantic updates to privacy policies and getting a cookie management systems in place as fines were dropping? As you very likely already know, the European Accessibility Act (EAA) went into effect in June 2025, and I agree with many others that this is GDPR’s equivalent for digital accessibility.

As GDPR transformed how companies handle data privacy, the EAA fundamentally changes how SaaS platforms must approach accessibility. But unlike GDPR, where you could update policies and data handling procedures, the EAA requires your actual software to meet EN 301 549 accessibility standards. No quick fixes. No last-minute policy updates. Your code itself must be compliant.

EAA Requirements for SaaS Platforms

The EAA mandates that any SaaS accessible to EU consumers must meet EN 301 549 standards, which incorporate WCAG 2.1 Level AA. This applies to all cloud software, web applications, and SaaS platforms that EU citizens can access—whether B2C or B2B where employees are end users.

Who Must Comply:

SaaS platforms with EU customers
Cloud-based software accessible from the EU
Web applications used by EU businesses
APIs and embedded widgets served to EU users
B2B platforms where EU citizens are end users

Microenterprise Exception: Companies with fewer than 10 employees AND under €2 million revenue may qualify for exemption, though enterprise customers often require compliance regardless.

Why Accessibility Overlays Don’t Provide EAA Compliance

Overlays don’t generally work on SaaS, however they are abundantly used on websites. So its worth noting that The European Commission rejects overlay widgets for EN 301 549 compliance. As stated: “Claims that a website can be made fully compliant without manual intervention are not realistic, since no automated tool can cover all the WCAG 2.1 level A and AA criteria.”

The Commission further warns that overlays can “interfere with the assistive technologies used by people with disabilities,” potentially making websites less accessible. The European Disability Forum and International Association of Accessibility Professionals jointly advise against overlay use, recommending engagement with accessibility experts instead.

UsableNet latest legal report showed that 25% of all lawsuits in 2024 cited an overlay widget. These widgets don’t provide compliance and they certainly don’t provide any legal cover. Instead they signal to regulators that you took shortcuts.

EAA Enforcement Status and Penalty Exposure for Cloud SaaS Providers

Since we’re early in the enforcement phase, we can just look at GDPR for indicators of what’s to come, with €4.5 billion in total fines since implementation, with individual penalties reaching €1.2 billion.

More immediate than regulatory fines: procurement rejection. European organizations now require EN 301 549 documentation (VPATs) as standard. Without proper accessibility documentation, SaaS platforms are automatically disqualified from EU government contracts, educational institutions, and enterprise deals.

Technical Requirements: WCAG 2.1 AA for SaaS

EN 301 549 compliance means meeting WCAG 2.1 Level AA across your entire platform. For SaaS applications, this includes:

Perceivable Requirements:

Alt text for all functional images
4.5:1 contrast ratio for normal text
Captions for video content
No color-only information

Operable Requirements:

Full keyboard navigation for all features
No keyboard traps in modals or dropdowns
Adjustable timeouts for sessions
Skip navigation links

Understandable Requirements:

Clear error messages with remediation guidance
Consistent navigation across the platform
Properly labeled form fields
Predictable interface behavior

Robust Requirements:

Valid HTML markup
Proper ARIA implementation
Compatibility with screen readers (NVDA, JAWS, VoiceOver)
Cross-browser assistive technology support

SaaS-Specific Accessibility Challenges

Cloud software faces unique WCAG compliance challenges beyond static websites:

Dynamic Content Updates: Real-time dashboards and notifications must announce changes to screen readers without overwhelming users. Every state change needs proper ARIA live regions.

Custom UI Components: Those beautiful custom dropdowns, date pickers, and data visualizations? They’re likely invisible to assistive technologies without proper ARIA roles, states, and keyboard navigation.

Complex Workflows: Multi-step processes, drag-and-drop interfaces, and collaborative features require careful accessibility implementation. One inaccessible modal can block entire workflows.

API and Integration Accessibility: Your embedded widgets, browser extensions, and third-party integrations must maintain accessibility. Your customers’ compliance depends on your API accessibility.

Documentation Requirements: All help content, API documentation, video tutorials, and PDF exports must meet WCAG 2.1 AA standards under EN 301 549.

Manual Testing vs Automated Testing for WCAG Compliance

Automated accessibility testing tools detect approximately 30% of WCAG issues—missing labels, contrast problems, HTML errors. The remaining 70% require manual testing with assistive technologies.

What Automated Tools Can Find:

Missing alt attributes
Color contrast violations
Missing form labels
Basic HTML structure issues
Some ARIA errors

What Requires Manual Testing:

Logical reading order
Keyboard navigation flow
Screen reader comprehension
Error message clarity
Custom component functionality
User workflow completion

For EN 301 549 compliance, you need both automated scanning AND manual testing with NVDA, JAWS, and VoiceOver screen readers by experienced accessibility professionals.

VPAT Documentation for SaaS Compliance

A Voluntary Product Accessibility Template (VPAT) documents your EN 301 549 conformance. For SaaS platforms serving EU markets, VPATs have become mandatory for procurement.

Your VPAT must accurately document:

Conformance level for each WCAG 2.1 criterion
Specific gaps with remediation timelines
Testing methodology used
Scope of evaluation (which features/pages tested)
Date of assessment

False claims in VPATs increase liability. Procurement team are increasingly scrutinizing these documents, and inaccurate VPATs can disqualify you faster than having no VPAT.

Benefits of EAA Compliance for SaaS

Accessible SaaS platforms see measurable business benefits:

Reduced customer support tickets through clearer interfaces
Improved SEO from proper semantic structure
Access to 135 million EU citizens with disabilities AND SENIORS!
Qualification for government and enterprise procurement

The cost of retrofitting accessibility later exceeds building it correctly by 3-5x. Technical debt compounds as inaccessible patterns spread through your codebase.

Path to EN 301 549 SaaS Compliance

Since we’re past the June 2025 deadline, immediate action is critical:

Comprehensive Manual Audit: Understand your actual WCAG gaps through expert testing with assistive technologies
Prioritized Remediation: Fix critical blockers first, then systematic improvement
Third-Party Verification: Confirm fixes work with real assistive technologies
VPAT Creation: Document your conformance level accurately
Ongoing Monitoring: Maintain compliance through development changes

Your existing development team should handle remediation to build internal accessibility expertise. External consultants should guide, not replace, your team’s learning.

Selecting an Accessibility Consultant

With sudden demand in recent years and only so many qualified experts in the field, most must rely more than they should on inexperienced auditors and software.

Red Flags to Avoid:

Promises of instant automated compliance
Overlay or widget solutions
No manual testing methodology
Can’t explain EN 301 549 requirements
Subscription models with minimal value

What to Require:

Manual testing with real assistive technologies
Senior consultants with 10+ years experience (all of ours are north of 21 years)
Actionable remediation guidance
Fixed-project pricing (many volume players in the space force subscriptions)
VPAT authoring expertise
References from similar SaaS companies

About Accessibility.Works

At Accessibility.Works, our team consists entirely of senior consultants with over 19 years each in digital accessibility. Our team lead serves on the W3C committees developing WCAG standards. We provide comprehensive manual audits, remediation guidance, and VPAT creation for SaaS platforms seeking real EN 301 549 compliance.

We don’t sell overlays, automated solutions, or subscription services. We deliver thorough manual testing with assistive technologies, actionable remediation guidance, and defensible documentation that stands up to procurement scrutiny.

Wrap-Up

The European Accessibility Act is current law with active enforcement. For SaaS platforms still non-compliant, every day increases legal exposure and competitive disadvantage. Automated overlays won’t save you—the EU explicitly rejects them. Only proper manual testing and systematic remediation achieve real EN 301 549 compliance.

Don’t wait for major enforcement actions. Get a comprehensive manual accessibility audit, understand your WCAG gaps, and implement real solutions immediately. Though the deadline passed, rapid compliance is still achievable with expert guidance.

Contact us for a manual accessibility audit that reveals your actual EN 301 549 compliance status and provides the roadmap to protect your business while expanding your market.