Navigating EAA Compliance in Testing.pdf
0 likes34 views
Designed for software testing practitioners and managers, this session provides the knowledge and tools needed to be prepared, proactive, and positioned for success with EAA compliance. See the full session recording at https://applitools.info/0qj
Navigating EAA Compliance in Testing.pdf
- 1. Navigating the European Accessibility Act Heather Vercillo Sr. PMM @ Applitools
- 2. What is the EAA? EU Legislation Ensures digital products and services are accessible to people with disabilities. Global Impact Applies to all companies offering products in the EU, regardless of location. Enforcement Date Compliance required by June 28, 2025.
- 3. Products and Services Impacted ✅ Computers and operating systems ✅ ATMs, ticketing and check-in machines ✅ Smartphones ✅ TV equipment related to digital television services ✅ Telephony services and related equipment ✅ Access to audio-visual media services such as television broadcast and related consumer equipment ✅ Services related to air, bus, rail and waterborne passenger transport ✅ Banking services ✅ E-books ✅ E-commerce
- 4. Core Accessibility Principles 4 1 2 3 Perceivable Information must be clearly presented for all users Robust Works across devices and assistive technologies Understandable Content must be intuitive and straightforward Operable Easy navigation with various input methods
- 5. Compliance Standards Web Content Accessibility Guidelines provide detailed criteria for making web content accessible. ● Text alternatives ● Navigability ● Readability ● Predictability WCAG 2.1 (Level AA) European standard for ICT products and services. ● Includes WCAG 2.1 and more ● Comprehensive approach ● Standardized across EU ● Covers all digital technologies EN 301 549
- 6. POUR Principle Example WCAG 2.1 AA Success Criterion Brief Description for Dev/QA Teams Perceivable 1.1.1 Non-text Content Ensure all images, icons, and multimedia have appropriate text alternatives (alt text, transcripts). 1.4.11 Non-text Contrast Ensure graphical elements and UI component states have a 3:1 contrast ratio against adjacent colors. Operable 2.1.1 Keyboard Ensure all functionality is operable using only a keyboard interface. 2.5.8 Target Size (Minimum) Ensure touch targets are at least 24x24 CSS pixels (WCAG 2.2 AA standard, good practice for EAA). Note: EAA references WCAG 2.1, but 2.2 is best practice. Understandable 3.1.1 Language of Page Specify the default human language of the page programmatically (e.g., <html lang="en">). 3.2.4 Consistent Identification Use consistent labels and icons for components with the same functionality across pages. Robust 4.1.1 Parsing Write valid HTML with complete tags, proper nesting, unique IDs, and no duplicate attributes. 4.1.2 Name, Role, Value Ensure UI components (especially custom ones) expose their name, role, state, and value to assistive technologies, often using ARIA.
- 7. Why Compliance Matters Non-Compliance Rate Home pages with WCAG 2 failures (WebAIM 2025) 94.8% Legal Penalties Significant fines for non-compliance €€€ Market Access Risk of exclusion from European markets EU UI/UX User Experience Better user experience for everyone
- 8. Implementation Testing Ensure compatibility with screen readers and assistive technologies. Design Phase Incorporate accessibility from the beginning, not as an afterthought. Deployment Integrate accessibility checks into CI/CD pipelines. Development Write semantic, accessible code with proper ARIA roles and keyboard navigation.
- 9. Practical Steps for Preparation Integrate Regular Checks Build accessibility testing into every stage of your development lifecycle. Train Your Teams Provide accessibility training on standards, ARIA implementation, and testing methodologies. Audit Existing Software Conduct comprehensive accessibility audits to identify barriers and non-compliance issues. Prioritize Issues Focus on critical accessibility problems and quick wins first.
- 10. Testing for Compliance Visual Verification Identify visual issues like insufficient color contrast and layout problems. Detailed Reporting Cross-Platform Testing Automated Checks Generate actionable reports on accessibility issues for developers Validate accessibility across browsers, operating systems, and devices Tools scan code for accessibility violations based on WCAG guidelines
- 11. Embrace Accessibility Legal Compliance Meet EAA requirements Wider Audience Reach more users with diverse needs Inclusive Experiences Create truly user-centric digital products
- 12. Resources 🔗 European Accessibility Act 🔗 WCAG 2.1 🔗 EN 301 549 🔗 Easy-to-understand WCAG guide 🔗 Web accessibility design patterns 🔗 Overview of WCAG in visual format
- 13. Want to explore AI-powered testing with Applitools? Schedule a call with a Testing Specialist applitools.info/v2j Questions??