The European Accessibility Act explained 🔗 **Source:** [The European Accessibility Act explained](https://www.youtube.com/watch?v=GEvgdJqg3jM) > [!note]+ Document Notes > tags: [accessibility, european-legislation, wcag, eaa, compliance] > author: Rianne Reehl > source: WordCamp Europe 2024 > reference: https://www.youtube.com/watch?v=GEvgdJqg3jM > date created: 2024-12-19 14:30 > > # 🏷️ Title: The European Accessibility Act Explained > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Assess EAA compliance status — audit existing e-commerce and service websites #accessibility - [H2] Train development team on WCAG 2.2 AA standards — integrate into workflow #training - [H3] Create accessibility statement and complaint process — legal compliance #documentation ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Rianne Reehl's slides](https://riannereehl.com/wcu24) - [OverlayFactSheet.com](https://overlayfactsheet.com) ## 📝 Summary - The European Accessibility Act (EAA) will be enforced starting June 28, 2025, requiring e-commerce websites and digital services to comply with WCAG 2.1 AA standards - Companies selling products or services to EU citizens must comply, with exceptions for businesses under 10 employees and €2M revenue - Penalties vary by country but can include significant fines (up to €90,000 in Spain) and imprisonment (up to 18 months in Ireland) - Best practices include independent audits, team training, gradual implementation, and accessibility statements - Accessibility overlays are not a valid solution and cannot make inaccessible websites compliant ## 📖 Main Content The European Accessibility Act represents a significant shift in digital accessibility legislation across the EU. Building on earlier directives for government websites (2016) and products/services (2019), the EAA mandates accessibility compliance for commercial digital services starting June 2025. The legislation covers a broad range of digital touchpoints including e-commerce websites, mobile services, banking applications, and electronic ticketing systems. Companies must meet EN 301 549 standards, which incorporate WCAG 2.1 AA guidelines for web accessibility. Implementation varies significantly across EU member states. Some countries like Spain have already begun enforcement with substantial penalties, while others are still developing their regulatory frameworks. The Netherlands implemented the legislation just two months before this presentation, highlighting the inconsistent rollout. Key compliance elements include conducting independent accessibility audits, training development teams, integrating accessibility into workflows, and maintaining transparent accessibility statements. The speaker emphasizes that accessibility overlays—JavaScript widgets claiming to provide instant compliance—are ineffective and potentially problematic. ## 🗒️ Notes #### ⏱️ [00:00](https://www.youtube.com/watch?v=GEvgdJqg3jM?t=0) — [H1] Introduction and Speaker Background - Key idea: Rianne Reehl introduces herself as web accessibility specialist from Netherlands - Evidence: "freelance accessibility consultant she works for NL design system the WordPress agency level level and the form plug-in gravity forms" #### ⏱️ [05:23](https://www.youtube.com/watch?v=GEvgdJqg3jM?t=323) — [H2] Brief History of EU Accessibility Legislation - Key idea: European accessibility legislation evolved from government-only (2016) to commercial services (2019) - Evidence: "2016 the EU member states agreed on a directive 2016 sl212 and these are accessibility requirements for websites and mobile apps for public sector bodies" #### ⏱️ [07:45](https://www.youtube.com/watch?v=GEvgdJqg3jM?t=465) — [H3] Products and Services Covered by EAA - Key idea: EAA covers both hardware products and digital services including e-commerce - Evidence: "computers and operating systems...e-commerce websites mobile services electronic ticketing ebooks...all these Services must be accessible" #### ⏱️ [09:12](https://www.youtube.com/watch?v=GEvgdJqg3jM?t=552) — [H2] Implementation Timeline and Status - Key idea: Member states had until June 2022 to implement, enforcement begins June 2025 - Evidence: "June 28th 2022 all member states must have implemented this legislation...the Netherlands only implemented this legislation two months ago" #### ⏱️ [10:30](https://www.youtube.com/watch?v=GEvgdJqg3jM?t=630) — [H3] Who Needs to Comply - Key idea: Companies selling services to EU must comply, with small business exceptions - Evidence: "companies with less than 10 employees and a global turnover of less than2 million EUR don't need to comply" #### ⏱️ [12:15](https://www.youtube.com/watch?v=GEvgdJqg3jM?t=735) — [H2] Technical Standards - EN 301 549 and WCAG - Key idea: EAA references EN 301 549 standard which incorporates WCAG 2.1 AA for websites - Evidence: "the part of En 305 549 that covers web accessibility is actually week level able a version 2.1" #### ⏱️ [14:20](https://www.youtube.com/watch?v=GEvgdJqg3jM?t=860) — [H3] Global Scope and Enforcement - Key idea: Non-EU companies selling to EU must comply, penalties are emerging - Evidence: "Spanish Airline Berling...got fined €90,000 because their website isn't accessible" #### ⏱️ [16:45](https://www.youtube.com/watch?v=GEvgdJqg3jM?t=1005) — [H2] Compliance Preparation Strategy - Key idea: Aim for WCAG 2.2 AA and conduct independent audits for proof of compliance - Evidence: "aim for wak 2.2 AA for websites that a pretty safe assumption...refer to a recent independent audit" #### ⏱️ [18:30](https://www.youtube.com/watch?v=GEvgdJqg3jM?t=1110) — [H3] WCAG Success Criteria Overview - Key idea: WCAG has three levels with AA being global standard requiring 55 success criteria - Evidence: "if you meet double A that's 31 success criteria double A is 55 this is a plus 24 extra" #### ⏱️ [20:15](https://www.youtube.com/watch?v=GEvgdJqg3jM?t=1215) — [H2] Implementation Process - Key idea: Start with audit baseline, create plan, train team, integrate into workflow - Evidence: "let someone one provide an audit for you as a basement measurement...train your team please" #### ⏱️ [23:40](https://www.youtube.com/watch?v=GEvgdJqg3jM?t=1420) — [H3] Accessibility Statements and Complaint Handling - Key idea: Provide accessibility statements and take user complaints seriously - Evidence: "take complaints seriously this is super important someone with a disability doesn't know how how to use your website" #### ⏱️ [25:50](https://www.youtube.com/watch?v=GEvgdJqg3jM?t=1550) — [H2] Warning Against Accessibility Overlays - Key idea: Accessibility overlays don't work and are opposed by accessibility experts - Evidence: "you cannot turn an inaccessible website into an accessible one by just adding a few lines of JavaScript" #### ⏱️ [28:15](https://www.youtube.com/watch?v=GEvgdJqg3jM?t=1695) — [H3] Gravity Forms Success Case Study - Key idea: Gravity Forms demonstrates comprehensive accessibility implementation process - Evidence: "they set a goal and that was in 2018...they wanted to comply with week AA 2.1" #### ⏱️ [31:20](https://www.youtube.com/watch?v=GEvgdJqg3jM?t=1880) — [H2] Personal Story and Motivation - Key idea: Speaker shares personal story about parents struggling with web accessibility - Evidence: "my mother got angry at bad uxx things that changed she couldn't understand her interface anymore" ## 📚 References - [Rianne Reehl's presentation slides](https://riannereehl.com/wcu24) - [Overlay Fact Sheet](https://overlayfactsheet.com) - [WebAIM WAVE accessibility tool](https://wave.webaim.org) - [Ally Collective learning platform](https://allyco) ## 🗣️ Paraphrase - The European Accessibility Act will require e-commerce and digital service companies to make their websites accessible to people with disabilities starting in June 2025, with significant financial and legal penalties for non-compliance - Companies should aim for WCAG 2.2 AA compliance through systematic auditing, team training, and workflow integration rather than relying on quick fixes like accessibility overlay widgets - Success requires organizational commitment from leadership, proper budget allocation, user complaint processes, and viewing accessibility as a core quality requirement alongside performance and security ## 📰 Newsletter The European Accessibility Act is coming to WordPress sites across the EU in just one year! If you're running e-commerce or providing digital services to European customers, June 28, 2025 is a critical compliance deadline. **What You Need to Know:** - EAA requires WCAG 2.1 AA compliance (aim for 2.2 AA to be future-ready) - Applies to companies selling products/services to EU citizens - Small business exception: under 10 employees and €2M revenue - Penalties can reach €90,000+ fines and potential imprisonment **Getting Ready:** Start with an independent accessibility audit to establish your baseline. Train your team on accessibility principles and integrate compliance into your development workflow. Create an accessibility statement and user feedback process. **Avoid This Trap:** Accessibility overlay plugins that claim instant compliance don't work and violate best practices. Real accessibility requires proper coding, design, and content practices. Resources: [Learn WordPress Accessibility](https://learn.wordpress.org/), [WebAIM Guidelines](https://webaim.org/), [Overlay Fact Sheet](https://overlayfactsheet.com/) ## ✅ Action Items #### WordPress - Core: Integrate EAA compliance considerations into core accessibility roadmap - Themes: Develop accessibility review criteria aligned with WCAG 2.2 AA standards - Plugins: Create guidance for plugin developers on accessibility compliance - Documentation: Expand accessibility documentation with EAA-specific guidance - Community: Organize accessibility training events and workshops for European WordPress users #### OSPO - Policy & Governance: Develop accessibility compliance policies for open source projects - Developer Support: Provide training on accessibility testing tools and methodologies - Community Engagement: Fund accessibility audits and improvements in key WordPress projects #### Community - Meetups: Host EAA compliance workshops and training sessions - WordCamps: Include accessibility tracks focused on legal compliance - Contributors: Establish accessibility testing protocols for core contributions ## 🧪 Hypotheses - Companies will initially resist accessibility compliance due to perceived costs but will adopt it rapidly as enforcement begins - Accessibility overlay usage will increase initially but decline as their ineffectiveness becomes apparent - WordPress themes and plugins with strong accessibility features will gain market advantage in European markets - Legal enforcement will vary significantly between EU member states creating compliance confusion ### 📊 Methodology - Survey WordPress agencies and businesses about current accessibility practices and EAA awareness - Analyze accessibility compliance rates in European WordPress sites before and after June 2025 - Track adoption patterns of accessibility tools and services in the WordPress ecosystem ### ❓ Questions - How will enforcement inconsistencies across EU member states affect compliance strategies? - What impact will EAA have on WordPress plugin and theme marketplace dynamics? - How can WordPress core better support automatic accessibility compliance checking? ### 🔮 Future Research - Longitudinal study of accessibility compliance costs versus business benefits - Analysis of accessibility overlay effectiveness versus proper implementation - Investigation of user experience improvements from accessibility implementations ### 💡 Implications - Practice: WordPress developers must integrate accessibility testing into standard workflows - Policy: Need for clear WordPress accessibility standards and review processes - Security: Accessibility overlays may introduce security vulnerabilities - Education: Urgent need for widespread accessibility training in WordPress community - Funding: Budget allocation required for accessibility audits, training, and remediation ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade (technical content with specialized terminology) #### 👀 Visual learners - Present: Slides with clear legislation timeline and compliance flowcharts - Improve: Visual comparison charts of WCAG levels, penalty visualization by country #### 🔊 Aural learners - Present: Full video presentation with clear verbal explanations - Improve: Audio-only version, podcast format for key compliance steps #### 🗣️ Verbal learners - Present: Clear definitions of EAA, WCAG, overlay terminology - Improve: Glossary of accessibility terms, analogy-based explanations #### 🧩 Kinesthetic learners - Present: Gravity Forms case study provides concrete implementation example - Improve: Step-by-step compliance checklist, hands-on audit exercises #### 🧠 Logical learners - Present: Clear timeline from 2016 directive to 2025 enforcement - Improve: Decision tree for compliance requirements, cost-benefit analysis #### 🧑‍🤝‍🧑 Social learners - Present: Q&A session with community interaction - Improve: Discussion forum for compliance questions, peer review groups #### 🧘‍♀️ Solitary learners - Present: Self-assessment questions about business compliance needs - Improve: Individual compliance worksheets, self-paced learning modules #### 🌿 Naturalistic learners - Present: Personal story about parents' web accessibility challenges - Improve: Real-world user experience examples, ecosystem thinking about accessibility ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Well-structured presentation with clear headings and flow - Improve: Ensure slide content has proper alt text, transcript availability #### Keyboard navigation - Present: Standard presentation format accessible via keyboard - Improve: Interactive elements should be keyboard accessible #### Contrast and readability - Present: Clear slide design with good contrast - Improve: Verify all slide text meets WCAG contrast requirements #### Text resizing and reflow - Present: Slides appear to scale appropriately - Improve: Test slides at 200% zoom for readability #### Media and captions - Present: Video has audio narration - Improve: Closed captions should be available for the video #### Standards reference - Content directly addresses WCAG 2.1/2.2 AA compliance requirements ### 🌍 DEIB Assessment #### Cultural breadth - Present: European focus with acknowledgment of global accessibility standards - Improve: Include examples from diverse EU member states, cultural accessibility considerations #### Inclusive language - Present: Uses person-first language ("people with disabilities") - Improve: Expand inclusive terminology throughout, avoid ableist assumptions #### Neurodiversity support - Present: Structured presentation with clear sections - Improve: Provide content warnings for compliance anxiety, chunked information delivery #### Representation - Present: Female accessibility expert presenting, diverse disability examples - Improve: Include broader range of disability experiences, intersectional considerations #### Psychological safety - Present: Acknowledges compliance fears and provides supportive guidance - Improve: Address anxiety about legal consequences, provide reassurance about gradual implementation ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Clear progression from EU directives to specific compliance requirements - Inductive strength: Gravity Forms case study supports general implementation principles - Causal reasoning: Links inaccessible websites to user exclusion and legal <!-- deep-read:sections end -->