European Accessibility Act is reshaping how products and services in the EU are designed, built, and delivered so that people with disabilities can use them on equal terms. If you make, sell, or provide digital products or consumer-facing services in the European market, this law matters to you—whether you’re a growing startup, a multinational, or a public-facing platform.
What the law is and why it exists
The Act is an EU directive (2019/882) that harmonizes accessibility requirements across Member States. Before it, companies faced a patchwork of national rules and voluntary standards. Now, one common set of rules helps businesses scale accessible products across the EU and gives 100+ million Europeans with disabilities better access to essential products and services.
Key dates and transition periods
- National adoption: EU countries had to transpose the directive into national law by 28 June 2022.
- Enforcement start: Requirements generally apply from 28 June 2025.
- Transition for existing offerings:
- Products placed on the market before 28 June 2025 can usually continue to be sold without redesign.
- Service contracts concluded before 28 June 2025 may continue under previous rules until 28 June 2030.
Check your country’s specific law for any nuances, as national authorities define penalties and some details.
Who must comply
The law covers manufacturers, importers, distributors, and service providers offering covered products or services in the EU, regardless of where the company is based. Microenterprises that provide services may have simplified obligations in some countries, but they’re not automatically out of scope. The “disproportionate burden” and “fundamental alteration” clauses may apply in limited cases, but you must document and justify any claim thoroughly.
What products and services are in scope The Act focuses on everyday consumer-facing technologies and services, including:
- Computers, smartphones, tablets, ATMs, ticketing and check-in machines, payment terminals, e-readers
- Telephony and electronic communications services
- Audiovisual media services platforms (e.g., streaming interfaces, EPGs)
- E-books and dedicated e-reading software
- E-commerce services and marketplaces
- Transport-related services (e.g., websites, apps, and ticketing for air, rail, bus, maritime)
- Banking services interfaces (e.g., online banking portals and apps)
- Emergency communication to the single European emergency number 112
European Accessibility Act: what it requires in practice The Act defines “functional accessibility requirements.” Rather than prescribing one technical solution, it tells you what outcomes people must experience. Common themes include:
- Perceivable information: Provide text alternatives for non-text content; ensure content can be presented in different ways without losing meaning.
- Operable interfaces: Support keyboard-only use, logical focus order, and sufficient time for interactions; avoid content that causes seizures.
- Understandable interactions: Clear labels, consistent navigation, predictable behavior, and error prevention.
- Robust content: Compatibility with assistive technologies (screen readers, magnifiers, switch devices), using proper semantics.
- Accessible customer support and information: Accessible instructions, product information, and user support channels.
- Interoperability: Where relevant, devices and software must expose accessibility features to assistive technologies.
- Documentation and conformity: Technical documentation, user information, CE marking for relevant products, and declarations of conformity.
Relationship to standards (WCAG and EN 301 549)
- Web and software: The widely used benchmark is WCAG (Web Content Accessibility Guidelines), typically Level AA. In the EU context, the ICT accessibility standard EN 301 549 incorporates WCAG for web, mobile apps, and software and adds requirements for documents, hardware, and biometrics.
- Presumption of conformity: Following EU-harmonized standards, when cited in the Official Journal, provides a “presumption of conformity.” Keep an eye on updates, as standards continue to evolve alongside the Act’s implementation.
How enforcement works
- Market surveillance: National authorities can request evidence, test products, and audit services.
- Penalties: Set by each Member State and may include fines, withdrawal from market, or corrective action orders.
- Feedback and remedy: Service providers may need to publish accessibility statements and offer user feedback channels to report issues and request accessible alternatives.
How to get ready: a practical roadmap 1) Map your scope
- Inventory all EU-facing digital channels and devices: websites, apps, kiosks, self-service terminals, e-readers, media platforms, payment flows, and customer support.
- Identify the legal basis in each EU market where you operate and note any sector-specific guidance.
2) Set your success criteria
- For web, apps, software, and content, set WCAG 2.1 AA (or later) as your baseline, via EN 301 549 where applicable.
- For hardware, map requirements for tactile controls, audio output, visual contrast, captions, and compatibility with assistive devices.
3) Design and build for accessibility
- Adopt inclusive design principles from the start: color contrast, clear typographic hierarchy, captions/transcripts, resizable text, and keyboard operability.
- Use semantic HTML, ARIA only when necessary, and accessible patterns for components like modals, carousels, and forms.
- Ensure embedded media offers captions, audio descriptions (where appropriate), and transcripts.
4) Test with people and tools
- Combine automated testing with manual audits and assistive technology testing (screen readers such as NVDA, JAWS, VoiceOver; keyboard-only navigation; switch control).
- Run usability sessions with participants with diverse disabilities to validate real-world experience.
5) Document and declare
- Maintain technical documentation: accessibility features, test results, risk assessments, and any justified claims of disproportionate burden.
- For products requiring CE marking, include accessibility in your conformity assessment and declaration of conformity.
- Publish accessibility statements for services and provide feedback and complaint mechanisms.
6) Train your teams
- Upskill designers, developers, content authors, QA, and support staff on accessibility best practices.
- Update procurement processes to require accessibility in vendor contracts and RFPs, including acceptance criteria and testing obligations.
7) Govern and monitor
- Establish accessibility ownership: appoint a lead or committee, define KPIs, and track compliance across releases.
- Integrate accessibility checks into CI/CD pipelines and regression testing to prevent backsliding.
What good looks like across channels
- Websites and e-commerce:
- Consistent headings and landmarks for navigation.
- Clear, descriptive link text (“Add to cart – Blue Jacket, Size M”) rather than “Click here.”
- Accessible forms with labels, instructions, and helpful error messages.
- Keyboard-operable product galleries and checkout flows; no keyboard traps.
- Mobile apps:
- Proper labeling for controls, meaningful accessibility hints, and support for dynamic text sizing.
- Focus management for modals and in-app notifications.
- Sufficient contrast and touch target sizes.
- Self-service terminals:
- Tactile keypads or alternatives, audio guidance via headphone jack, adjustable volume, and screen magnification.
- Physical reach ranges and placement that support wheelchair users.
- Media and e-books:
- Captions and subtitles, audio description where needed, accessible players with keyboard control.
- EPUB with proper semantics and navigable structure; avoid images of text.
Common pitfalls to avoid
- Treating accessibility as a one-time retrofit rather than an ongoing practice.
- Relying only on automated scanners; they catch a fraction of issues.
- Providing accessibility features that are hidden, incomplete, or undocumented.
- Ignoring non-web assets: PDFs, kiosks, emails, and customer support scripts are also in scope.
Business benefits beyond compliance
- Larger addressable market: Better experiences for people with disabilities, older adults, and users in situational limitations.
- Stronger SEO, faster performance, and higher conversion due to cleaner structure and better content.
- Reduced legal risk and smoother cross-border expansion thanks to harmonized requirements.
- Enhanced brand trust and employee pride.
FAQs
- Does it apply outside the EU? If you offer covered products or services to EU consumers, yes—even from abroad.
- Are microenterprises exempt? Some service-related obligations may be simplified, depending on national law, but do not assume full exemption.
- Can I claim disproportionate burden? Only if you’ve assessed, documented, and considered alternatives; authorities can review your assessment.
- Is WCAG 2.2 required? Follow the latest applicable standard in your market. Planning for WCAG 2.2 AA is prudent to future-proof.
Next steps
- Confirm the law transposition in your target countries and any sector guidance.
- Conduct a gap analysis against WCAG/EN 301 549.
- Prioritize fixes for high-impact user journeys (e.g., account creation, checkout, payments).
- Build accessibility into your product lifecycle and vendor contracts.
The Act is both a compliance milestone and an opportunity. Teams that start now—auditing, fixing, training, and governing—will not only meet legal obligations by the enforcement date but also deliver better, more resilient experiences for everyone.
Further Reading