What EAA requires
European Accessibility Act (Directive 2019/882) — the short version.
- 1Directive 2019/882 applies to e-commerce, banking, e-books, transport ticketing, smartphones, ATMs, and any consumer-facing digital service sold in the EU.
- 2The compliance deadline is 28 June 2025 for most services. Microenterprises (<10 employees and <€2M turnover) are exempt but still often required by customers.
- 3National transposition varies (Germany: BFSG, France: RGAA, Spain: Ley 11/2023) but all point to EN 301 549 v3.2.1 as the technical spec.
- 4EN 301 549 incorporates WCAG 2.1 Level AA by reference for web content.
How AllyShield maps to EAA
EAA points to EN 301 549 v3.2.1 → WCAG 2.1 Level AA. Every scan you run produces a jurisdiction-tagged report that separates EAA requirements from other frameworks you might also target.
Non-text content
All non-text content has text alternatives conveying equivalent purpose.
Contrast (Minimum)
Text presentation meets at least 4.5:1 contrast ratio (3:1 for large text).
Keyboard
All functionality is operable through a keyboard interface without requiring specific timings.
Target Size
Pointer-input targets are at least 44×44 CSS pixels.
Accessibility statement
Public statement of accessibility, known limitations, and contact for feedback.
Documentation & support
Support and help documentation must themselves be accessible.
Download a signed EAA compliance certificate.
Every completed scan can produce a PDF certificate containing the scan date, AllyScore, and WCAG target level — HMAC-SHA256 signed and publicly verifiable via QR code. Attach it to vendor questionnaires, legal reviews, or customer RFPs.
Generate a certificateEAA compliance FAQ
Does the EAA apply to my company if I'm not in the EU?+
Yes if you sell covered digital services or products to EU consumers. The directive is market-based, not territory-based. Non-EU sellers on Amazon, Shopify, or their own storefronts are in scope.
What happens if I miss the June 28, 2025 deadline?+
Enforcement is per member state. Typical first step is a warning with a remediation period; continued non-compliance can trigger fines, public listing of non-compliant services, and in extreme cases withdrawal of the service from the EU market.
Is EN 301 549 the same as WCAG?+
EN 301 549 is broader — it covers ICT hardware, software, documentation, and support in addition to web content. For web content specifically, EN 301 549 incorporates WCAG 2.1 Level AA by reference. AllyShield targets the web-content subset.
Do I need an accessibility statement?+
Yes. Every covered service must publish a statement describing its conformance level, known limitations, and feedback contact. AllyShield generates one automatically from your latest scan on Pro plans and above.
Is AllyShield hosted in the EU?+
AllyShield runs on Supabase in an EU region for primary data storage, and we sign a DPA compliant with GDPR Article 28. Strict data-residency guarantees (e.g. contractual EU-only processing, regional sub-processor scoping) are available on custom Enterprise contracts — contact sales for the latest sub-processor list and residency terms.
Stop wondering. Start scanning.
Get a EAA-oriented accessibility report in minutes, then run automated monitoring between releases so issues don't regress unnoticed.
Jurisdiction slug: eaa · API: /api/scans/[id]/compliance?jurisdiction=eaa